InfoScale™ 9.0 Storage Foundation Quick Recovery Solutions Guide for Microsoft SQL Server - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Introducing Quick Recovery for SQL Server
    1.  
      About Quick Recovery snapshot solutions
    2.  
      About snapshot-assisted backups
    3.  
      Advantages of Quick Recovery snapshots
    4.  
      Quick Recovery process
    5. Methods of implementing Quick Recovery snapshots for SQL Server
      1.  
        About the Quick Recovery Configuration Wizard
      2.  
        About the VSS Snapshot Scheduler Wizard
      3.  
        About the VSS Snapshot and Snapback wizards and the vxsnap utility
    6. 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
    7.  
      VCS, Microsoft clustering, and Volume Replicator considerations
    8.  
      About the Solutions Configuration Center
    9.  
      Starting the Configuration Center
    10.  
      Solutions wizard logs
  2. Preparing to implement Quick Recovery for SQL Server
    1.  
      Tasks for preparing to implement Quick Recovery for SQL Server
    2. Reviewing the prerequisites
      1.  
        Storage requirements and best practices
      2.  
        Configuration requirements and best practices
    3.  
      Reviewing the configuration
    4. Configuring SQL Server 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
  3. Implementing Quick Recovery for SQL Server with the configuration wizard
    1. About the Quick Recovery Configuration Wizard
      1.  
        Backup types for 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 SQL Server 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
  4. Scheduling or creating an individual snapshot set for SQL Server
    1.  
      About scheduling or creating an individual snapshot set
    2.  
      Tasks to schedule a new snapshot set
    3.  
      Tasks to create a one-time snapshot set
    4.  
      Reviewing the prerequisites
    5.  
      Preparing the snapshot mirrors
    6.  
      Scheduling a new snapshot set
    7.  
      Creating a one-time snapshot set
    8. Refreshing a snapshot set
      1.  
        Reattaching the split-mirror snapshots
  5. 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
  6. Recovering a SQL Server database
    1.  
      About recovering a SQL Server database
    2.  
      Tasks for recovering a SQL Server database
    3.  
      Prerequisites for recovering a SQL Server database
    4.  
      Types of recovery
    5.  
      Recovering using snapshots without log replay
    6.  
      Recovering using snapshots and log replay
    7.  
      Restoring snapshots and manually applying logs
    8. Recovering missing volumes
      1. Preparing for the recovery
        1.  
          Reassigning the drive letter or mount points of the missing volumes to the snapshot volumes
        2.  
          Replacing hardware and adding disks to the dynamic disk group
      2.  
        Performing the recovery
    9.  
      Post-recovery steps
    10.  
      Vxsnap restore command reference
  7. Vxsnap utility command line reference for SQL Server
    1.  
      About the vxsnap utility
    2. Vxsnap keywords
      1.  
        vxsnap prepare
      2.  
        vxsnap create
      3.  
        vxsnap reattach
      4.  
        vxsnap restore

Creating a one-time snapshot set

Creating a one-time snapshot or snapshot set is a two-step process as follows:

  • The first step is to prepare the snapshot mirrors for the database volume or volumes. If you are creating a snapshot set after a snapback to refresh existing snapshot mirrors, you can skip this step.

    See Preparing the snapshot mirrors.

  • The second step uses either the VSS SQL Snapshot Wizard or the vxsnap create command to create the snapshot set by detaching the snapshot mirrors from the original volumes. This step creates separate on-host snapshot volumes as well as a snapshot set XML file to store the application and snapshot volume metadata.

    The VSS SQL Snapshot Wizard and vxsnap create command integrate with VSS to quiesce the database and then simultaneously snapshot the volumes in the database. This snapshot is done while the database is online and without disrupting the database operations. The resulting snapshot set provides a complete picture of the database at the point in time the command is issued.

The VSS SQL Snapshot Wizard can be run from either a local system or a remote node. The vxsnap utility must be run from the local system.

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 SQLServerWriter node.
  3. Expand the system node, the Storage Agent node, and the Applications node. If the SQL node is not shown, start the SQL Server VSS Writer service and then select the Storage Agent node and refresh the VEA display (Actions > Refresh).
  4. Expand the SQL node.
  5. Right-click the instance and click VSS Snapshot.
  6. In the wizard, review the Welcome page and click Next.
  7. Specify the snapshot set parameters as follows and then click Next:

    Select Component for snapshot operation

    Select the database for the snapshot set.

    Directory

    The wizard creates the snapshot set metadata XML file. The XML metadata 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.

    There are two ways to change the XML file location.

    First, edit the directory path in the Directory field for this wizard screen. Second, change the XML file location. Use a text editor to create a text file named redirect.txt. This text file should contain a single text line specifying the Universal Naming Convention (UNC) path to the location of the XML file, for example, \\ServerName\SharedFolderName. Save the redirect.txt file in the default directory C:\Program Files\Veritas\Veritas Volume Manager\VSSXML.

    If the product is installed on the D drive, then the path will be the same as above, but on the D drive.

    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.

    Snapshot set

    Enter a name for the snapshot set, for example, billing or accept the default name. The wizard generates a default snapshot set name that includes the term "SnapshotSet", component name, date, and time.

    Select snapshot type

    Select the snapshot type.

    You can specify that snapshots be created as either a Full backup or Copy backup type. Either type can be used to restore a database. However, if you want to replay logs in SQL Server as part of restoring a database, a Full backup needs to have been created earlier. When replaying logs, you can replay from the time of the last Full backup. A Copy backup does not affect this sequence of log replay and therefore is often used as an "out of band" copy for purposes such as testing or data mining.

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

    Volume Name

    Displays the name of the volume.

    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.

  9. On the Synchronized Snapshot panel (Volume Replicator only), 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 (Volume Replicator). Otherwise, you will be directly taken to the Schedule Information panel.

    See Volume Replicator Administrator's Guide.

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

To create the snapshot set from the command line

  • Type the command, as in the following example:
    > vxsnap -x billing_DB.xml create
        source=L:/Newvol=billing_data
        source=M:/Newvol=billing_log
        writer=SQLServerWriter component=billing_DB
        backuptype=full

    where billing_DB.xml is a name you assign the metadata file that is used to reattach the snapshot set or to recover using that snapshot set.

    The complete syntax of the vxsnap create command is:

    vxsnap -x filename create [-gDynamicDiskGroupName]
    source=Volume [/DriveLetter=DriveLetter]
    [/DrivePath=DrivePath] [/Newvol=NewVolName][/Plex=PlexName]...
        writer=WriterName component=ComponentName
        [server=ServerName] [instance=InstanceName]
        [backuptype=FULL|COPY][-O]

    The WriterName and ComponentName are required. The component name is the name of the SQL database. The option to assign drive letters or mount points is useful for tracking volumes and for scripting purposes. You can use either a Full backup or Copy backup for restoring from a snapshot (recovery). However, if you want to replay logs in SQL Server as part of restoring a database, a Full backup needs to have been created earlier. When replaying logs, you can replay from the time of the last Full backup. A Copy backup does not affect this sequence of log replay and therefore is often used as an "out of band" copy for purposes such as testing or data mining.

    Note:

    Any text string that contains spaces must be enclosed in quotation marks.