I am facing a somewhat serious problem with Log Shipping on SQL Server 2005 and I am having trouble to correct it, so I will try some help from SF's experts.
I have a Windows 2003 Server (PROD) that ships transactional log backups to another two servers:
- STAND1: Windows 2003 Server with SQL Server 2005.
- STAND2: Windows 2008 R2 Server with SQL Server 2005.
The problem is that Log Shipping to STAND2 is breaking for ~ 90 minutes some times of the day and returning back without intervention. The breaking occur at times when the backup file is larger (after reindexing, etc). I can see the message below logged on the COPY job:
*** Error: The specified network name is no longer available
The copy agent was breaking dozens times a day only to STAND2 server, and after the changes below "only" breaks ~ two times a day:
- The frequency of the backup job was changed from 5 minutes to 10 minutes.
- Instead of backing up the 4 databases to the same folder, the log backups are now saved on separated folders for each database.
- The backup job doesn't run 24hs now, and only for 14 hours a day, when people are working on the database.
- I configured the SQL Server instances on the three servers to limit the memory, leaving more memory to the OS.
Now I don't know what to do. Any help will be much appreciated! Thanks!
© Server Fault or respective owner