Storage Foundation 8.0 Quick Recovery Solutions Guide for Microsoft Exchange - Windows
- Introducing Quick Recovery for Microsoft Exchange
- Planning a Quick Recovery snapshot solution for Exchange
- System requirements
- Methods of implementing Quick Recovery snapshots
- Recommendations and best practices
- Configuring Exchange for Quick Recovery snapshots
- Implementing Exchange snapshot sets with the configuration wizard
- About the Quick Recovery Configuration Wizard
- Scheduling Exchange snapshot sets
- Scheduling or creating an individual snapshot set for Exchange
- Maintaining or troubleshooting snapshots
- Recovering Exchange mailbox databases
- Recovering after hardware failure
- About recovery after hardware failure
- Scenario I: Database and transaction logs volumes are missing
- Scenario II: Database volumes missing, transaction logs are available
- Refreshing the snapshot set on the current disks
- Moving the production volumes to different disks and refreshing the snapshot set
- Vxsnap utility command line reference for Exchange
Post-recovery steps
After you have performed any of the recovery methods, whether point-in-time or roll forward, you should refresh the snapshot set, by performing a snapback to reattach the snapshot mirrors, and then create a new snapshot set.
See Refreshing a snapshot set .
In a Volume Replicator environment, there is an additional post-recovery step. During a point-in-time recovery in a Volume Replicator environment, the volumes on the secondary site lose write-order fidelity. DCM automatically becomes active to ensure data consistency between the primary and secondary sites. While DCM is active, the volumes cannot be expanded by either manual or AutoGrow operations. You must perform a manual resynchronization of the secondary to deactivate DCM.
To resynchronize the node at the secondary site with the node at the primary site:
- Right-click on the primary RVG and click Resynchronize Secondaries.
- Click Yes to resynchronize the nodes.