April 26, 2012 at 9:35 am
If I connect to the secondary server, I can query the "log_shipping_monitor_history_detail" table and see a message that tells me how many files were restored.
The problem is, that I have several log shipping jobs across several servers that are being monitored by one monitoring server. The data appears to exist for all the jobs in the monitoring servers same table. However, I can't figure out which server/database the message is referring to. The database field is NULL on the monitoring server, and the table does not contain a guid for the job. Am I forced to go back to the secondary source server?
I need this info, because I've had situations, where the log shipping chain apparently broke, and the log shipping kept cranking along as usual for weeks, except it was restoring 0 files (jobs were successful). I need some way to verify that at least 1 file was actually restored everyday for each Log Shipping setup.
Any better ideas on how to verify this?
May 1, 2012 at 11:18 pm
You can configure thresholds in the log shipping configuration. If these thresholds are exceeded, the log shipping alert job will raise a failure.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply