SR with VMware support is the best place to start.
If you want to look at logs, then you can either download the log bundle and then look at the extracted bundle or SSH / putty into the appliance.
The best place to start with troubleshooting a job is the look at the vdr-server.log in /usr/local/avamar/var/vdr/server_logs.
In this log, search for the backup job name.
If you do not find definitive information there for a root cause, then you can go to /usr/local/avamarclient/. In this directory, I usually do an "ls -ltR | less" and then look for the correct backup log in the returned results.
The log files here are going to be named based on the backup job name, then vmimage?.log where ? is w for windows and l for linux.
The best place to start with this log is generally the end of the log file and work your way backwards.
If these two logs do not provide information, then it is best to open an SR with VMware support.
One other point, that MIGHT help a bit.
If you SSH / putty to the VDP appliance, there are two documents in /space/avamar/doc.
One is called event_summary.txt which gives a list of all of the error codes that we generate.
The second is called event_catalog.txt which will describe the error code in a little more detail, and if a defined solution exists, then we document it there as well. A large number of the codes have "Call Support" as the Remedy.
Hope this helps.
-Greg Sparks
