Environment:
DP 9.05, also seen with 9.04
VMware ESXi 6 u1
vCenter Server 6 u1
The VEPA integration has been installed on the vCenter server.
Session Report extract:
[Warning] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:15 PM
Virtual Machine 'VM-NAME': Could not lock vMotion.
...
[Normal] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:19 PM
Virtual Machine 'VM-NAME': Backing up configuration file VM-NAME.vmx
...
[Normal] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:21 PM
Virtual Machine 'VM-NAME': Creating snapshot
...
[Normal] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:26 PM
Virtual Machine 'VM-NAME': Getting Changed Blocks for disk scsi0:0.
[Major] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:38 PM
Virtual Machine 'VM-NAME': Could not backup disk scsi0:0
Normal] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:47:43 PM
Virtual Machine 'VM-NAME': Removing snapshot
...
[Normal] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:48:17 PM
Virtual Machine 'VM-NAME': Unlocking vMotion
[Warning] From: VEPALIB_VMWARE@hostname "/DATACENTER" Time: 1/12/2016 3:48:41 PM
Virtual Machine 'VM-NAME': Could not unlock vMotion
...
[Critical] From: BSM@hpdp0905.kms.hmgc.net "SPEC_1" Time: 1/12/2016 3:49:34 PM
None of the Disk Agents completed successfully.
Session has failed.
VEPALIB_VMWARE_THREAD debugs:
[199] 2016-01-12 15:46:51.581 ("/integ/vep/vepa/Plugins/Vmware/VmwareHelpers/QueryUtil.cpp $Rev: 46816 $ $Date:: 2015-02-15 06:27:39":62)
[199] <<=== (7) } /* QueryUtil::getDynamicProperty */
[199]
[ 20] [VirtualEnvironment::VirtualMachine::isVmotionDisabled] Returning:
Type='bool';value='false'
...
[ 99] 2016-01-12 15:46:51.581 ("/integ/vep/vepa/Plugins/Vmware/VmwareHelpers/DiskUtils/VixDiskLib.cpp $Rev: 2517 $ $Date:: 2009-10-28 16:12:58":204)
[ 99] ===>> (9) VixDiskLib::VixDiskLib_PrepareForAccess {
[ 99]
[110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_PrepareForAccess: Prepare to access disk.
[110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_Connect: Establish connection.
[110] [VddkUtil::diskLibLog] VixDiskLib: Resolve host.
[110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLibVim was not loaded during initialization. Error at 355.
[110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_PrepareForAccess: Disable Storage VMotion failed. Error 16053 (One or more required subsystems failed to initialize) at 4000.
[ 20] [VixDiskLib::VixDiskLib_PrepareForAccess] Returning:
Type='unsigned __int64';
value='16053'
Explanation:
With version 6, VMware introduced a bug that leads to a library conflict.
Reference article: http://kb.vmware.com/kb/2120818
This has also been documented in the DP Integration Guide (Integration.pdf), search for 2120818.
Solution:
Until VMware has resolved this bug the following workarounds are available:
Install the vCenter and the VDDK on separate servers.
or
Copy the libldap_r.dll and liblber.dll from \Program Files\OmniBack\lib\vddk\AMD64 to \Program Files\OmniBack\bin.
Additional info:
HP generally does not recommend to install the VMware Integration component onto the vCenter Server because
this could cause severe performance issue. However, for a test environment this should be OK.