March 17, 2011 at 4:49 pm
I'm planning on setting up some Log Shipping across a few SQL Server 2005 servers, and I've never really bothered with setting up the "monitor server" in the past. I thought I'd finally ask about it though to see what other people are doing.
What's the point of this monitor server when you can just monitor whether the jobs that are running for LS are successful or not? What advantage does it give you?
Would appreciate some comments.
Thanks.
March 20, 2011 at 8:12 pm
Bump - any help?
March 20, 2011 at 10:05 pm
Though the log shipping is pretty straight fwd and you can monitor manually but that will be reactive strategy.
For proactive, microsoft justified it here :-
http://msdn.microsoft.com/en-us/library/ms190224.aspx
----------
Ashish
April 7, 2011 at 10:45 pm
The optional monitor server tracks all of the details of log shipping, including:
· When the transaction log on the primary database was last backed up.
· When the secondary servers last copied and restored the backup files.
· Information about any backup failure alerts.
The monitor server should be on a server separate from the primary or secondary servers to avoid losing critical information and disrupting monitoring if the primary or secondary server is lost. A single monitor server can monitor multiple log shipping configurations. In such a case, all of the log shipping configurations that use that monitor server would share a single alert job.
I hope it will help.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply