August 3, 2012 at 8:35 am
can any one reply
in case my mirror database is down , how we will resume the mirroring when the mirroring is configured in high safety mode ?
What are the possible ways to resume back the mirroring if a primary database went down ?
August 3, 2012 at 8:45 am
Not enough info to really answer your questions. First, you say the mirror went down, how about more information about you mean by went down? Did the server it resides crash? Did you lose connectivity to the server? What?
August 3, 2012 at 8:47 am
If you can recover the primary server intact, it will rejoin the mirroring session as the mirror, and start synchronising from the principle.
You can fail back to it if required once it's synchronised.
If it's junked, you'll need to break the mirror on the principle & follow the steps for creating a mirroring session again (backup -> restore with norecovery etc.)
August 3, 2012 at 10:07 pm
If Mirror went down or unavailable, Principal will be running 'exposed',it means it can serve the application and accept transactions, but principal cant send trns to mirror. So down side is tlog growth in principal.
We need more information on your second question. It depends on various factosr.
August 11, 2012 at 3:46 am
In high safety mode, if mirror db becomes unavailable, you need to break mirroring, since you don't need to block ur user transactions happening on ur principal which do a 2 phase commit (mirror db commit nd then principal db commit). You can setup mirroring again once ur mirror db is back online.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply