Recovery of Enterprise Vault using data-only backups

This recovery procedure assumes that you have backed up only Enterprise Vault data, including the registry, and have not been backing up the actual system disks on your Enterprise Vault servers. If you have also been backing up the system disks on your Enterprise Vault servers then you need to follow some guidelines on how to recover your Enterprise Vault environment.

In order for the disaster recovery procedure to be successful, recent backups of the following must be available:

The following recovery procedures cover environments where Enterprise Vault has been deployed on a single server or on multiple servers. Obviously, where you are running Enterprise Vault on multiple servers you may need to perform a disaster recovery for only one of the servers. In this case, follow only the steps necessary to restore the failing server.

The recovery procedure for an individual server depends on which Enterprise Vault services and tasks were running on that server and what Enterprise Vault data was stored on that server. You need to know this information when you work through the recovery procedure.

If you are unsure which components of Enterprise Vault are running on each server, you can get the information by running the SQL script ServiceLocations.sql, which is installed in the Enterprise Vault program folder (normally C:\Program Files\Enterprise Vault).

Before you can run the script you must first restore your Enterprise Vault directory database.

More Information

About Enterprise Vault backups

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.