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

Configuration requirements and best practices

Review the following configuration requirements and best practices:

  • Configuring Enterprise Vault to work with Storage Foundation requires that Microsoft Windows PowerShell 1.0 or later be installed.

  • The system and boot volumes must reside on a separate disk (Harddisk0) from the dynamic volumes used for the Enterprise Vault components and split-mirror snapshots.

  • Disk groups must be of a Storage Foundation 4.0 or later version. Upgrade any disk groups created using an earlier version of Volume Manager for Windows before creating Quick Recovery snapshots.

  • Quick Recovery snapshots are supported only on volumes belonging to an SFW dynamic disk group. They are not supported on volumes belonging to a Microsoft Disk Management Disk Group. For more information on Microsoft Disk Management Disk Groups, see Storage Foundation Administrator's Guide.

  • Database and transaction logs must be stored on disks within a single dynamic disk group.

  • Database and transaction logs should be on separate disks so that disk failure does not affect anyone of these filegroups.

  • User-defined database and transaction logs may not be stored in the same volume as the Enterprise Vault program files or system data files.

  • Locate snapshot volumes on separate disks from any database and log volumes so that the snapshot process does not interfere with database operations.

  • Locate the snapshot volumes for each component on separate disks from snapshots of other components. This is recommended so that the process of creating the snapshot of one component does not interfere with any operations on another component.

    Warning:

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

  • Transaction logs should always be configured in a redundant layout. The preferred software layout is RAID 0+1 (mirrored striped) volumes as this provides better read and write performance than RAID 1 (mirrored) alone. The transaction log will generate the most I/O and thus should use the highest performance disks available.

  • The preferred layout for the database is hardware RAID 5, software RAID 1 (mirrored with logging enabled) or software RAID 0+1 (mirrored striped).

    Note:

    FlashSnap is not supported for software RAID 5 volumes.