asked
EMC's Data Domain with SQL Server Backups
Is anyone using EMC's DataDomain product for their SQL Server Backups where they backup directly to Data Domain over a CIFS's share? I am having a lot of trouble setting this up where my backups are sporadically failing with error Operating system error 53(The network path was not found.). [SQLSTATE 42000] (Error 3201) BACKUP LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed What is crazy is that sometimes I get this message when I am verifying the backup file that I just successfully wrote to the path. Anyone else encounter this type of problem and successfully work with EMC support to resolve it. Right now my team and I are getting a resolution. We have ruled out DNS by using host files and IP addresses directly. I feel this is something on their side as I have no issue writing to local disk or another network share. I am only pushing around 40 servers so far to the device, no where near my entire load.
We backed up to local disk then had, EMC NetWorker come in and do a file copy from local disk to the DD. While the local disk was on a EMC SAN, linking the two together was a major headache. Could it be that the DD is changing the virtual tapes which could be causing a blip in the path, temp offline online kind of situation?
Might be worth having a chat with Chris Testa-O'Neill. He's ex-EMC, might have some ideas...
Thanks for the comments and suggestions. Working with EMC support it was determined that we had way to many transaction log backups in our backup folders. The recommendation was no more than 1000 files per directory and no more than 1000 subdirectories. We have implemented a purge routine and are adopting a strategy of a dbname subdirectory per database for tlog backups.
13 People are following this question.
