Recently on a new install of Avamar version 6.1; I had a VMware Image based backup fail with error 10007. Upon further investigation of the backup job log I noticed that the snapshot failed with: A general system error occured: Protocol error from VMX. This is a good example of two very vague errors on both the backup system and the virtual infrastructure. So to further investigate we needed to look deeper into the vmware.log file…

Incoming search terms:

• netbackup snapsure file system creation fails
• avamar & no vm
• no vm error in avamar
• avamar failed no data error
• avamar no vm
• no vm avamar
• avamar 6 1 sql cluster 10007
• netbackup general ystem error occurred protocol
• location of ndmp vnx log files
• backups fail vmx avamar

I’m going back over some of the new differences in Avamar 6.1 and am very impressed with the enhancements that Avamar now has with VMware image based backups. Before version 6.1 you needed a seperate image proxy for Linux and a seperate proxy for Windows, now with the new proxy design both Operating Systems have been integrated into one proxy. Not only does the proxy support both OS’s but now it also supports File Level Recovery to both OS’s where as Windows was only supported previously. To be more specific; the Unified Proxy now supports Windows NTFS, and Linux ext2, ext3, and LVM. The proxy does NOT support the following: Windows GPT Partitions, Windows Dynamic disks, Extended Partitions, Encypted Partitions, Compressed Partitions, or XFS.

Incoming search terms:

• proxy appliance vmware
• vmware proxy appliance
• avamar extended partitions are not supported
• avamar vmware
• emc avamar vmware image backup appliance
• restore code 536870919: miscellaneous error
• avamar proxy file size limit
• avamar 6 1 extended partition
• avamar vmware image and file level extended partitions are not supported
• ndmp backup job slow on the vnx