+6
Hi all.
After upgrading to 11.32.13 we are sporadically starting to see the below error when doing Vmware snapshot backup. The backup job fails or completes with errors:
“Snapshot creation is disabled on [Server name] by [].”
Snapshot creation is not disabled for the server, and when backup is re-run everything is working.
Have anyone else seen this behavior?
Regards
-Anders
Best answer by Sebastien Merluzzi
View originalHi,
case is open and i set the key.
Also i added an new schedule for backup failed vms only to cover this issue.
Lets see what the support find out.
We have the same issue.
Set pending cause [Snapshot creation is disabled on [xyz] by [].]:
If we retry the backup it works.
We are running version 11.32.42 , so it should have been fixed already?
You do not need to restart the commvault services for the additional setting to take effect.
32.28 will be out next week.
You do not need to restart the commvault services for the additional setting to take effect.
32.28 will be out next week.
But we are already on a higher version (11.32.42) and still have the issue.
It looks like a different issue then, you can either log a case with VMware or Commvault, they/we will check.
I see your case is now closed.
Whatever issues was present before is no longer occurring.
Hello, I have the same error messages since I upgraded to 11.32.49.
Should I add the Key on the media agents?
You should not need to, you can check with VMware Team so they can check and confirm and then if needed log a case with Support so we can check.
+1
Same issue at 1.32.45. Ramdom VM getting this warning snapshot is disabled.
Same issue at 1.32.45. Ramdom VM getting this warning snapshot is disabled.
Hi, I made a ticket to the support this week, and they told me to add the key as indicated in this topic.
It worked and I don't get these errors anymore.
+1
Same issue at 1.32.45. Ramdom VM getting this warning snapshot is disabled.
Hi, I made a ticket to the support this week, and they told me to add the key as indicated in this topic.
It worked and I don't get these errors anymore.
Unless they tell me it’s a false positive, masking the error/warning in the log, doesn’t fix anything.
Hi
That’s correct, it is already fixed.
You can set the key as a workaround, however the issue can also be different.
So you may log a case with SUpport so we can check & confirm.
Best Regards,
Sebastien
Adding the key means that commvault does not perform the bVerifySnapshotCreationAllowed check, but it performs the backups anyway.
Hi
We are on 11.32.45 and still have this issue.
Could see this was addressed in 11.32.28 itself, anyone else with similar issues?
Thanks,
Diwakar
Hi
We are on 11.32.45 and still have this issue.
Could see this was addressed in 11.32.28 itself, anyone else with similar issues?
Thanks,
Diwakar
Tried with adding the key as well, which didn't help
+1
Worked for us. Still think that masking a warning message, instead of addressing the issue is not a fix...
+5
We are on 11.32.49 and still had this issue intermittenly.
Will there be a hotfix for this issue instead of just the workaround?
We had our issue resolved.. Problem was the additional key was added at the cs level by the team.
After adding it to ma level, it fixed our issue
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
