Taking down a replication server during the day

  • Just need some reassurance of my own thoughts on this haha

    Server A, B and C. Replication is handled on B Pulling from A and C and pushing out to the other.

    Now if the server B needs a reboot for a vital network fix, can I get away with disabling the distribution agents whilst this takes place?

    Therefore from my knowledge, the log reader will just build up the transactions on A and C ready to release to B once I enabled the dist agents again?

    Is this right?

    I can't think there are any issues at all.

  • You can reboot whenever you want. You can be really sloppy like me and not bother stopping any agents. We replicate over 100 million rows a day and have never lost anything but maybe it's dangerous of me to guarantee the integrity of someone else's software!?!

  • Yeah slap head moment on my part as of course if the replication does have an issue, the agent will just keep retrying until it sends those transactions! Duh!

    I'm sure I had an instance tho where the VPN connecting B and C went down, and a certain amount of records went out of sync. Not sure what happened differently there.

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

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