Lock on machine believed to be attributed to vRanger (Failed snapshot locked file being shown whe (4047119)

Customer believes that vRanger has lock on the machine, and they are unable to snapshot to backup normal.

There can be multiple reasons why the disk becomes locked, and unable to snapshot the virtual machine. There disk could have exceed the maximum block size permitted for the target datastore. There could be "phantom" snapshot or a broken snapshot tree for the machine. The snapshot manager for the machine may or may not show the snapshot being presented so verification will be needed.

1. Putty to machine in question and login with root

2. cd /vmfs/volumes/datastore name/machine/.vmdk

3.run a ps-ef | grep machinename.vmdk This will show if the .vzbin is running in the list of processes for the machine. If this is the case we will need to continue with the steps in this resolution: SOL76568
 

4. run command in brackets (cat machinename.vmdk) This will show you if the vzmutex has been uploaded to the host.

If you do not see the .vzbin listed in the temp directory or do not see the vzmutex file uploaded on the machine. You can safely assume that the application vRanger does not have a lock on the machine. To resolve the issue offer the customer the option to cold clone/migrate or perform a clone of the machine as a workaround to resolve the problem.