+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
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.
+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.
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.
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.
Hello, I have the same error messages since I upgraded to 11.32.49.
Should I add the Key on the media agents?
I see your case is now closed.
Whatever issues was present before is no longer occurring.
It looks like a different issue then, you can either log a case with VMware or Commvault, they/we will check.
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.
You do not need to restart the commvault services for the additional setting to take effect.
32.28 will be out next week.
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?
Hi,
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.
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
Hi All,
as per documentation:
https://documentation.commvault.com/v11/expert/files/service_pack/updates/11_32_35.htm
The fix should be Included from Maintenance Release 11.32.28 (Nov 07, 2023) and all after. We are running 11.32.35 and have the problem.
Do you know something about that ?
Is the way now set the key ?
ok, so the path is the category, VirtualServer
Just need to add the Additional Setting,
+1
Hi Sebastien
Thanks for the prompt response, I cannot update to the latest MR as there is a strict Change Control/Freeze in place at present.
So the Key workaround would help.
HI
The key is a workaround, can you upgrade to latest MR?
+1
You set it on the VSA/MediaAgent.
additional key:
Name: bVerifySnapshotCreationAllowed
Category:VirtualServer
Type: Integer
Value: 0
Do you have the Path on the MA where this Key is set? - I’m having the same issue !
You do not need to restart the commvault services for the additional setting to take effect.
32.28 will be out next week.
+6
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
