Backup Exec for Windows Servers (BEWS) Enterprise Vault (EV) Agent Backup and Recovery Procedures Best Practices.

Article:TECH54605  |  Created: 2009-01-31  |  Updated: 2014-01-08  |  Article URL
Article Type
Technical Solution


Backup Exec for Windows Servers (BEWS) Enterprise Vault (EV) Agent Backup and Recovery Procedures Best Practices.


Enterprise Vault (EV) Backup Configurations can be divided into 3 categories:
1. Everything (EV + SQL + Indexes) on one server ... this is very rare combination and is not recommended because of the heavy I/O Load that it would place on the one machine.
2. EV is on one system and  SQL is on a different machine... very common ...  EV + multiple SQL Servers which is not very common but could be there in customer environments.
3. EV on a separate server + SQL on a separate server + EV partitions on a NAS device such as a NetApp filer or a a EMC filer.

Restore Privilege:

Only user who is either the EV service account or is in the Domain Admins group, is authorize to do restores. This user should have Restore privileges.

Handling NTFS Data:

Restore of Index Locations and Partitions are actually done by the NTFS agent.

Handling SQL Data:

Restore of Directory Db, Monitoring DB and Vault Store DB are actually done by the SQL agent.

Running Recovery-tools post-restore:

When restoring EV entities underneath the Vault Store individually the data is likely to become out-of-sync. In order to fix any data inconsistency within a Vault store or between data and indexes, EV Recovery tools need to be run with appropriate recovery options.

EV Server Redirection

User can change the machine name between two backups, thereby changing the EV server name too. EV Agent allows restores to be done even when the machine name has been changed.

EV Entity Redirection

The agent supports limited redirection of EV entities underneath an EV Server. Vault Stores Partitions, Index folders and Vault Store Databases may be restored to the same EV entities only.

EV Agent - Redirection Options 
  • Option to specify SQL Server and Instance for Directory and Monitoring DB redirection.
  • Option to specify EV Server Name for EV Server redirection.
Option to specify Path for Index Root Paths (Index Locations) redirection.

Implicit Restore:

When some EV entities are restored, certain other EV entities need to be restored implicitly. This approach helps making the recovery process fast by getting crucial entities as closely synched as possible. In Open Partition restore is based on the selected Partition being currently open. It is not based on the partition's status when it was backed up.

EV Restore Support Limitations:
  • EV does not provide any specific restore support apart from the Read-only Mode.
  • Currently, EV does not expose the interface to create or modify EV entities externally. So, the agent cannot recreate deleted EV entities to be restored. Hence, the user will have to create appropriate entities through existing EV mechanism (UI) before selecting such EV entities for successful restore.
In EV, there is no facility to allow changing file system paths for Partitions and Index Folders. There is no API or UI facility to do this. However the user may change these in the Directory DB manually. The agent will allow automatic redirection to the new path referring the current configuration to facilitate restores from previous backups.


Restore Failed: "File or Directory Not Found"

Reason: The Partition or Vault DB would not exist on the target EV server. Please create the entity using EV and then rerun the restore job.

Restore of Directory DB/Monitoring DB fails with error "Database Query Failure"

Reason: The database were in use and hence could not be replaced. Please use the EV restore options page to force restore Directory and Monitoring DB.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices