White Papers

BP1013 Best Practices for Enhancing Microsoft Exchange Server 2010 Data Protection and Availability 43

When the Smart Copy snapshot was recovered or the cloned volume was moved to its final location,

we resumed the Exchange Replication service activities with the command below:

[PS]>Resume-MailboxDatabaseCopy -Identity DBn\ MBXn

Finally, to quickly monitor the status of the mailbox database copies and of the Content Index (not

reported in the Exchange Management console GUI), we used one of the commands below:

[PS]>Get-MailboxDatabaseCopyStatus -Identity DBn\ MBXn

[PS]>Get-MailboxDatabaseCopyStatus -Server MBXn

Note: When using the

SeedingPostponed

option associated with a point-in-time image copy of a

mailbox database, we must ensure all the transaction logs from when the Smart Copy first occurred

are preserved and available for the final transaction log replay process.

The transaction log chain must be maintained in order to be able to perform the full recovery required.