Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Server Restart Sequence - With Replication Expand / Collapse
Author
Message
Posted Monday, August 9, 2010 3:00 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:19 PM
Points: 228, Visits: 555

I have replication setup and have separate servers for publisher, distributor and subscriber.

I need to restart my distributor. Is there a restart sequence I need to follow?


Help much appreciated

Shinoj
Post #966259
Posted Monday, August 9, 2010 3:04 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, November 14, 2014 12:37 PM
Points: 2,361, Visits: 6,752
SQL Server replication is quite robust. It wont matter which server goes down first. But if you want to be safe, you can stop the log reader agent and restart your distributor and start the log reader agent. All the changes that were done on the publisher will stay in the log till the distributor reads it. (There is a time limit off course but it is more than an hour)

-Roy
Post #966262
Posted Monday, August 9, 2010 3:07 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 3:07 PM
Points: 2,049, Visits: 3,592
Shinoj Ramanathan (8/9/2010)

I have replication setup and have separate servers for publisher, distributor and subscriber.

I need to restart my distributor. Is there a restart sequence I need to follow?


Help much appreciated

Shinoj


You should be able to just restart the distributor and have no problems. Not sure how you have things set up (i.e. PUSH / PULL subscriptions if transactional) but the log reader and distribution agents will typically run on the distributor so, there will be no problems with restarting that box.

Post back if you have problems.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #966263
Posted Monday, August 9, 2010 3:10 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 4:19 PM
Points: 228, Visits: 555
Thanks roy..

I sort of messed up the whole thing when i did it last time...
I restarted the distributor without stopping the logreader agents and after the service came back up... some of the agents simply did not get back to normal..

Had to re setup the publications

So lets see.. I got stop the logreader agents, restart the distributor and start the logreader agents..

Thanks
Shinoj
Post #966266
Posted Monday, August 9, 2010 3:13 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 3:07 PM
Points: 2,049, Visits: 3,592
While I agree with Roy that stopping the log reader agents is the nice way to do things, it is not necessary. I would be curious as to what error you were seeing during your last restart.

It is designed in such a way that it can recover. We have ours set on a cluster and fail it over periodically with no issues.

Hope this helps and please post back if you have problems.


David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #966269
Posted Tuesday, August 10, 2010 6:50 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, November 14, 2014 12:37 PM
Points: 2,361, Visits: 6,752
Keep us posted how it went this time.

-Roy
Post #966632
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse