We have been successfully been running log shipping between our production facility and our DR site for the past 3 years. These two facilities are approx. 300 miles apart and we have a DS3 connection between us. Recently log shipping failed due to a hardware issue in one of our database servers. The hardware issue has been resolved and I attempted utilizing the database maintenance plan wizard in EM. I selected to perform an initial backup of the database and then to create and initialize the database in our DR site. It performs the initial backup just fine, however, I receive an error “unable to copy the initialization file to the secondary server”. I figured this was because the database is 60GB.



I decided to manually backup the database through EM and ftp the backup file to our DR site. Once received, I performed a successful restore at our DR site. This time in the database maintenance wizard I selected to use an existing database. The plan was successfully created with all subsequent ms sql jobs. Transaction files are now being created every 15 minutes at our production site. However, when I look at the log shipping monitor the last file copied and last file restored say “first_file_000000000000.TRN” and none of the TRN files at our production site are being copied over.



Any insight or ideas would be greatly appreciated.



Regards,



David Schachinger

IT Operations Manager

MS Sql Server LazyDBA home page