Restoring snapshots and manually applying logs


Restoring snapshots and manually applying logs
Prev	Recovering Enterprise Vault components	Next

The following procedure uses the No Recovery option to restore the component database from the component database and log snapshot volumes. Selecting this option leaves the component database in a loading state. You can then manually apply backed up transaction logs to recover the component database to the desired point in time.

Note:

The No Recovery option is applicable only for EV database components and not for EV Index and Partitions.

You can use either the Enterprise Vault Restore Wizard from the VEA console or the vxsnap restore command.

Warning:

Before you begin, use your preferred method to backup the transaction logs within SQL Server. You must use the "overwrite existing media" option to create uniquely-named backup files.

To restore EV components using the No Recovery option in the VEA

Ensure that you have backed up the transaction logs within SQL Server using the "overwrite existing media" option to create uniquely-named backup files.
Close the SQL GUI, all Explorer windows, applications, consoles (except the VEA console), or any third-party system management tools that may be accessing the EV component volumes.
It is also recommended to bring the database offline.
On the VEA, navigate to the Storage Agent on the left-hand pane and click to expand Applications. Right-click Enterprise Vault and select Enterprise Vault Restore from the context menu.
Review the information on the Welcome page and click Next.
Select the snapshot set XML metadata file to be used for this operation and click Next.
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, select No_Recovery.

Complete the information on this page as follows:

Forcefully close any open handles

Enable this checkbox if some EV component volumes have open handles. This will forcefully close any open handles of the volumes to be restored.

Click Next.
On the Select Enterprise Vault components for Restore operation page, select the EV component or components that you want to restore.
The original volumes of selected components are restored from the snapshot volumes.
Verify the snapshot restore specifications for No Recovery option on the summary page and click Finish.
The component database and log snapshot volumes are restored and the component database is left in a loading state.
Use your preferred method to manually restore the backup transaction logs to the desired point in time and then bring the component database back online.

To restore using the No Recovery option with the vxsnap restore command

Ensure that you have backed up the transaction logs within SQL Server using the "overwrite existing media" option to create uniquely-named backup files.
Close the SQL GUI and all Explorer windows, applications, consoles or third-party system management tools that may be accessing the database 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=NO_RECOVERY
 Writer=EnterpriseVault site=site1/vsg=vsg1/vs=vs1 
 component="Directory DB"
```
where billing_DB.xml is the name of the metadata file generated by the vxsnap create command.

The component database and log snapshot volumes are restored and the component database is left in a loading state.
Use your preferred method to manually restore the backup transaction logs to the desired point-in-time and bring the database online.

Prev	Up	Next
Recovering using snapshots without log replay	Home	Post-recovery steps