I have recently set up log shipping in MSSQL 2005 (sp3 cu7) using 2 SQL instances and a primary DB on instance 1 log shipping to a secondary database on instance 2. I have the secondary database in no recovery mode as I simply don;t want anything change the database. However it keeps failing after a few hours and I would like to ask some questions to make sure I have the environment is set up properly. I don't have any problems setting up the log shipping but it fails only after a few hours and I get the following error messages:
Error: Could not find a log backup file that could be applied to secondary database
The log shipping secondary database INSTANCE.SECONDARY has a restore threshold of 45 minutes and is out of sync. No restore was performed for 504 minutes. Restored latency is 10 minutes. Check agent log and logshipping monitor information.
My question are:
1 - Do I run maintenance plans on the primary server now I have log shipping essentially backing up the TRN files on the primary database? Does log shpping truncate the primary databases TRN files?
2 - What happens if I run maintenance plans on teh secondary database? Would this have impact on log shipping?
I have a feeling that the LSN is out of sequence as another backup job has run, but I just don't know how to get this working right.