Implementing and Monitoring Log shipping

• klnsuddu

  SSCertifiable

  Points: 5836

  More actions

  May 29, 2009 at 12:54 pm

  #132705

  Hi,

  We are planning to implement Log shipping for 2 Production Servers, Server A and Server B

  Server A has 2 instances.

  Server B has 4 instances.

  We are planning to log ship all the databases from all the instances from both servers. For this At Secondary location, We build 2 servers, Server C and Server D.

  and Installed 2 instances in Server C and 4 Instances in Server D.

  Now for monitoring these 6 instances,

  1.can we use Only one Sql server instance?

  2.can we use Developer edition for this purpose?

  3.It should installed on Primary location or Secondary location?

  Thanks

• george sibbald

  SSC Guru

  Points: 104210

  More actions

  May 29, 2009 at 1:20 pm

  #1002237

  the most resilient way to monitor log shipping is to use a separate instance on its own server to do the monitoring. This can be any edition but the best to use is express because its free, and can be installed on a low end server or even a PC. One monitor server can handle multiple logshipping configurations.

  The only problem I can see with using developer edition is licensing, I am not sure if MS see a loghip monitoring instance as 'production'. It does not support a production application so I would hope not, so developer edition should be fine if thats what you have already.

  ---------------------------------------------------------------------

• george sibbald

  SSC Guru

  Points: 104210

  More actions

  May 30, 2009 at 2:59 pm

  #1002423

  My apologies , there is an error in the above post. You cannot use express edition as a logshipping monitor as it does not come with SQLAgent.

  I was thinking mirror witness servers.:blush:

  ---------------------------------------------------------------------