To restore Enterprise Vault data, use the Backup, Archive, and Restore user interface. You must specify the NetBackup server along with the source client and the destination client to perform the restore operation.
A restore of Enterprise Vault data generally involves redirected restores. Similarly to how SQL backups occur, Enterprise Vault backups are cataloged against the Enterprise Vault server and should be restored to the SQL host. In addition, there can be other Enterprise Vault components that are cataloged against an Enterprise Vault server but the restore should happen to a different Enterprise Vault server. How to interpret the destination client from the backup view is explained later in this chapter. To perform redirected restores NetBackup requires additional steps then those in this topic. refer to the "To allow all clients to perform redirected restores" topic in the NetBackup Administrator's Guide for Windows, Volume I.
To browse the Enterprise Vault Administration Console for a destination client, the Enterprise Vault services must be up and running. You should know the destination client name before you start a restore because you must stop those services on all Enterprise Vault servers for a restore.
To specify the server, source client, destination client, and policy type for a restore operation
From the Destination client for restores list, select the client that you want. The destination client is the name of the system where you want the images to be restored. You can determine the name of the destination client from either the NetBackup Backup, Archive, and Restore user interface or the Enterprise Vault Administration Console.
You interpret the destination client based on the version of Enterprise Vault and the data type that you want to restore. The following explains how to determine the destination client of a file system or SQL data type on either Enterprise Vault 7.5 or 8.0.
From the NetBackup
Backup, Archive, and Restore user interface, expand the selected
image to see the hierarchy of the Enterprise Vault resources so you
can view the Enterprise Vault server. The destination client is
displayed within the parenthesis along side the Enterprise Vault
server. For example, a destination client named
CLIENT ONE, is displayed as EV server (CLIENT ONE) in the
The database name contains the system name in a format similar to System name\SQL instance\SQL DB name. For example, a vault store database on CLIENT TWO, would appear as a Vault Store DB (CLIENT TWO\SQLINST\database). The destination client name in this example is CLIENT TWO.
The root path of the partition that you want to restore contains the system name that you use as the destination client name. From the NetBackup Backup, Archive, and Restore user interface, you can view the partition or the index location that you want to restore. The root path of a partition or index location is shown within parenthesis along side the partition or the index location name. This root path uses the format, \\system name\Drive$\partition name. For example, a destination client named VMWIN-X64 for a closed partition named VS1 Ptn1 would appear as VS1 Ptn1(\\VMWIN-X64\Drive$\VS1 Ptn1).
The UNC restore can use any Enterprise Vault server in an Enterprise Vault site as the destination client. That is possible because the data is automatically restored to its original location because the source path is embedded in the file path. You must make sure that the Enterprise Vault user name credentials for this Enterprise Vault server, has write permissions for this UNC path. The user name credentials are specified in the NetBackup client properties.
The database name contains the system name in a format similar to System name\SQL instance\SQL DB name. For example, a vault store database on CLIENT TWO, would appear as Vault Store DB (CLIENT TWO\SQLINST\database). The destination client name in this example is CLIENT TWO.