September 6, 2010 at 5:05 am
Hi All,
i need some help regarding database failover in asynchronous mode of the db mirroring
Before do the failover what are the things we need to consider.
what are the services we need to stop.
Regards,
Anjali
September 7, 2010 at 3:28 am
Hi,
You need to consider whether you have a large backlog or not at the principal, if there are transactions on the fly, etc... because the failover will be delayed until the mirror session is quiesced (ie until all the transactions committed at the principal are committed at the mirror). There are perfmon counters to monitor this: \...DatabaseMirroring\Send Queue KB, \...DatabaseMirroring\Redo Queue KB.
I would suggest to fail over to the mirror when the activity slows down, depending on your users habits (like at noon or in the evening), and switch to synchronous mode before you fail over to minimize the amount of time needed to run the recovery on the mirrored database.
David B.
September 7, 2010 at 3:31 am
Also you need to ensure that any application that connects to the principal database is made mirror-aware. You can do this in .NET by using FAILOVER PARTNER in the connection string.
You need to make sure the logins have access to the mirror, and also that any agent jobs that are needed are also failed over.
September 8, 2010 at 7:39 am
If replication is being used you may want to consider adding a PublisherFailoverPartner parameter for the various replication agents to ensure it work still works post failover.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply