VM_LOCK_ERROR Cloud not obtain exclusive access to the Virtual Machine
Boomerang reads VM disk data from ESXi or vCenter host using a standard protocol supported by VMware. The "lock" error occurs if VMware protocol informs Boomerang that it cannot get access to specific virtual machines in the Protection Group.
The error message observed will be:
VM_LOCK_ERROR Could not obtain exclusive access to the Virtual Machine. This could be due to a storage migration or vMotion in progress; or the previous replication task was not terminated properly. Check the Virtual Machine status in the VMware console or unlock this vm.
This could be caused by one of the following reasons:
- vMotion or storage migration of VMs in the Protection Group are in progress,
- The VMs are protected by other Protection Groups and another replication is in progress,
- The VMs were not unlocked properly when the previous replication run (e.g., the Boomerang virtual appliance shut down non-gracefully.)
- The VMs are also protected by other backup software and the backup task is in progress, or
- The VMs were not unlocked properly by other backup software
In order to address this issue, we recommend:
- If vMotion or storage migration is in progress, wait for the process finishes, and then restart the current Protection Group replication.
- If other backup software is in progress, wait for the backup task finishes, and then restart the current Protection Group replication. To avoid future conflicts, update the schedule set to the Protection Group.
- If no backup task (by Boomerang or other backup software) is running, the VMs need to be unlocked manually. In the Activity page, you can click "Unlock VMs" button to unlock VMs. After clicking the button, wait for another 5 mins, and then restart the replication.