May 23, 2012 at 2:32 pm
I have setup mirroring between my local and DR sites.
Thanks to everyone on here for your help.
It's working fine so far, but my boss stated that they normally use the DR site to test the DB patches that come out. These patches are for the DB vendor (UltiPro) and come out pretty often.
Due to budget reasons (long story) we are forced to use the newly mirrored DR site to test the Ultipro patches/updates.
So, I will have to disable the mirroring on my DR site, then run the patches, then patch the prod server, then re-enable mirroring.
How do I re-enable the mirroring on the remote/DR box? Will it sync back up to prod? or will I have to do the entire mirroring setup process again?
June 11, 2012 at 3:17 pm
In a situation like this, I would have a separate copy of the database on the server, if disk space allows, and point your test environment to this for your patching tests. That way, you don't have to worry about the mirroring topology. But to answer your question, it is my experience that you will have to apply a couple of tlogs to the mirror site DB to get things flowing again.
June 11, 2012 at 3:27 pm
kyle.freeman (6/11/2012)
In a situation like this, I would have a separate copy of the database on the server, if disk space allows, and point your test environment to this for your patching tests. That way, you don't have to worry about the mirroring topology. But to answer your question, it is my experience that you will have to apply a couple of tlogs to the mirror site DB to get things flowing again.
If you break the mirror to apply the database changes on the mirror database (DR site), you won't be able to restart mirroring until you patch the principal database, back it up and take a tlog backup and restore those to the DR site using the NO RECOVERY option.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply