Recovering using snapshots without log replay
The following procedure uses the Recovery option without the option to restore missing volumes. It restores the database from the snapshot set volumes to the time of the snapshot set. The database and transaction log volumes are restored but no additional transaction logs are applied.
The Recovery option can also be used to recover a database for a missing volume. For the procedure to recover a missing volume, see the following topic:
See Recovering missing volumes.
To recover a database without log replay using the VEA
- Close the SQL GUI and all Explorer windows, applications, consoles (except the VEA), or third-party system management tools that may be accessing the volumes. It is also recommended to bring the database offline.
- From the VEA console, navigate to the system where the database volumes are located.
- Right-click and click .
- Expand the system node, the Storage Agent node, and the Applications node.
- Right-click and click .
- Review the Welcome page and click .
- Select the snapshot set XML metadata file to be used for this operation and click .
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.
- On the Select Restore Type panel, click .
- You may receive a message "Some volumes in this component have open handles. Do you want to override these handles and do this restore? Click to proceed." Click , close any open handles and retry the command.
- Verify the restore specifications and click .
The database is restored to the time the snapshot set was created or last refreshed. If you took it offline earlier, bring it back online.
- The restore operation leaves the snapshot volumes snapped back to the production volumes. To ensure that another split-mirror snapshot set is immediately available, use the VSS SQL Snapshot Wizard to create a new snapshot of all the volumes in the database.
To recover without log replay using the vxsnap restore command
- Close the SQL Enterprise Manager GUI and all Explorer windows, applications, consoles, or third-party system management tools that may be accessing the volumes. It is also recommended to bring the database offline.
- Type the command as in the following example:
vxsnap -x billing_DB.xml restore RestoreType=RECOVERY noLogs
where billing_DB.xml is the name of the metadata file generated by the vxsnap create command. The volumes in the snapshot set are restored and the database is left in an operational state. The database is restored to the time the snapshot set was created or last refreshed. If you took it offline earlier, bring it back online.
- The restore operation leaves the snapshot volumes snapped back to the production volumes. To ensure that another split-mirror snapshot set is immediately available, use the vxsnap create command to create a new snapshot of all the volumes in the database.
