Chat now with support
Chat with Support

Spotlight on SQL Server Enterprise 11.7 - Release Notes

Log Shipping - Secondary Latency Alarm

The Log Shipping - Secondary Latency alarm is raised when the amount of time that elapsed between the log backup being created on the primary database and when it was restored on the secondary database exceeds a threshold.

When the alarm is raised

It may indicate a problem in getting data from the primary database to the secondary database. Looking at the history of the copy or restore job may help identify the problem. To do this, go to the Secondaries page of the SQL Server | High Availability Drilldown and select an item in the grid to view the history.

TIP: The Primary ID column may be hidden by default. See Show, hide and order columns for more information on how to display hidden columns.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating