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
Using snapshot schedules in a DAG
In an Exchange 2010 DAG, you may want to create snapshot schedules on the replication (passive) nodes of the DAG as well as the active node. The VSS Schedule Snapshot wizard supports scheduling snapshots on passive copies.
Note:
The Quick Recovery Configuration Wizard does not support snapshots for a passive copy. If the active database copy switches to another node, a Quick Recovery Wizard schedule on the node that is now passive is no longer valid and scheduled snapshot operations on the passive node will fail.
For example, if the DAG contains an active database on NodeA that is being replicated to NodeB, you can set up a snapshot schedule on NodeB as well as on NodeA. Setting up a snapshot schedule on the replication node ensures that snapshots continue as scheduled if a database fails on the active node.
Exchange 2010 provides two VSS Writers as follows:
The Store Writer is available on any mailbox server and is used for backup and restore of active databases.
The Replication Writer is available on the passive node of a DAG server. The Replication Writer supports backup functionality for a selected database where the snapshot is taken against the replicated instance of the database and transaction log files. The Replication Writer is supported by SFW Flashsnap for snapshot and schedule snapshot operations but not for restore operations.
If you have set up schedules on both the active and passive nodes, the appropriate VSS writer is used automatically for the scheduled snapshot. For example, if the database on NodeA changes from an active to a passive copy, the snapshot schedule is maintained with the Replication Writer if the database remains in a healthy state. If you have set up a snapshot schedule on NodeB and the database on NodeB changes from a passive to an active copy, the snapshot schedule on NodeB continues using the Store Writer.