Storage Foundation 8.0.2 Quick Recovery Solutions Guide for Enterprise Vault - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2)
Platform: Windows
  1. Introducing Quick Recovery for Enterprise Vault
    1.  
      About Quick Recovery snapshot solutions
    2.  
      About snapshot-assisted backups
    3.  
      Advantages of Quick Recovery snapshots
    4.  
      Quick Recovery process
    5.  
      Enterprise Vault components supported by SFW
    6. Methods of implementing Quick Recovery snapshots
      1.  
        About the Enterprise Vault Snapshot Scheduler Wizard
      2.  
        About the Enterprise Vault Snapshot and Snapback wizards and the vxsnap utility
    7. About the components used in Quick Recovery
      1.  
        FlashSnap and FastResync
      2. Integration with Microsoft Volume Shadow Copy Service
        1.  
          VSS framework
        2.  
          VSS process
  2. Preparing to implement Quick Recovery for Enterprise Vault
    1.  
      Tasks for preparing to implement Quick Recovery for Enterprise Vault
    2. Reviewing the prerequisites
      1.  
        Storage requirements and best practices
      2.  
        Configuration requirements and best practices
    3. Configuring Enterprise Vault storage with Storage Foundation for Windows
      1.  
        Creating dynamic disk groups
      2.  
        Creating dynamic volumes
      3.  
        Pointing the databases and log paths to the SFW volumes
    4. Preparing for Enterprise Vault snapshots
      1.  
        Invoking the Enterprise Vault Management Shell
      2.  
        Configuring the Veritas Scheduler Service
      3.  
        Starting services required for Enterprise Vault Quick Recovery
  3. Scheduling or creating a snapshot set for Enterprise Vault
    1.  
      About scheduling or creating a snapshot set
    2.  
      Tasks to schedule a new snapshot set
    3.  
      Tasks to create a one-time snapshot set
    4.  
      Configuration requirements for snapshots
    5.  
      Preparing an EV snapshot mirror
    6.  
      Scheduling a new snapshot set
    7.  
      Creating a one-time EV snapshot set
    8.  
      Refreshing an EV snapshot
  4. 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
  5. Recovering Enterprise Vault components
    1.  
      About recovering an Enterprise Vault Server component
    2.  
      Tasks for recovering an Enterprise Vault Server component
    3.  
      Prerequisites for recovering an Enterprise Vault Server component
    4.  
      Types of recovery
    5.  
      Recovering using snapshots without log replay
    6.  
      Restoring snapshots and manually applying logs
    7.  
      Post-recovery steps
  6. Vxsnap utility command line reference for Enterprise Vault
    1.  
      About the Vxsnap utility
    2. Vxsnap keywords
      1.  
        vxsnap prepare
      2.  
        vxsnap create
      3.  
        vxsnap reattach
      4.  
        vxsnap restore

Restoring snapshots and manually applying logs

The following procedure uses the No Recovery option to restore the component database from the component database and log snapshot volumes. Selecting this option leaves the component database in a loading state. You can then manually apply backed up transaction logs to recover the component database to the desired point in time.

Note:

The No Recovery option is applicable only for EV database components and not for EV Index and Partitions.

You can use either the Enterprise Vault Restore Wizard from the VEA console or the vxsnap restore command.

Warning:

Before you begin, use your preferred method to backup the transaction logs within SQL Server. You must use the "overwrite existing media" option to create uniquely-named backup files.

To restore EV components using the No Recovery option in the VEA

  1. Ensure that you have backed up the transaction logs within SQL Server using the "overwrite existing media" option to create uniquely-named backup files.
  2. Close the SQL GUI, all Explorer windows, applications, consoles (except the VEA console), or any third-party system management tools that may be accessing the EV component volumes.

    It is also recommended to bring the database offline.

  3. On the VEA, navigate to the Storage Agent on the left-hand pane and click to expand Applications. Right-click Enterprise Vault and select Enterprise Vault Restore from the context menu.
  4. Review the information on the Welcome page and click Next.
  5. Select the snapshot set XML metadata file to be used for this operation and click Next.

    The XML metadata file contains all required information needed to restore the snapshot set, including the names of the database and transaction logs volumes. Click the appropriate header to sort the list of available files by File Name or Creation Time.

  6. On the Select Restore Type panel, select No_Recovery.

    Complete the information on this page as follows:

    Forcefully close any open handles

    Enable this checkbox if some EV component volumes have open handles. This will forcefully close any open handles of the volumes to be restored.

    Click Next.

  7. On the Select Enterprise Vault components for Restore operation page, select the EV component or components that you want to restore.

    The original volumes of selected components are restored from the snapshot volumes.

  8. Verify the snapshot restore specifications for No Recovery option on the summary page and click Finish.

    The component database and log snapshot volumes are restored and the component database is left in a loading state.

  9. Use your preferred method to manually restore the backup transaction logs to the desired point in time and then bring the component database back online.

To restore using the No Recovery option with the vxsnap restore command

  1. Ensure that you have backed up the transaction logs within SQL Server using the "overwrite existing media" option to create uniquely-named backup files.
  2. Close the SQL GUI and all Explorer windows, applications, consoles or third-party system management tools that may be accessing the database volumes. It is also recommended to bring the database offline.
  3. Type the command as in the following example:
    > vxsnap -x billing_DB.xml restore RestoreType=NO_RECOVERY
     Writer=EnterpriseVault site=site1/vsg=vsg1/vs=vs1 
     component="Directory DB"

    where billing_DB.xml is the name of the metadata file generated by the vxsnap create command.

    The component database and log snapshot volumes are restored and the component database is left in a loading state.

  4. Use your preferred method to manually restore the backup transaction logs to the desired point-in-time and bring the database online.