Hello,
I have only recently started using VDP after having taken over responsibilities for the VMware environment from the engineer who performed the installation. In familiarizing myself with the environment & configuration, I am seeing failed backup jobs for a number of VMs. To provide some background, there are a total of five environments; Production, QA, UAT, Development & Integration. Total VM server count is 61. Based on my reading of how VDP works, it has created eight virtual proxies in order to run multiple backup jobs in parallel (Max Parallel Jobs = 64)
In reading the various posts, I found a script which allowed me to locate logs for the various VM's that are being backed up. For one particular VM (VAPP01), I've included an excerpt from the logs. If my interpretation is correct, the process is proceeding OK, until the last two lines. The server is a production server and currently being utilized and functioning without any issues, so I'm a bit perplexed by the message that the error is caused by the vmdk file.
Any suggestions or additional documentation recommendations that would help troubleshoot/resolve this issue would be greatly appreciated. I will continue to troubleshoot this issue.
Thank You in Advance,
Michael
*******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
2013-11-15 20:00:36 avvcbimage Info <9674>: virtual disk [Datastore4] VAPP01/VAPP01-000004.vmdk will be connected readonly
2013-11-15 20:00:37 avvcbimage Info <16041>: VDDK:VixDiskLibVim: Unable to find key for disk [Datastore4] VAPP01/VAPP01-000004.vmdk, trying snapshot tree.
2013-11-15 20:00:38 avvcbimage Info <16041>: VDDK:VixDiskLib: Trying to open disk [Datastore4] VAPP01/VAPP01-000004.vmdk using mode nbdssl.
2013-11-15 20:00:38 avvcbimage Info <16041>: VDDK:NBD_ClientOpen: attempting to create connection to vpxa-nfcssl://[Datastore4] VAPP01/VAPP01-000004.vmdk@esx04.some-company.com:902
2013-11-15 20:00:39 avvcbimage Info <16041>: VDDK:Opening file [Datastore4] VAPP01/VAPP01-000004.vmdk (vpxa-nfcssl://[Datastore4] VAPP01/VAPP01-000004.vmdk@esx04.some-company.com:902)
2013-11-15 20:00:39 avvcbimage Info <16041>: VDDK:DISKLIB-LINK : Opened 'vpxa-nfcssl://[Datastore4] VAPP01/VAPP01-000004.vmdk@esx04.some-company.com:902' (0x1e): custom, 419430400 sectors / 200 GB.
2013-11-15 20:00:39 avvcbimage Info <16041>: VDDK:DISKLIB-LIB : Opened "vpxa-nfcssl://[Datastore4] VAPP01/VAPP01-000004.vmdk@esx04.some-company.com:902" (flags 0x1e, type custom).
2013-11-15 20:00:39 avvcbimage Info <9675>: Connected with nbdssl transport to virtual disk [Datastore4] VAPP01/VAPP01-000004.vmdk
2013-11-15 20:00:39 avvcbimage Info <12008>: Check that the backup proxy VM(127.0.0.2,vbkp01.some-company.com,vbkp01,172.16.15.250) is deployed on an ESX(i) host that has a path to the storage holding the virtual disk being backed up ([Datastore4] VAPP01/VAPP01-000004.vmdk). Also check that the proxy is configured to protect this datastore
"Error caused by file /vmfs/volumes/51d70c8d-0f6da9b9-41eb-0025b501a06f/VAPP01/VAPP01-000004.vmdk"
*******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************