Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Issue:Mirroring Sync in Asynchronous Mode Expand / Collapse
Author
Message
Posted Friday, April 12, 2013 10:09 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, July 17, 2014 1:37 PM
Points: 1,612, Visits: 1,536
houming1982 (4/12/2013)
If data loss happened when failed over to the mirror server, and there were lots of transactions happened on the mirror server during the downtime of principal server, HOW TO FAILOVER back to the principal server on keeping Consistency of data?


If a fail over is issued either manual or automatic, there is no chance for data loss. Data loss will not occur. Data loss is only possible when you use FORCE_SERVICE_ALLOW_DATA_LOSS to force the mirror to come online. When the mirroring session is resumed after forcing service, and data that was on the principal and not yet synched to the mirror at time of failure will be lost and the new mirror (original principal) will be synched with the new principal.




My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server 2008
Principal DBA: Outerwall, Inc.
Also available for consulting: SQL DBA Master
Post #1441785
Posted Friday, April 12, 2013 1:00 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 7:32 AM
Points: 809, Visits: 1,157
I agree with Robert Davis, once mirroring is suspended, it is not started automatically, you have to issue "ALTER DATABASE DBName SET PARTNER RESUME", then only the mirroring will start again.
Post #1441860
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse