So, I'm working with VDP and trying to backup 7 vms. I don't have this issue at any other client of ours. I have a client that the VDP runs at the default time set and fails to backup all the servers. I have yet to have it backup every server without any issues.
The error in vSphere Web Client tells me the following:
2013-03-29 20:01:05 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd
2013-03-29 20:01:05 avvcbimage Info <9667>: Calling ConnectEx with servername=***********************:443 vmxspec=moref=vm-25 on port 0 snapshot()
2013-03-29 20:01:05 avvcbimage Info <9668>: virtual machine will be connected readonly
2013-03-29 20:01:05 avvcbimage Info <9669>: VixDiskLib_ConnectEx returned VIX_OK
2013-03-29 20:01:05 avvcbimage Info <9672>: Disconnected from VM
2013-03-29 20:01:05 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 2, exitcode 202: plugin error 02
After the VDP Job fails. I notice that the snap is actually there, as I check the Snapshot Manager and see the "VDP-Job###" listed.
So, when I rerun the job manually it goes ahead and removes the VDP-Snapshot. Then begins to re-snap the VM. I know these VMs lock up for less than a minute when VDP runs. I feel as if when Virtual Center is being snapped it freezes the I/O on that VM and makes VDP lose it's connection to vCenter Server and then fails the VDP backup. So, we thought to get another set of 1TB Drives and put them in a RAID-1 Configuration and create another datastore to strictly be dedicated for VDP backups.
Even after this implementation we still are seeing the issue.
Does anyone have any suggestions as to what to try to get VDP working properly. Also, I have redeployed mutliple times to ensure it wasn't corruption in VDP itself.
Thank you to anyone who assists Image may be NSFW. Clik here to view.!
!