InfoScale™ 9.0 Storage Foundation Quick Recovery Solutions Guide for Microsoft SQL Server - Windows
- Introducing Quick Recovery for SQL Server
- About Quick Recovery snapshot solutions
- About snapshot-assisted backups
- Advantages of Quick Recovery snapshots
- Quick Recovery process
- Methods of implementing Quick Recovery snapshots for SQL Server
- About the components used in Quick Recovery
- VCS, Microsoft clustering, and Volume Replicator considerations
- About the Solutions Configuration Center
- Starting the Configuration Center
- Solutions wizard logs
- Preparing to implement Quick Recovery for SQL Server
- Implementing Quick Recovery for SQL Server with the configuration wizard
- About the Quick Recovery Configuration Wizard
- Tasks for implementing snapshot sets with the configuration wizard
- Reviewing the prerequisites
- Scheduling SQL Server 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
- Scheduling or creating an individual snapshot set for SQL Server
- Maintaining or troubleshooting snapshots
- Recovering a SQL Server database
- About recovering a SQL Server database
- Tasks for recovering a SQL Server database
- Prerequisites for recovering a SQL Server database
- Types of recovery
- Recovering using snapshots without log replay
- Recovering using snapshots and log replay
- Restoring snapshots and manually applying logs
- Recovering missing volumes
- Post-recovery steps
- Vxsnap restore command reference
- Vxsnap utility command line reference for SQL Server
Vxsnap restore command reference
The following is a summary of the vxsnap restore command syntax and attribute descriptions.
The command syntax is as follows:
vxsnap -x Filename [-b] [-f] [-r] restore
{RestoreType=[RECOVERY|NO_RECOVERY]}
[noLogs|logFiles=tlog1,tlog2,...] writer=WriterNameThe following attributes apply:
-x Filename | The metadata file created by the vxsnap create command. Each snapshot set must have a unique name for the metadata file. |
-b | Resynchronizes the volume in the background. A new snapshot cannot be made until the resynchronization is complete. |
-f | Forces the operation. Make sure the volume is not in use before using this option. |
-r | Recover even if original volume is not present. If this option is selected and the original volume is not present, the snapshot volume of the missing volume is changed from a read-only volume to a read-write volume. Use this option only with Recovery noLogs. After using this option you must explicitly assign the original drive letter/mount path of the missing volume to the snapshot volume in the VEA and then bring the database online. |
RestoreType= [RECOVERY|NO_RECOVERY] | Specifies the type of database recovery, either recovery or no recovery: RECOVERY can be used with either the noLogs or logFiles=tlog1,tlog2,.... attributes. NO_RECOVERY restores from the specified snapshot set to the time of the snapshot. No logs are applied and the database is left in an loading state so that you can manually replay backup logs to a specific point in time. |
noLogs | Database and transaction log files are restored from the snapshot set. No transaction backup logs are applied. The database is left in an operational state. |
logFiles=tlog1,tlog2,... | Transaction log backup files to be applied with the RECOVERY option to achieve a point of failure recovery. Each transaction log must have a unique name and be created using the "overwrite existing media" option within SQL Server. The database is left in an online state. |
writer=WriterName | The name for the SQL Server VSS Writer; used to located the default directory to search for the XML metadata file. Specify SQLServerWriter. |