August 23, 2013 at 4:40 pm
We are setting up Database Mirroring in our lab without a Witness. We are able to get the principal and mirror servers synchronized. When we manually failover, through their UI, everything works smoothly. Failing back, again through the UI, works.
When we simulate a complete Principal shutdown, our Mirror stays in the Disconnected/In Recovery state. In order to get it out of that state and usable we need to run the following two commands:
ALTER DATABASE <database_name>
SET PARTNER OFF
RESTORE DATABASE <database_name> WITH RECOVERY
Now to restart mirroring we have to go through the whole process of creating a full backup, tail backup, copy that over to the mirror (the original principal), apply the backup, and go through the Mirroring Wizard, start mirroring, and then, finally, failover to the original primary.
I am just wondering if, in the above, is how it is supposed to be?
August 24, 2013 at 3:17 am
ALTER DATABASE <db name> SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS instead of PARTNER OFF
Forces the mirror online without destroying the mirroring config entirely.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 28, 2013 at 9:15 am
That was what I was looking for. Thank you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply