I was setting up an NDMP accelerator node today to back up a new VNX and came across this error message when trying to backup a test volume for the first time:

Errors and Exceptions
2013-02-13 11:25:19 avndmp Error : [snapup-/NDMP_Test] NDMP: SnapSure file system creation fails (Log #2) 2013-02-13 11:25:19 avndmp Error :

[ndmp2avtar-/NDMP_Test/] Problem reading 65536 bytes from NDMP stream socket, at stream position 0: code 104: Connection reset by peer (Log #2) 2013-02-13

11:25:34 avtar FATAL : Backup aborted due to earlier errors. No backup created on the server. (Log #1) 2013-02-13 11:25:35 avndmp Error :

[snapup-/NDMP_Test] Backup for target /NDMP_Test had errors. (Log #2)

After I double checked that everything was setup correctly on both the NDMP Accelerator node and on the VNX, I decided to simply create a manual snapshot on the VNX first and see if I would run into trouble. The snapshot completed without an issue. I went ahead and just reran the backup and it ran successfully. I guess the VNX just needed a little manual intervention.

Incoming search terms:

• snapsure file system creation fails
• vnx ndmp backup error
• problem reading 65536 bytes from ndmp stream socket at stream position 0: code 104:
• \Problem reading 65536 bytes from NDMP stream socket\
• logs snapsure
• vnx ndmp setup
• snapsure file system creation fails dataprotector
• snapsure file system creation fails netbackup
• vnx snapsure file system creation fails
• snapsure file system creation succeeds

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

When backing up SQL databases using the incremental option the backup job fails with “The statement BACKUP LOG is not allowed while the recovery model is SIMPLE” This is because the recovery model of the database being backed up is currently set to “Simple”. To resolve this error you must either change the database backup type to full, or change the database recovery model in SQL to either “BulkLogged or Full”.
The new EMC Avamar 6.1 Microsoft SQL plugin feature actually detects the recovery model of the database and skips the incremental backup, places a message in the log and automatically promotes the backup from an incremental to a full backup. So you can also upgrade Avamar to version 6.1 to resolve this error as well.

Incoming search terms:

• avamar NDMP: SnapSure file system creation fails error 10007
• avamar oracle 10007
• networker mssql incremental error
• SQL AVAMAR
• what is in the /data/col1/backup mtree?

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

When you try to create shadow copies on large volumes that have a small cluster size (less than 4 kilobytes), or if you take snapshots of several very large volumes at the same time, the VSS software provider may use a larger paged pool memory allocation during the shadow copy creation than is required. If there is not sufficient paged pool memory available for the allocation, the shadow copy cannot complete and may cause the loss of all previous shadow copy tasks. Follow this article and apply the fix: http://support.microsoft.com/kb/833167

Incoming search terms:

• buraguy
• socks4 proxy
• vmware backup size limit exceeded unable to transmit file
• avamar no proxy error
• avamar emc Size limit exceeded unable to transmit file
• volume shadow copy 0x800706be
• avamar pure offsite backup
• error code 10007 avamar and vmware
• emc avamar troubleshooting guide
• avamar sql simple recovery incremental