What if Publisher and Distributor Server goes down

Question

HI I am having a Replication set up on my Production machines, this is my first time set up :Transactional Replication

Server A:SQL Server 2008 R2 SP1, Std edition , Publisher Database A (Simple recovery model) , and Distributor is sitting here .

Server B :SQL Server 2008 R2 SP1, Std edition , Subscriber  Database A (Simple recovery model)

I tested in inserting data to a table and also its getting replicated.My question is If Server A or Publisher Database A or Distributor database goes down , what are the next steps should i have to do , in order to 1.bring back servers ONLINE ,or keep data in Sync ...and what are the precautions should i have to make ?

Can any one please give me some information on this 

Thanks

Answer 1

First of all Its always Advisable to have Distributor on Separate Box.

Now First have a quick look how its work …

Publisher Publishes the articles and send these updates to Distributor after words distribution is pushing the data to subscriber, It depends on Pull or Push Subscription I am assuming push in this case and Distributor agent Is on Distributor DB

 Pub ----------à Distributor ----------àSubscriber

Scenario one,

Pub ----- -----à Distributor ----------àSubscriber

Now all the Transaction resides with Distributor will be delivering to Subscriber.

Scenario Two,

Pub ----------à Distributor -----X -----àSubscriber

Now its very much visible that your subscriber will be out of sync or behind the publisher until your distributor is up

-------------------------------SUGGESTION -----------------------

If you can effort Distributor on separate box

Else If I would be setting up with limitations I would have placed my Distributor @ Subscriber side. Thought behind that if my Distributor is Down with subscriber , No much impact a my publisher is still serving to business and If my Publisher is Down My Distributor can update my Subscriber what ever updates it has.

You just need to make sure in any case keep an Eye on the Disk size as log files will be filling up until Rest of the DB’s are up and running .

Hope it will help. 

--Mark as Answer if it resolves--

Cheers

Praveen