• dbasachinkumar (4/5/2012)


    If both principal and mirror are synchronized then manual failover is not the issue but in case if databases are not synchronized and for drill or in distar we need to bring mirror force fully up in that case user will start using mirror which is principal now once of old principal is up we want that to take load.How we can achieve that without data loss that is the main issue by what methods we can overcome this situation.

    Please help.

    Regards,

    Sachin

    If you force service, when the principal comes back online, mirroring will not restart automatically. You have to issue the RESUME command. The data on the principal that was not synched to the mirror when you forced service is not lost until the mirroring session is resumed. You have the option to remove mirroring instead or create a database snapshot and bring the original principal online so you can query it for data not on the original mirror (current principal) and manually insert the missing data yourself into it.


    My blog: SQL Soldier[/url]
    SQL Server Best Practices:
    SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]