Storage Foundation 8.0 Quick Recovery Solutions Guide for Microsoft Exchange - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (8.0)
Platform: Windows
  1. Introducing Quick Recovery for Microsoft Exchange
    1.  
      About Quick Recovery snapshot solutions
    2.  
      Advantages of Quick Recovery snapshots
    3.  
      Quick Recovery process
    4. About the components used in Quick Recovery
      1.  
        FlashSnap and FastResync
      2. Integration with Microsoft Volume Shadow Copy Service
        1.  
          The VSS framework
    5.  
      About the Solutions Configuration Center
    6.  
      Starting the Configuration Center
    7.  
      Solutions wizard logs
  2. Planning a Quick Recovery snapshot solution for Exchange
    1. System requirements
      1.  
        Storage requirements
    2. Methods of implementing Quick Recovery snapshots
      1.  
        About the Quick Recovery Configuration Wizard
      2.  
        About the VSS Exchange Snapshot Scheduler Wizard
      3.  
        About the VSS Snapshot and Snapback wizards and the vxsnap utility
    3.  
      Planning your Quick Recovery solution
    4.  
      Backup types for snapshot sets
    5.  
      About logs
    6. Recommendations and best practices
      1.  
        Recommendations for Exchange storage configuration
      2.  
        Recommendations for maintenance and backups
      3.  
        SFW cluster considerations
      4. Exchange 2010 Database Availability Group (DAG) considerations
        1.  
          Using snapshot schedules in a DAG
        2.  
          Guidelines for creating passive copy snapshots in a DAG
        3.  
          Recovery in a DAG
      5.  
        Microsoft cluster considerations
      6.  
        Volume Replicator considerations
  3. Configuring Exchange for Quick Recovery snapshots
    1.  
      Tasks for configuring Exchange storage
    2.  
      Reviewing the prerequisites
    3.  
      Reviewing the configuration for Exchange 2010
    4.  
      Creating dynamic disk groups
    5.  
      Creating dynamic volumes
    6.  
      Pointing the database and log paths to the SFW volumes
  4. Implementing Exchange snapshot sets with the configuration wizard
    1. About the Quick Recovery Configuration Wizard
      1.  
        About snapshot sets
      2. About snapshot templates
        1.  
          Templates and multiple components
        2.  
          Templates and schedule start dates
    2.  
      Tasks for implementing snapshot sets with the configuration wizard
    3.  
      Reviewing the prerequisites
    4. Scheduling Exchange snapshot sets
      1.  
        System Selection panel details
      2.  
        Instance Selection panel details
      3.  
        Mount Details panel details
      4.  
        Synchronizing Schedules panel details
      5.  
        Template Selection panel details
      6.  
        Number of Snapshot Sets panel details
      7.  
        Snapshot Volume Assignment panel details
      8.  
        Snapshot Schedule panel details
      9.  
        Specifying snapshot schedule details
      10.  
        Summary panel details
      11.  
        Template Implementation panel
    5.  
      Administering or troubleshooting scheduled snapshots
  5. Scheduling or creating an individual snapshot set for Exchange
    1.  
      About scheduling or creating an individual snapshot set
    2.  
      Tasks to schedule a new snapshot
    3.  
      Tasks to create a one-time snapshot set
    4.  
      Reviewing the prerequisites
    5.  
      Preparing the snapshot mirrors
    6.  
      Scheduling a snapshot set
    7.  
      Creating a one-time snapshot set
    8. Refreshing a snapshot set
      1.  
        Reattaching the split-mirror snapshots
  6. Maintaining or troubleshooting snapshots
    1.  
      Viewing the status of scheduled snapshots
    2.  
      Troubleshooting scheduled snapshots
    3.  
      Deleting or modifying schedules
    4.  
      Synchronizing schedules after adding a cluster node
  7. Recovering Exchange mailbox databases
    1.  
      About recovery using Quick Recovery snapshots
    2.  
      Tasks for recovery using Quick Recovery snapshots
    3.  
      Prerequisites for recovery
    4.  
      Recovery using an Exchange 2010 passive copy snapshot in a Database Availability Group (DAG)
    5.  
      Recovery for Exchange 2010 using the VSS Restore Wizard
    6.  
      Recovery for Exchange 2010 using the vxsnap utility
    7.  
      Post-recovery steps
  8. Recovering after hardware failure
    1. About recovery after hardware failure
      1.  
        Recovery scenarios
      2.  
        Recovery tasks
    2.  
      Tasks for recovering after hardware failure
    3.  
      Reviewing the prerequisites
    4.  
      Reviewing the sample configuration for Exchange 2010
    5. Scenario I: Database and transaction logs volumes are missing
      1.  
        Identifying the missing volumes (Scenario I)
      2.  
        Deleting missing volumes from Storage Foundation
      3.  
        Replacing hardware and adding disks to the dynamic disk group
      4.  
        Changing the drive letter or mount points of the snapshot volumes
      5.  
        Restoring the Exchange 2010 mailbox database to the point in time
      6.  
        Refreshing the snapshot set (Scenario I)
    6. Scenario II: Database volumes missing, transaction logs are available
      1.  
        Identifying the missing volumes (Scenario II)
      2.  
        Deleting missing volumes from Storage Foundation
      3.  
        Replacing hardware and adding disks to the dynamic disk group
      4.  
        Changing the drive letter or mount points of the snapshot volumes
      5.  
        Restoring the Exchange 2010 mailbox database to the point in time
      6.  
        Recovering the Exchange 2010 mailbox database to the point of failure
      7.  
        Refreshing the snapshot set (Scenario II)
    7.  
      Refreshing the snapshot set
    8. Refreshing the snapshot set on the current disks
      1.  
        Reattaching healthy snapshot volumes
      2.  
        Clearing the snapshot association for volumes whose drive letters or mount points were reassigned
      3.  
        Creating snapshot mirrors of volumes whose drive letters or mount points were reassigned
      4.  
        Creating the new snapshot set
    9. Moving the production volumes to different disks and refreshing the snapshot set
      1.  
        Reattaching healthy snapshot volumes
      2.  
        Clearing the snapshot association for volumes whose drive letters or mount points were reassigned
      3.  
        Adding mirrors to volumes whose drive letters or mount points were reassigned
      4.  
        Creating snapshot mirrors of volumes whose drive letters or mount points were reassigned
      5.  
        Creating the new snapshot set
  9. Vxsnap utility command line reference for Exchange
    1.  
      About the vxsnap utility
    2. Vxsnap keywords
      1.  
        vxsnap prepare
      2.  
        vxsnap create
      3.  
        vxsnap reattach
      4. vxsnap restore
        1.  
          Recovery after hardware failure

Creating the new snapshot set

Create the new snapshot set from the VEA console or from the command line.

To create the snapshot set from the VEA console

  1. From the VEA console, navigate to the system where the production volumes and snapshots mirrors are located.
  2. Expand the system node, the Storage Agent node, and the Applications node.
  3. Choose one of the following:
    • Right-click Exchange and click VSS Exchange Snapshot.

    • Optionally, if replication is enabled in an Exchange 2010 DAG and you want to create a snapshot on the replication node, right-click Exchange Replica and click VSS Exchange Snapshot.

  4. In the wizard, review the Welcome page and click Next.
  5. Specify the snapshot set parameters as follows and then click Next:

    Select Component for snapshot operation

    Select the component for the snapshot set.

    For Exchange 2010, the component is a mailbox database.

    Directory

    Enter a directory location for the XML file or accept the default. The XML file is stored by default in the directory shown on the screen.

    Note:

    The XML file for the snapshot must be stored separately from the volumes that are included in the snapshots, otherwise a restore will fail.

    In a clustered server environment, the XML file must be saved on shared storage to be available from all nodes in the cluster. To accomplish this, either edit the directory path in the Directory field for this wizard screen or use a text editor to create a text file named "redirect.txt." This text file should contain a single text line specifying the full path to the location of the metadata file, for example, G:\BackupSets. Save the redirect.txt file in the default directory C:\Program Files\Veritas\Veritas Volume Manager\VSSXML on each node of the cluster.

    Note:

    You must not use the volume name or volume path in the redirect.txt file that is involved in the snapshot. If the volume name or path for the snapshot is used, then a restore will fail.

    Note that if your Exchange 2010 mailbox database is configured under a VCS cluster, then you can store the snapshot set metadata file in a file share path by configuring a file share resource. This is to avoid configuring extra shared volumes to store the snapshot set file, which is available once the mailbox database fails over. You can also specify the file share path in the redirect.txt file.

    Snapshot set

    Enter a name for the snapshot set. The snapshot set metadata XML file is stored under this name.

    Select snapshot type

    Select the snapshot type.

    Full Backup is typically used for backup to tape or other storage media. It does the following:

    • Creates a copy of the selected component

    • Runs Eseutil to check for consistency before truncating the logs

    • Truncates the transaction logs

    Copy is typically used for Quick Recovery. It creates a copy of the storage group, but does not truncate the transaction logs. Optionally check Run Eseutil with the Copy option to check the snapshot for consistency.

  6. In the Change Attributes panel, optionally change the attributes for the snapshot volumes as follows and click Next:

    Snapshot Volume Label

    Displays the read-only label for the snapshot volume.

    Drive Letter

    Optionally, click a drive letter and select a new choice from the drop-down menu.

    Plex

    Optionally, click a plex and select a new choice from the drop-down menu.

  7. Optionally, in the Synchronized Snapshot panel, select the secondary hosts for which you want to create synchronized snapshots. Either double-click on the host name or click the Add option to move the host into the Selected Secondary Hosts pane. To select all the available hosts, click the Add All option. The VSS wizard creates synchronized snapshots on all the selected secondary hosts.

    This panel is displayed only in an environment using Volume Replicator. Otherwise, you will be directly taken to the Schedule Information panel.

  8. Review the specifications of the snapshot set and click Finish.

To create the new snapshot set from the command line

  • Type the vxsnap create command. The exact command will vary depending on your environment.

    The complete syntax of the vxsnap create command is:

    vxsnap [-x <filename>] create [source=<volume>]
    [/DriveLetter=<driveLetter>][/DrivePath=<drivePath>][/Newvol=<n
    ewVolName>][/Plex=<plexName>]...writer=<writerName>
    component=<componentName>[backuptype=<backuptype>][-E][-O][-C]
    [secHosts=<secondary hosts>]

    The WriterName and ComponentName must be included in the command. The option to assign drive letters or mount points is useful for tracking volumes and for scripting purposes. Any text string that contains spaces must be enclosed in quotation marks.

    Note:

    If you have scripted the refresh process, you will need to change the snapshot volume names assigned by your script using the option Newvol=NewVolName. For instance, if DB1 volume was missing, and the volume DB1snap was used in the restore process, it will retain the volume name DB1snap.Your script will not be able to assign DB1snap as the new snapshot volume name in step 4 when using the vxsnap create command.

    See vxsnap create.