13,280 Metrics install automatically if you have Redgate Monitor installed.
If you are using Redgate’s SQL Server monitoring tool, Redgate Monitor, you can instantly install and run this metric on your servers.
This metric tracks the number of minutes since the most recent restore of the database.
If your log restores aren’t happening when they’re meant to, you want to know about it. You’ll be relying on restoring from logs should anything happen to your databases, and if you can’t restore to a certain point in time, you risk losing valuable data.
For more information about restoring data, see: http://msdn.microsoft.com/en-us/library/ms177446.aspx
Note: This metric works on SQL Server 2000 SP4 and later versions.
Note: An alert can only be raised after at least once restore has occurred.
Metric definition
Name
Last restore time
Description
Measure the time since the last restore, in minutes.
The T-SQL query that will collect data
Instances to collect from
Select the instance that contains a database that is regularly restored via log shipping.
Databases to collect from
The database you're interested in
Collection frequency
60
Use collected or calculated values
Leave the Use a calculated rate of change between collections check box unchecked
Metric collection
Enabled
Alert definition
Alert name
Log restoration overdue
Description
Raise an alert when the metric value goes
above the defined threshholds
Default threshold values
| High: | 122 |
| Medium: | 65 |
| Low: | 32 |
Note: These thresholds are intended as guideline values and are based on a log shipping frequency of 30 minutes. If they seem too high or too low in practise, replace them with values that match your log shipping frequency.
Raise an alert when the threshold is passed for
1 collection
Alert is
Enabled
