Hot-adding backup jobs using the Virtual Disk Development Kit (VDDK) 6.0 fails with timeout errors
Article ID: 337528
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- Hot-adding backup jobs using the Virtual Disk Development Kit (VDDK) 6.0 fails.
- In the VixDisklib log files, you see entries similar to: FILE: FileLockWaitForPossession timeout on 'C:\ProgramData\VMware\hotAddLock.dat.lck\M54759.lck' due to a local process '11348-130780441008509426' FILE: FileRemoveDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\hotAddLock.dat.lck): The directory is not empty (145) Note: For more information on logging, see Collecting diagnostic information for the VMware Virtual Disk Development Kit (1006186)
Environment
Virtual Disk Development Kit 6.0
Cause
This issue occurs in two different scenarios:
Scenario 1:
Prior to VDDK 6.0, the virtual disks of a target virtual machine were hotadded to the proxy virtual machine during VixDiskLib_ConnectEx and hotremoved during VixDiskLib_Disconnect API calls.
Starting from VDDK 6.0 and later, each virtual disk of the target virtual machine is hotadded to proxy during VixDiskLib_Open and hotremoved during VixDiskLib_Close API calls. Each hotadd/hotremove requires the proxy virtual machine to be reconfigured.
If the reconfiguration operation is time consuming, some of the hotadd/hotremove calls may timeout due to lock contention resulting in the errors listed in the symptoms section.
Scenario 2:
If a VDDK 6.0 base process crashes before it has cleaned up its lock files, the disk in question cannot be accessed until the lock is manually removed.
Resolution
To resolve this issue, use one of these options:
Scenario 1: Reduce the number of parallel backup jobs to limit the virtual disks being backed up.
Scenario 2: Manually clean the lock files. For more information, see Investigating virtual machine file locks on ESXi/ESX (10051).
Additional Information
Feedback
Yes
No
Powered by
