June 22, 2016 at 9:57 am
Hi experts please provide your inputs on below scenario
we have Server (A,B-one n/w)C--on diffrent n/w
A-> B Mirrorg Configured
A-> C Logshipping Configured
if AB server/n/w fails our intention is to route application to C server..
Now If AB n/w down so mirroring& Log shipping will break
what are the steps to work DB on secondary server only(if primary fails) & (one DB with One Login only)
once AB servers Up then how to restart Both Mirroring & Logshipping again ..
Your inputs are highly appreciated..
June 22, 2016 at 3:37 pm
Hi James, are you asking for the failover steps for both scenarios as well as how to "re-sync" them after a failover?
June 23, 2016 at 1:52 am
Yes
Kindly update the steps
June 23, 2016 at 5:35 am
jamessdba (6/22/2016)
Hi experts please provide your inputs on below scenariowe have Server (A,B-one n/w)C--on diffrent n/w
A-> B Mirrorg Configured
A-> C Logshipping Configured
if AB server/n/w fails our intention is to route application to C server..
Now If AB n/w down so mirroring& Log shipping will break
what are the steps to work DB on secondary server only(if primary fails) & (one DB with One Login only)
once AB servers Up then how to restart Both Mirroring & Logshipping again ..
Your inputs are highly appreciated..
if network A-B is down it's extremely likely network A-C will be unavailable too unless you have some extensive network design in place!
In the log shipping scenario you would need to run the role reversal procedure, this is documented at the following link
https://msdn.microsoft.com/en-gb/library/ms178117(v=sql.120).aspx
Also, check this article too
https://msdn.microsoft.com/en-us/library/ms187016(v=sql.120).aspx
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 24, 2016 at 4:27 am
Thanks Perry
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply