Disk Consolidation Impacting VMs hosting Critical Business Applications
Article ID: 414849
Updated On:
Products
Issue/Introduction
Snapshots fail to consolidate.
Third-party applications, such as VEEAM in a race condition with the vCenter Server holding the lock file
The affected virtual machine summary tab displays messages similar to:
- Snapshot consolidation required
In the hostd logs, where the virtual machine is running, you see similar messages such as:
YYYY-MM-DDTHH:MM:SS.SSSZ Db(167) Hostd[2099581] --> Locking conflict for file "/vmfs/volumes/xxxxxxxxxxxxxxx/xxxxxxxx_replica/xxxxxxx_replica-flat.vmdk". VMFS on-disk lock owner is host with MAC address
yyyyyyyy-dddddd-xxxx-000000000000 and VMFS lock mode 0x2.
Environment
VMware vCenter Server 8.0.x
VMware vSphere ESXI 8.0.x
Cause
One of the host have a lock on that VM's disk that could not be released for the consolidation process to complete on time. The snapshot could not finish on time, and another process was initiated by the VEEAM backup solution, leading to a race condition.
Resolution
This is a third-party issue. Vendor adjusted the I/O control to stagger the task to avert Race conditions.
Feedback
