Skip to main content

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

 

@Sebastien Merluzzi,

 

The hotfix did not fix the issue. I have uploaded logs for a failed job to the case.

 

Regards

-Anders


@Sebastien Merluzzi 

 

The additional setting did the trick.

Do you know if I can remove the additional setting again, after the fix is part of a future MR?

 


Hi @Sebastien Merluzzi Sebastian.

 

I have created a case to get the hotfix.

 

Regards

-Anders


Worked for us. Still think that masking a warning message, instead of addressing the issue is not a fix...

CommVault is asking VMware to create a snapshot and is getting a denial without a proper reason. The additional setting makes a direct call to the create snapshot API. This should generate a proper VMware error explaining the denial or in most cases we see the snapshot is actually created. 


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 ? 


Hi @SSchmidt ,

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,

 

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.


@SSchmidt Excellent, what is your case number please?


send via pm


@ApK ,

Actually you need a key too.

Let me know

Best Regards,

Sebastien


@Egor Skepko 

You do not need to restart the commvault services for the additional setting to take effect.

32.28 will be out next week.


@Sebastien Merluzzi We are running 30.64 atm, wil it be there aswell?


Where to add below key? Any path 

Name: bVerifySnapshotCreationAllowed
Category:VirtualServer
Type: Integer
Value: 0

in VSA.


@Egor Skepko 

Yes in 30.72.


@NDinesh 

This key is set on the VSA Proxies used for the VM Backups. - The path is VirtualServer.

Steps to apply are below:
CommCell Console: https://documentation.commvault.com/2023e/expert/adding_additional_setting_from_commcell_console.html

Command Center Web Console: https://documentation.commvault.com/2023e/essential/adding_setting_for_servers_and_server_groups.html

 

Best Regards,

Michael


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?


Hello, I have the same error messages since I upgraded to 11.32.49.

Should I add the Key on the media agents?


@johann 

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.


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


Same issue at 1.32.45. Ramdom VM getting this warning snapshot is disabled.


@ApK ,

You cannot remove it.

The Additional setting is to not perform the pre-check at all, and instead directly call the create snapshot API.

Best Regards,

Sebastien


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.


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 @SSchmidt ,

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 @ApK ,

This has been fixed in Hotfix 8847, MR will be available soon.

You can log a case or I will let you know which one asap.

Best Regards,

Sebastien


Reply