Ensure that you have prepared for the recovery first.
See Preparing for the recovery.
To recover a database with one or more missing volumes 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.
- Expand the system node, the Storage Agent node, and the 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 and select .
- 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 snapshot of the missing volume is changed from a read-only volume to a read-write volume.
- If you have not already done so, in the VEA, ensure that the drive letter or mount path of the missing production volume is assigned to the snapshot volume.
- Bring the database online.
If the production volume was missing, the snapshot volume is now changed to the production volume. The database is restored to the time the snapshot set was created or last refreshed.
- 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 a database with one or more missing volumes 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 -r restore RestoreType=RECOVERY noLogs
where billing_DB.xml is the name of the metadata file generated by the vxsnap create command.
The snapshot of the missing volume is changed from a read-only volume to a read-write volume.
- If you have not already done so, in the VEA, reassign the drive letter or mount path of the missing volume to the snapshot volume.
- Bring the database online.
If the production volume was missing, the snapshot volume is now changed to the production volume. The database is restored to the time the snapshot set was created or last refreshed.
- 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.