... well, perhaps some sophistication. The setup:
Server A publishes to server B via transactional replication. Server A is to be shut down while some electrical work is done. So we fail over to server B for a couple days. My underpowered brain says to shut down replication, possibly fail over well in advance of the power outage.
Then, when the electrical work is done and server A is restarted: 1) stop work on server B, 2) ?copy? the database on B to A (I suppose after deleting it from A), and 3) redoing the replication from scratch.
Can anyone recommend a better process?
I am very gratefull for any enlightenment.
If you're on SQL Server 2005, you can consider a 2 node Peer to Peer transactional replication. Transactional Replication with queued updating or bidirectional replication may also fit your scenario if you're on SQL Server 2000. For more information, please visit SQL Server Books Online about those topics.
With above replicaiton configuration, there is no need for you to redo replication setup from scratch, just stop/restart replication should be enough
Zhiqiang Feng
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment