April 30, 2008 at 7:17 am
Hi all,
I've implemented database mirroring for a project at work. Everything went smoothly and it's working great. I now have to write a disaster recovery plan for every eventuality that could occur. No where on the net can i find any disaster recover info for database mirroring. There is no information on how to recover from the basic stuff like if the principal database fails and the mirror takes over, if the principal database is corrupt and needs rebuilt how do i do this?
Maybe I'm searching for the wrong thing or i just thick!
Please can anyone refer me to somewhere i can find details of this
Many thanks
Lee
April 30, 2008 at 1:01 pm
Lee,
I haven't done a lot of work with this, but when there's a failover, the mirror becomes the principal and the principal is the downed mirror. There is a priority setting between the servers.
This doc has a lot of scenarios in it: http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
May 1, 2008 at 2:23 am
Thanks for the link! that was great for the various scenarios although again it refers to bringing back the principal database but doesnt describe how to do this. Thanks for the scenario info though
May 1, 2008 at 9:18 pm
You'd fail back to the original principal the same way you failed over in the first place.
If your original principal was completely hosed and needed an OS rebuild, you would have to recreate database mirroring, using the DR server as the original principal to start with. Once the original principal is rebuilt and database mirroring established, do a failover.
Or you could plan an outage to kick everyone out of the database, remove database mirroring and do a backup/restore or file copy from DR then attach to [new] production. Then recreate database mirroring.
Like a lot of things in SQL Server, there are many ways to get the job done.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply