White Papers

BP1013 Best Practices for Enhancing Microsoft Exchange Server 2010 Data Protection and Availability 38
We simulated a scenario where a DAG environment was running and was already protected by the
Smart Copy snapshots on both nodes. In this context we had the advantage of starting the recovery
process from the pre-existing snapshots on the node that owned the mailbox database passive copy.
Test Details for one database with the seeding process using the iSCSI SAN network:
Details Reseeding of the database using a Smart Copy snapshot
Workload User workload applied or not
Key indicator Host resources impact
The steps needed to recover the required data on the target volume were as follows:
1. Create the definition of the mailbox database copy
2. Select the most recent SAN snapshot of the volume containing the target database mailbox
copy
3. Proceed with a Soft recovery procedure by ASM/ME (if not already done)
4. For safety, proceed with a Checksum verification procedure by ASM/ME (if not already done)
5. Mount the Smart Copy snapshot to the target host
6. Resume the regular activity of Exchange Replication service for this mailbox database copy
7. Wait while all the transaction logs (generated between the point-in-time when the Smart
Copy was taken and the copy was resumed) are transferred and replayed to the passive
database