In his article, “Exchange 2010 Mailbox Moves and Mailbox Resiliency”, Ross Smith discusses certain data loss scenarios that can exist even though Exchange Server 2010 includes continuous replication block mode. Continuous replication block mode was added to Exchange Server 2010 to provide greater protection from mailbox data losses.

Ross Smith specifically describes scenarios that result from a high logging generation rate environment. These scenarios often occur during mailbox move operations. One example given is when a mailbox has been moved from an active database to a second passive database. Then, right after the move, the server hosting the primary (or active) database fails. As a result of the primary server failure, the second database is then activated. But because the “AttemptCopyLastLogs” operation is unable to complete, the recently copied mailbox will not have a complete copy of the pre-move mailbox.

He then further discusses the Data Guarantee API and some of the API calls that can be used to help maintain and ensure successful mailbox move operations. Some of the calls mentioned include:  Check Replication Health and Check Replication Flush.

Continue reading Mailbox Replication Service