We have a production primary SQL2008R2 server enterprise edition (Windows 2008 R2 enterprise) and a secondary SQL2008R2 server enterprise edition (Windows 2008 R2 enterprise).
We have configured log shipping on 10 databases between the 2 servers via the wizard which created the lsbackup, the lscopy, and lsrestore jobs for the 10 databases in the SQL agent, that will run according to schedule.
We see that the lsbackup job (runs every 2hrs from 12am) creates the backup logs in the log shipping folder in the secondary server for the 10 databases and the lscopy job (starts 15min after lsbackup job) copies this backup log files to another folder in the secondary folder which the lsrestore job (runs 5 min after lscopy job) takes from to restore the database using standby option in the secondary server.
But an alert (lsalert job runs every 6hrs from 12am) notifies that restore is out of sync and no restore was performed. e.g. 'The log shipping secondary database DB1 has restore threshold of 360 minutes and is out of sync. No restore was performed for 181453 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.'
This is happening for 9 out of the 10 databases that the log shipping was configured. The remaining database has an alert that the backup has not been performed but the backup log files were created in the folder. e.g. 'The log shipping primary database DBTEST has backup threshold of 60 minutes and has not performed a backup log operation for 194199 minutes. Check agent log and logshipping monitor information.'
So why is it out of sync and how to put it back in sync for these databases? Are the timings for the jobs wrong to cause this?