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
- Planning your Quick Recovery solution
- Backup types for snapshot sets
- About logs
- Recommendations and best practices
- Configuring Exchange for Quick Recovery snapshots
- Implementing Exchange snapshot sets with the configuration wizard
- About the Quick Recovery Configuration Wizard
- Tasks for implementing snapshot sets with the configuration wizard
- Reviewing the prerequisites
- Scheduling Exchange snapshot sets
- System Selection panel details
- Instance Selection panel details
- Mount Details panel details
- Synchronizing Schedules panel details
- Template Selection panel details
- Number of Snapshot Sets panel details
- Snapshot Volume Assignment panel details
- Snapshot Schedule panel details
- Specifying snapshot schedule details
- Summary panel details
- Template Implementation panel
- Administering or troubleshooting scheduled snapshots
- Scheduling or creating an individual snapshot set for Exchange
- Maintaining or troubleshooting snapshots
- Recovering Exchange mailbox databases
- About recovery using Quick Recovery snapshots
- Tasks for recovery using Quick Recovery snapshots
- Prerequisites for recovery
- Recovery using an Exchange 2010 passive copy snapshot in a Database Availability Group (DAG)
- Recovery for Exchange 2010 using the VSS Restore Wizard
- Recovery for Exchange 2010 using the vxsnap utility
- Post-recovery steps
- Recovering after hardware failure
- About recovery after hardware failure
- Tasks for recovering after hardware failure
- Reviewing the prerequisites
- Reviewing the sample configuration for Exchange 2010
- Scenario I: Database and transaction logs volumes are missing
- Identifying the missing volumes (Scenario I)
- Deleting missing volumes from Storage Foundation
- Replacing hardware and adding disks to the dynamic disk group
- Changing the drive letter or mount points of the snapshot volumes
- Restoring the Exchange 2010 mailbox database to the point in time
- Refreshing the snapshot set (Scenario I)
- Scenario II: Database volumes missing, transaction logs are available
- Identifying the missing volumes (Scenario II)
- Deleting missing volumes from Storage Foundation
- Replacing hardware and adding disks to the dynamic disk group
- Changing the drive letter or mount points of the snapshot volumes
- Restoring the Exchange 2010 mailbox database to the point in time
- Recovering the Exchange 2010 mailbox database to the point of failure
- Refreshing the snapshot set (Scenario II)
- Refreshing the snapshot set
- Refreshing the snapshot set on the current disks
- Moving the production volumes to different disks and refreshing the snapshot set
- Reattaching healthy snapshot volumes
- Clearing the snapshot association for volumes whose drive letters or mount points were reassigned
- Adding mirrors to volumes whose drive letters or mount points were reassigned
- Creating snapshot mirrors of volumes whose drive letters or mount points were reassigned
- Creating the new snapshot set
- Vxsnap utility command line reference for Exchange
Volume Replicator considerations
In a Volume Replicator environment, observe the following precautions:
Store the XML metadata file and other snapshot related files on a volume that is included in the replicated data set so that the metadata file is available at the secondary site.
Additionally, if VCS is used, store the metadata file on a volume in the cluster disk group associated with the Exchange database so that the metadata file is available from all nodes in the cluster.
During a point-in-time recovery, 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.
See Post-recovery steps.