Log Shipping Failover

  • Hi

    We are using log shipping as part of our disaster recovery plan. We have a number of standby servers, and copy over the logs in 15 minute intervals. It’s stable and generally works very well.

    However, I have inherited a DR procedure which details how to fail over to the standby machines in the event of a disaster. Basically it involves recovering the standby databases, and then changing the IP address and name of the standby machine to that of the production machine.

    Changing the IP / machine name of the standby machine does concern me. I’ve read various posts / blogs saying this can be problematic to say the least.

    Does anyone have any advice when it comes to log shipping failover? Is it good practice to rename machines? Is there a better way?

    I’d like to update and test this plan asap, so that when the time comes I’m comfortable knowing it will work.

    Any advice would be appreciated...

  • I've previously used a dns entry to point at a SQL server. All I needed to do after that was change dns between machines.

    Changing the name of a server is not impossible but does cause a couple of issues. Primarily in replication based on experience.

  • I agree with MysteryJimbo, use DNS to handle connectivity to your machines. That way you can simply repoint DNS to the new server and your connections will be automatically repointed.



    Shamless self promotion - read my blog http://sirsql.net

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply