If this is the case then it will be fixed in a newer version of the VDDK, the reason why I suspect it might be related is because if the Vmware VixDiskLib_Cleanup() hangs then the disks will not be removed from the backup host. A fix has been identified, and will be available in the VDDK 5.1 first update release Windows processes can sometimes hang when calling VixDiskLib_ConnectEx() or VixDiskLib_Cleanup() due to a race condition while loading or unloading libraries. Hang in connect or cleanup due to intermittent race condition. HP has since come back to me with an actual fix.Īs of version 8.00, Data Protector uses VDDK 5.0U1, and our issue is related to the following Known VMware Issue: The workaround was simply to not run backups against your virtual VEAgent host, or to make your VEAgent host physical.

In the last post on this subject I discussed an issue where backing up a virtual VEAgent/Backup/Proxy host itself leads to orphaned disks on the host (when using a HotAdd backup transport method), which inevitably leads to the host itself becoming unstable and crashing – thus causing any subsequent VM backups relying on he backup host to fail!

Virtual disk consolidation is needed