Solved

VM Snapshot Question

  • 30 June 2021
  • 3 replies
  • 2212 views

Userlevel 4
Badge +9

A couple of our VM clients have failed to delete the snapshot and has locked the snapshot file

Question:

What Commvault service is responsible for locking the snapshot file on the VM client ?

In the past we have just rebooted the VM to delete the Commvault snapshot

The virtual machine reports that it has virtual disks that need consolidation and this could not be performed automatically. In order to prevent a further buildup of delta disks and possible stability issues with the virtual machine, further backups of this virtual machine will not be performed until this condition is corrected. Please check if there are any locks on the virtual disks or if the disks are still attached to a backup proxy. Virtual disk file [[] /-000001.vmdk] is attached to virtual machine []

icon

Best answer by Gopinath 30 June 2021, 23:10

View original

3 replies

Userlevel 5
Badge +8

Hi Gary,

Part of HotAdd backups, VM disks will be attached to VSA proxy machine to read data directly, if any communication issue or vddk hotadd lock issues may left disks attached to VSA proxy which needs be removed. As mentioned in JPR, please cross check that vsa backup proxy and remove those backup VM disks from it and delete hotadd lock files if any in path of <install path>\Base\Temp\vmware-SYSTEM and restart cv services then perform consolidation on source VMs.

Please refer and follow best practice from HotAdd BOL

https://documentation.commvault.com/commvault/v11_sp20/article?p=32048.htm

Regards

Gopinath

Userlevel 4
Badge +9

We perform NBD backups

Userlevel 5
Badge +8

Gary,

in NBD or in general, vscleanup thread will take care of cleanup of CV created VM snapshot if backup job not cleaned it due to any communication or api call failed issues and cvd thread will cleanup which do once in a day. But if VSA proxy lost commination to infrastructure VC/ESXi or it got rebooted or process abruptly killed then next VSA proxy which picks this VM to protect will observe existing snapshot and fails with respective JPR. then also needs manual cleanup of snaps. Also hoping same VMs not getting protected with multiple VSA proxies with different subclients around similar timewill also lead to this kind of situation where manual cleanup required. Please check

 

Regards

Gopinath

Reply