Transactional replication - rebooting the servers

  • I have transactional replication set up between two servers, PubServer and SubServer.

    There is some planned downtime for upgrade of VMWare software/hardware for the VM host these servers sit on.

    Both servers will need to be shut down while this maintenance happens.

    What do I need to do to ensure replication is started up as normal when the servers come back up?

    Is there a preferred order in which to perform the shutdown/restarts of the publisher vs the subscriber?

    I'm struggling to google this, any pointers much appreciated.

    ------------------------------------------------------------------------
    Bite-sized fiction (with added teeth) [/url]

  • All things being equal, you do not need to worry about the order that the servers are started etc. Replication is smart enough to re-try. At worst, you may need to start some of the replication agents if they re-try too many times and then stop.

    If you are particularly concerned, I suggest that you start servers in the following order:

    - distribution server

    - publication server(s)

    - subscribers

  • Great - thanks for the help!

    ------------------------------------------------------------------------
    Bite-sized fiction (with added teeth) [/url]

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

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