Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Monitor Log Shipping Expand / Collapse
Author
Message
Posted Friday, January 11, 2013 7:30 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 13, 2013 10:34 AM
Points: 5, Visits: 23
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.
Post #1406024
Posted Sunday, January 20, 2013 2:17 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 3:47 PM
Points: 3,087, Visits: 1,437
You can use the log shipping reports to monitor the state of the log shipping. These reports are standard. You can find more info on the link below:
http://msdn.microsoft.com/en-us/library/ms181149.aspx





My blog
Post #1409308
Posted Tuesday, January 22, 2013 3:56 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:45 AM
Points: 127, Visits: 307
All other ways will be just wastage if your sql agent services getting shutdown abruptly. Its good to find out reason for that and fixes that will be probably the best solution. Why don't you change the services parameter to start automatically when it stops.

But still you can try the other way around:- Query the msdb.log_shipping_secondary_databases and related table from other server (May be Primary) using link server and send alert.

Regards
Dhananjay
Post #1409906
Posted Tuesday, January 22, 2013 7:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 13, 2013 10:34 AM
Points: 5, Visits: 23
Thanks for the response - confirms that we did not miss something obvious - checking the tables on the monitor server seems to be the best approach. We check SQL Agent from the file system already - easy enough to add log shipping monitor to the same routine.

Post #1410033
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse