August 26, 2009 at 4:17 pm
Hi...we are about to move and we have SQL Servers that use transactional replication...does anyone know what sequence the servers should be shutdown and started in order for replication to be restored successfully?
August 26, 2009 at 4:21 pm
Please provide your topology/architecture ... how many publishers, distributors and subscribers ...... what is the sequence you are planning to restart them ???
generally replication does come back up pretty fine after a reboot, but depending on architecture you might have to sequence the reboots in an order for an hiccup free reboot.
-------------------------------------------------
-Amit
Give a man a fish and he'll ask for a lemon. Teach a man to fish and he wont get paged on weekends !! :w00t: - desparately trying to fish [/size]
August 26, 2009 at 4:35 pm
Hi Amit...hope this helps...
Server A serves as a publisher to subscriber Server B, DB 1, which pulls the data
Server B, DB 2 also serves as a publisher to subscribers Server C and Server D, which also pull the data.
Is this enough info?
August 27, 2009 at 11:06 am
You should not have any problem with how you shut it down but I assume you will be blocking all traffic to the DB Server before you shut down.
-Roy
August 27, 2009 at 11:19 am
Thank you Roy for your response...
What about startup? Should there be a certain sequence or will SQL Handle it?
August 27, 2009 at 11:23 am
SQL Will handle it.... The monitor will be red but you can manually start it up without any issues if you want to. How much downtime are you talking about?
-Roy
August 27, 2009 at 11:33 am
Hopefully no more than 8 hours...thanks again!
August 27, 2009 at 11:41 am
Since it is eight hours, make sure you shut down all traffic to the DBs and take you last transaction back up (If you have Warm StandBy) or take a back up of the DB before moving servers. You never know what could happen to HW when transporting.
-Roy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply