Post reply

Server Restart Sequence - With Replication

  • August 9, 2010 at 3:00 pm

    #157139

    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

  • August 9, 2010 at 3:04 pm

    #1204416

    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

  • August 9, 2010 at 3:07 pm

    #1204417

    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

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • August 9, 2010 at 3:10 pm

    #1204420

    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

  • August 9, 2010 at 3:13 pm

    #1204423

    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

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • August 10, 2010 at 6:50 am

    #1204723

    Keep us posted how it went this time.

    -Roy

Viewing 6 posts - 1 through 5 (of 5 total)

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