August 26, 2015 at 6:40 am
Hello,
I have the following mirroing setup for DR.
Prinical(ServerA) and Mirror(ServerB)
When we do a DR test we do manual failover from Principal(ServerA) to Mirror(ServerB)
Now
ServerB is Prinicpal
ServerA is Mirror
Applications do their testing against the new principal which is ServerB but dont want to take those changes or sync to ServerA(Mirror).
Is there any way to do this without breaking the mirror?
Finally It will go back to original setup after the test which Server A is Principal and Server B will be its mirror.
TIA...
August 26, 2015 at 7:11 am
Will the changes be reversed before you fail B as principle back to A?
August 26, 2015 at 7:43 am
No! They will not be. Changes made on new principal(Server B) are not needed..
Idea is When we reverse it will be in sync with Old principal...
August 26, 2015 at 8:12 am
At first blush I don't think this is possible.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
August 26, 2015 at 8:21 am
So I think the only option is to break mirror and let them do the testing..and set up the mirroring again..
August 26, 2015 at 9:04 am
why not restore a backup on the principle B and let them conduct the testing on that?
August 26, 2015 at 9:50 am
Presumably because the objective of this test was to make sure the application (and lots of other stuff) are done right and operate correctly after a mirroring failover. This is a DR test after all.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
August 26, 2015 at 10:22 am
Kevin is right..
Thanks
August 26, 2015 at 10:50 am
With that being said, what is the problem with conducting the testing on a test db that is not part of the mirroring session. If it's an exact copy, then you will know that the changes are acceptable.... Right?
August 26, 2015 at 12:23 pm
ARC211 (8/26/2015)
With that being said, what is the problem with conducting the testing on a test db that is not part of the mirroring session. If it's an exact copy, then you will know that the changes are acceptable.... Right?
This has VERY LITTLE to do with the changes that are being done inside the database during testing. It is about the MYRIAD things that accompany a full-blown DR scenario test. Your solution doesn't test that jobs get enabled, logins/users work correctly, EVERYTHING in the PRODUCTION APPLICATION ENVIRONMENT gets changed to point to the correct new server/database, etc., etc. Also that all of this is properly documented. Also that everything can successfully go back to the original server (if desired after the DR test is complete).
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply