Repair operations

Note the following important points before you perform any Repair operation with EVSVR:

Only consider running a Repair operation if you encounter errors when you run a Verify operation.

Before you undertake a Repair operation, make a backup copy of your databases and place the vault stores that you want to repair in backup mode. This is the case even if you have stopped the associated Storage service.

Caution:

Starting the Storage service on a damaged system can damage it further. Do not start the Storage service before you have put the problematic vault stores in backup mode. Even then, only start the Storage service if it needs to be running.

If you previously used the version of EVSVR in Enterprise Vault 8.0 SP2 or SP3 to repair any errors, you may need to perform the Repair operations again with the latest version of EVSVR. This is necessary in cases where you performed the repairs with a version of EVSVR to which you did not apply the available hotfix. However, it is unnecessary if you performed the repairs with a hotfixed version of EVSVR.

If EVSVR reports any errors when you perform a Verify operation, you can correct them by performing a Repair operation. The function of the Repair operations is to recreate missing entries in the vault store and fingerprint databases. In rare instances, a Repair operation creates new SIS parts on disk for items that have been shared many times.

A Repair operation has four Option settings from which you can select. Table: Option settings for a Repair operation describes the available settings.

Table: Option settings for a Repair operation

Option setting

Effect

BlacklistBadSISParts

Blacklists any SIS part that does not verify correctly because it does not exist, has the wrong size, or does not match the value in the fingerprint database. After you blacklist a SIS part, archiving a new item with the same SIS part causes Enterprise Vault to create a new SIS part file on disk.

Symantec does not support this option in environments where Veritas NetBackup is in use.

DatabaseLinkages

Does the following:

Verifies and corrects the reference counts of savesets and SIS parts in the collection records in the vault store databases.
Recreates any missing information on the SIS parts used by savesets in the vault store databases.
Verifies the number of references to SIS parts in the fingerprint databases against the number of references in all vault store databases in the vault store group, and corrects any that are wrong.
Reports on the number of unreferenced, unshared, and shared SIS parts, after the repair operation has completed.

DeleteSurplusReferences

Deletes the vault store and fingerprint database entries that are associated with missing items. When an item consists of multiple parts, this option also deletes from disk any remaining parts that are associated with the item.

You may find this option useful in exceptional cases, when the missing items are irretrievably lost, and you want to optimize your Enterprise Vault system by deleting the associated database entries.

When you start a DeleteSurplusReferences operation, it first performs an internal DatabaseLinkages Verify operation. The DeleteSurplusReferences operation only starts to process when the DatabaseLinkages Verify operation reports that the environment is consistent and error-free.

Before you perform a DeleteSurplusReferences operation, we recommend that you use RecreateMissingDBReferences to recreate any missing database references and ensure that the environment is consistent.

Note:

The DeleteSurplusReferences operation does not take any action unless it can conclusively determine that the items in question are missing. For example, suppose that you have migrated archived data to secondary storage by using a non-Enterprise Vault migrator, such as Veritas NetBackup. If the migrator returns generic errors such as E_FAIL or E_UNEXPECTED, EVSVR does not take any action other than to report the errors.

RecreateMissingDBReferences

Recreates any missing entries in the fingerprint databases and vault store databases.

The DeleteSurplusReferences and RecreateMissingDBReferences operations do not work with savesets and SIS parts that you have migrated to secondary storage. The reason for this is that each operation needs to determine the locations of the migrated files from the vault store and fingerprint databases. As the information in these databases may be incorrect, the operation cannot proceed effectively.

If you want to perform a Repair operation on migrated files, we recommend that you first return them to their original store location.