Following upgrade to Plug-in for VMware version 11.2, some backups fail with the below log messages:
If a virtual machine is migrated through Storage vMotion during backup the job will fail. This can leave orphaned virtual disks on the datastores.
In preivous versions of Plug-in for VMware, disabling Storage vMotion for VMs during backup was optional, however since Plug-in for VMware 11.2 the 'Enable virtual machine locking' option is now set by default.
The plugin process will now attempt to lock the VM from vMotion before backup. After 10 unsuccessful locking attempts are made, the backup is failed.
While enabling vMotionLock should work fine, this operation may fail on some VMs for many vmware related reasons such as:
- failure to allocate memory
- Change Block Tracking related issues
- Incorrect vMotion entries left in the vmware database
- Disk consolidation issues leading to files being locked ...
All these issues should be reported and investigated with vmware Support.
