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
vxsnap reattach
Reattaches and resynchronizes the snapshot volumes in the snapshot set to the original database volumes.
Note:
Make sure that the snapshot volumes are not in use before using this command.
The vxsnap reattach command has the following syntax:
vxsnap -x <filename> [-f][-b] reattach writer=<writername> [secHosts=<secondary hosts>]
The vxsnap reattach command has the following attributes:
-x <Filename> | The file created by the vxsnap create command. Each snapshot set must have a unique name for the metadata file. Note: This file is deleted after the reattach operation has completed successfully. |
-f | Forces the reattach. Make sure the volume is not in use by another application before using this command. Use this option with care. |
-b | Resynchronizes the volume in the background. A new snapshot cannot be made until the resynchronization is complete. |
writer=<writername> | Unique ID of the VSS writer, for example, "Microsoft Exchange Writer" or the GUID for the writer. If you plan to be able to do a roll-forward recovery to the point of failure, you must specify the writer. |
secHosts=<secondary hosts> | Applies to Volume Replicator environment only. Comma separated list of secondary hosts on which a synchronized snapshot is to be taken. |
The following is an example of the vxsnap reattach command:
vxsnap -x snapdata.xml reattach writer="Microsoft Exchange Writer"
This command uses the information in the snapdata.xml file to reattach and resynchronize all the volumes in the snapshot set. This xml file is deleted after the reattach operation has completed successfully. The snapshot volumes remain synchronized with the original volumes until the vxsnap create command is issued.