May 26, 2011 at 1:43 pm
Hi All, Here is our scenario. We have one server (for example Server A) which is acting as Publisher and another SQL server (For Example Server B) which is acting as Distributor and subscriber.
We have several tables which are getting updated on subscription database through several where conditions.
We are looking for Disaster Prespective, What needs to be done and what are that thing need to be considered/backedup in order to recover from a disaster for following conditions.
Condition 1: If Server A is totally Crashed abd down.
Condition 2: If Server B is totally Crashed and down.
Any help will be greatly appreciated!!! We are new to SQL Replication and this is our first replication system. We want to make our environment protected and make sure that we will be able to restore in case of disaster.
Thanks!
May 26, 2011 at 4:55 pm
Several factors here. Is the subscriber a complete, replicated copy? Is this merge replication with changes occuring on both sides? Either way the following generally applies.
Obviously you will have a maintenance plan on both servers with adequate backups/transaction log backups occurring and being transferred off of the server. 🙂 5-15 minute transaction log backups will normally suffice.
You also need to ensure the publications and logins are scripted regularly. I use powershell SQLPSX tasks to do this.
Assuming you have up to date backups of the published db and the distribution database along with the scripts that should be sufficient to rebuild a replication topology.
May 31, 2011 at 8:09 pm
Thanks,
It will be Transactional replication with Pull from Subscription server.
So as per your reply,
- We need to backup distribution database
- We need to backup publisher database
- We neeed to backup scripts for replication
We need above things to rebuild replication? correct?
Can you please send me any documentation on how to rebuild replication in case of disaster if possible?
Thanks a lot for your reply...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply