Error #1
Found in the beremote.log on the media server.
[fsys\vmvcb] - SymVmTools: GetVmDetails: SYM_VMC_ERROR: FAILED_TO_GET_MOB
[fsys\vmvcb] - SymVmTools: GetObjDetails: SYM_VMC_ERROR: FAILED_TO_GET_VM_PROPERTIES
[fsys\vmvcb] - VM_VCBPROXY_FS::GetVmDetails: vmcGetObjDetails failed, result = 0X28
[fsys\vmvcb] - VM_VCBPROXY_FS::GeneratebackupTree() Status CODE (E0009543) Getting VM Details for '(DC)VM House(DC)\vm\VMName '
[fsys\vmvcb] - SymVmTools: RetrieveHostContents: Skipping host
[fsys\vmvcb] - SymVmTools: RetrieveHostContents: Skipping host
[fsys\vmvcb] - SymVmTools: SetVmPowerState: enableChangeTracking: Completed OK
[fsys\vmvcb] - VM_VCBPROXY_FS::GeneratebackupTree() VM () config file 'C:\Program Files\Symantec\Backup Exec\Data\config-b--22-06-2011-11-18.xml' is not found.
Error# 2
[fsys\shared] - vddkConnectToVMWareServer() GD: status = 0X0
[fsys\shared] - SymVmTools: GetVmPropertyInfo: SYM_VMC_ERROR: SOAP_ERROR
[fsys\shared] - vddkGetVmBackupInfo(): vmcGetVmBackupInfo() failed, result = 0X6
[ndmp\loops] - LP_ENV::createVMWareSnapshot(): Failed to get config info for the VM '(DC) Datacenter(DC)\vm\HOSTNAME'
[fsys\shared] - SymVmTools: httpsget: SYM_VMC_ERROR: FAILED_TO_OPEN_FILE
[fsys\shared] - vddkGetManagedObjInfo(): vddkGetManagedObjInfo() failed, result = 0X53
UMI: V-79-57344-38273
Error Code: 0xe0009581 Cannot get the virtual machine XML information.
This Issue may occur due to a Network Connection Timeout with the VCenter Server.
Solution #1
Create the "VCB refresh timeout" registry key on the media server and run the backups again.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes
Solution #2