Logshipping Alert

Question

Date 6/16/2021 7:08:00 PM
Log Job History (LSAlert_server)

Step ID 1
Server server
Job Name LSAlert_server
Step Name Log shipping alert job step.
Duration 00:00:00
Sql Severity 16
Sql Message ID 14421
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: x. The log shipping secondary database x.dbname has restore threshold of 15 minutes and is out of sync. No restore was performed for 21 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421) The log shipping secondary database server.dbname has restore threshold of 15 minutes and is out of sync. No restore was performed for 19 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421) The log shipping secondary database server.dbname has restore threshold of 15 minutes and is out of sync. No restore was performed for 18 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421) The log shipping secondary database server.dbname has restore threshold of 15 minutes and is out of sync. No restore was performed for 16 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed.

Not sure why we are getting this error. There are no issue with copy and restore in Logshipping view history

Answer 1

Hi,

According the setting in the restore transaction log (the third screenshot): "Alert if no restore occurs within 15 minutes"（ The value in the default configuration is 45）. So the alert on the secondary server stated that the secondary database did not restore any log backup file within 15 minutes.

Based on the run interval set for backup jobs, copy jobs, and restore jobs, you may need to set this value("Alert if no restore occurs within") to 40.

>There are no issue with copy and restore in Logshipping view history

It seems that the copy and restore jobs are executed normally without errors.

Please also use the report ("Transaction Log Shipping Status") in SSMS to check the log shipping status of the primary server and the secondary server. Or use the stored procedure sp_help_log_shipping_monitor

>LS Alert in primary server no issue, but LS alert in secondary server is failing

Does the alert job continue to report errors on the secondary server? If this error only occasionally occurs once at the beginning, and the log shipping status is normal, you can simply ignore it.