Monitoring Log Shipping
My client in Manhattan maintains a disaster recovery server in South Brooklyn. We employ log shipping to sync five databases. I have been trying to determine the best way to programmatically determine whether the databases are synchronized, or perhaps better, when they were last synchronized.
The problem is complicated by the fact that the system appears healthy from the primary server’s perspective – it created the logs and shipped them successfully – but not from the secondary server’s perspective – sql agent shut down so logs were not restored and alerts not sent.
Does anyone have suggestions regarding “best practices” to monitor system that employ’s log shipping. We do have a monitor server available, but it is currently on the same file system as the primary. I would rather not have to lobby for a third server – monitoring from the secondary would be fine if it can accurately tell me that status of the secondary in the event that the primary goes missing.