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
Creating dynamic volumes
Create a volume for the log files and an additional volume for each database.
To create a dynamic volume from the VEA console
- Launch Veritas Enterprise Administrator from the Apps menu on the Start screen.
Select a profile if prompted and connect to the appropriate host.
- In the tree, expand the system name, expand the storage agent, and then expand Disk Groups.
- Right-click on the disk group in which to create the volumes (for example, Exch-DG1) and click New Volume.
- In the Welcome panel of the New Volume Wizard, click Next.
- Select the disks for the volume as follows:
Make sure the appropriate disk group name appears in the Group name drop-down list.
For example, Exch-DG1.
For Site Preference, leave the setting as Siteless (the default).
Specify automatic disk selection (the default) or manual disk selection. To manually select disks, use the Add button to move the appropriate disks to the Selected disks list. Manual selection of disks is recommended.
You may also check Disable Track Alignment to disable track alignment for the volume. Disabling Track Alignment means that the volume does not store blocks of data in alignment with the boundaries of the physical track of the disk.
Click Next.
- Specify the parameters of the volume:
Enter the volume name (for example, DB1-tlogs).
Note:
A volume name is limited to 18 ASCII characters. It cannot contain spaces, slash mark (/), backslash (\), exclamation point (!), angle brackets (< >), or equal sign (=). Also, a period cannot be the first character in the name.
Enter the size.
Select the layout.
Select the appropriate mirror options.
Click Next.
- Assign a drive letter to the volume (for example, I: for the DB1-tlogs volume) and click Next.
If you are assigning a drive letter to a replication volume in an Exchange 2010 DAG, use the same drive letter as the volume on the active node.
- Create a file system as follows:
Make sure that the Format this volume checkbox is checked and clickNTFS.
Select an allocation size.
Accept the default file system label, which is the same as the volume name you entered previously or enter a file system label.
If desired, select Perform a quick format.
Click Next.
- Review the volume specifications, then click Finish to create the new volume.
- Repeat the previous steps as necessary to create volumes for the databases. For example, create volumes DB1 and DB2.
To create a volume from the command line
- Type the CLI command, as in the following example:
vxassist [-b] -gExch-DG1 make DB1-tlogs 200 DriveLetter=I
This example command will create a 200 MB volume named DB1-tlogs on drive letter I: in the Exch-DG1 dynamic disk group.
Note:
This command does not format the volume (a file system is not created on the volume). You must use the operating system format command to format the volume.
- Modify and repeat this command as necessary to create volumes for the databases.