The job starts, backs up the vmx, nvram, and log files but when it goes to transfer the vmdk, it fails.
It happens for every VM it attempts to back up within the job, and on all hosts part of the cluster.
Errors in the logs include:
VDDK 141 0 145457 Remote connect done
VDDK 36 0 145457 Failed to open vmdk
VDDK 138 0 145457 VDDK error encountered: code 16053
VDDK 139 0 145457 Retrieving error message text
The ESX server logs were also filled with authentication errors, which may have cascaded into 'can't
start subsystem' errors.
VDDK 52 0 145457 VDDK error message is 'One or more required subsystems failed to initialize'
Customer was using a Windows AD account to confiure the VCenter client in the plugin.
Specify a user account that can be used to log on to the vCenter or
ESX Server. The configured user account must have privileges to register or create virtual machines
Using a local Windows Adminsistrator account on the VCenter machine as opposed to a Windows AD account, in the plugin configuration resolved the issue.
