|Message:||The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and logshipping monitor information.|
This message indicates that log shipping is out of synchronization beyond the restore threshold. The restore threshold is the number of minutes that can elapse between restore operations before a message is generated.
To troubleshoot this message:
Make sure that the SQL Server Agent service is running for the secondary server instance and that the restore job for this secondary database is enabled and is scheduled to run at the appropriate frequency.
The restore job on the secondary server might be failing. In this case, check the job history for the restore job to look for the cause.
The log shipping restore job, which runs on the secondary server instance, might not be able to connect to the monitor server instance to update the
The backup alert threshold might have an incorrect value. Ideally, this value is set to at least three times the frequency of the restore job. If you change the frequency of the restore job after log shipping is configured and functional, you must update the value of the backup alert threshold accordingly.
When the monitor server instance goes offline and then comes back online, the
To update the monitor tables with the latest data for the secondary database, run
On the secondary or monitor server instance, the date or time is incorrect. This may also generate alert messages. Possibly the system date or time was modified on the one of them.
Different time zones for the two server instances should not cause a problem.