Uses the snapshot volumes in a snapshot set created by the vxsnap create command to recover a corrupted or missing SQL Server database.
Exclusive access to the SQL Server database is required for this operation.
Before using this command verify that the source volumes and the snapshot volumes are not in use.
The vxsnap restore command has the following syntax:
vxsnap -x Filename [-b] [-f] [-r] restore {RestoreType=[RECOVERY|NO_RECOVERY]} [noLogs|logFiles=tlog1,tlog2,...] writer=WriterName
The vxsnap restore command has the following attributes:
Following are examples of the main types of restore operation:
Recovering using snapshots without log replay
vxsnap -x TestDB.xml restore RestoreType=RECOVERY noLogs
This command uses the information in the TestDB.xml file to restore all the volumes in the snapshot set and brings the database online. The database is restored to the time the snapshot set was created or last refreshed.
You can use the -r option with the RECOVERY noLogs restore type if a production volume is missing due to hardware failure:
vxsnap -x TestDB.xml -r restore RestoreType=RECOVERY noLogs
This command uses the information in the TestDB.xml file to restore all the volumes in the snapshot set. Any missing volume is changed from a read-only volume to a read-write volume. After using the -r option you must explicitly assign the original drive letter/mount path of the missing production volume to the snapshot volume in the VEA. You then bring the database online.
Recovering using snapshots and log replay
vxsnap -x TestDB.xml restore RestoreType=RECOVERY logFiles=c:\backup\tLog1.bak, c:\tLog2.bak
This command uses the information in the TestDB.xml file to restore all the volumes in the snapshot set and then applies the specified transaction log backups (c:\backup\tLog1.bak and c:\tLog2.bak) and brings the database online.
Restoring snapshots and manually applying logs
vxsnap -x TestDB.xml restore RestoreType=NO_RECOVERY
This command uses the information in the TestDB.xml file to restore all the volumes in the snapshot set and leaves the database in a loading state so that backup logs can be manually restored to a specific point in time.