May 26, 2010 at 9:33 am
I want to know what one can do if database mirroring is configured for disaster recovery and high availability. One cannot mirror system databases, but what can one do to mitigate this restriction.
Also, after a failover to the mirror. Do connections now have to reflect the new server name or can one change DNS settings so that applications can still carry on connecting to the database. Also, if failover has been carried out and applications are now running on the mirror, how can one failback to the principal assuming its now up and running without loosing data.
Any ideas.
May 26, 2010 at 10:06 am
You should read the white papers on how this works to better understand. DB Mirroring is designed for DR and the clients can be configured in the connection string to automatically switch to the mirror server. Switching back is easy once you ensure that mirroring is working in the opposite direction.
May 26, 2010 at 10:07 am
Start with this, and all the stuff it links to.
http://msdn.microsoft.com/en-us/library/ms189852.aspx
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply