SQL Server Performance Forum – Threads Archive

Primary Failback

Hi guys, I have a scenario in which I have a primary DB. I maintain either standby secondary DB using log shipping or I maintain secondary DB using replication. And say my primary DB dies. So I can failover to secondary DB without any problems. My problem is what are my options if I want to failback to my original primary DB once I bring it up. The data has changed in the secondary DB in the time, I bring my primary DB up and online. Please let me know this ASAP and also the impact on performance of the solution to accomplish this. Thanks
-Rajeev Lahoty

Refer to the books online for Log shipping role changes and this Technet documenthttp://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/logship2.mspx which will guide you.
I don’t think there will be any performance issues in getting this process workout. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Satya, Thanks for your reply. I had read it and implemented it and had faced the same problem while reversing roles. I mean I had to delete maintenance plans on both the servers and set up the log shipping again. This is not what I want. I don’t want to set up log shipping again once I change the roles. Is there any other way out? Thanks
-Rajeev Lahoty

To accomplish a full log shipping role reversal, you only need to set up log shipping from the new primary server to the new secondary server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

]]>