If your backup is still running, try this..
1.Get the backup job ID of the running job (If you have VI client connected, See recent tasks at the bottom and the one under details column of the VDP backup job is the Job ID associated with the backup)
2.SSH to the VDP appliance and run the command tail -f /usr/local/avamarclient/var-proxy*/<Backup JOB ID>*vmimage?.log
By this atleast you will know if you backup is still running..if you see something like this..
==> /usr/local/avamarclient/var-proxy-1/Sanity-Feb-04-Sanity-Feb-04-1360209600062-a6e80a4cd7b59d767a97a2626da0a950503f215f-3016-vmimagew.log <==
If the backup is completed, you should see something like this..
==> /usr/local/avamarclient/var-proxy-8/Sanity-Feb-04-Sanity-Feb-04-1360209600062-ee4eb28536c3f37cb0b5bde293816852cd0fb559-3016-vmimagew.log <==
2013-02-06 20:29:12 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLoadVMCb
2013-02-06 20:29:12 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVimLogout
2013-02-06 20:29:12 avvcbimage Info <0000>: VixDiskLib vMotion reservation successfully released
--------------------------------------------------------------------------------------------------------
----- END avvcbimage log 2013-02-06 20:29:15 PST (1 warning, 0 errors, 0 fatal errors)
--------------------------------------------------------------------------------------------------------
