Enterprise Vault™ Utilities
- About this guide
- Audit Viewer
- Domino Archive Exporter
- Domino Profile Document Tool
- Domino Retention Plan Tool
- EVDominoExchangeMigration Tool
- Running the EVDominoExchangeMigration tool
- EVEARemovalUtility usage examples
- About EVSVR
- About the EVSVR operation settings
- Report operations in EVSVR
- Verify operations in EVSVR
- Repair operations in EVSVR
- Using the output from one EVSVR operation as input for another operation
- Viewing the EVSVR output log file
- Running EVSVR in interactive mode
- About using FSAUtility with Dell EMC Celerra/VNX placeholders
- FSAUtility options
- NTFS to Centera Migration
- Permissions Browser
- Policy Manager (EVPM)
- Sections and keynames in Policy Manager initialization file
- Policy Manager initialization file examples
- About using the Provisioning API to run Policy Manager scripts
- Provisioning API scripting properties for Policy Manager scripts
- Provisioning API Advanced settings for Policy Manager scripts
- Vault Store Usage Reporter
Risk of data loss when you run certain EVSVR Repair operations
We strongly recommend that you contact Veritas Technical Support before you run any of these operations.
The circumstances in which you can experience data loss include the following:
The DatabaseReferences or Archives operation has failed to recreate all the missing records in the fingerprint databases and vault store databases. This issue typically arises when some of the Archive records and ArchiveFolder records in the Directory database are missing.
You have specified an inappropriate date range for the DatabaseReferences or Archives operation. This can lead to the situation where the operation does not process some savesets and SIS parts that it ought to repair.
You have selected the optionfor the DatabaseReferences or Archives operation. However, some savesets do not have index information because one or more of the following conditions applies:
You have chosen to defer indexing (that is, Enterprise Vault does not index files as they are archived).
You have a backlog of index operations.
An index rebuild is in progress.
You have run a DatabaseLinkages operation after a DatabaseReferences or Archives operation that failed to repair all the repairable items.
You have run a DeleteSurplusReferences operation after a DatabaseReferences or Archives operation that failed to repair all the repairable items.
You have not run a DatabaseLinkages operation after a DatabaseReferences or Archives operation that successfully completed.
For these reasons, it is important to ensure that the DatabaseReferences or Archives operation has repaired all the repairable items before you proceed with any other Repair operation.
For example, you can experience data loss when you run a DeleteSurplusReferences operation after a DatabaseReferences operation. This situation can arise if the DatabaseReferences operation has failed to repair all the saveset records in the vault store databases for some reason. When you subsequently run the DeleteSurplusReferences operation, certain SIS parts may incorrectly appear to be unused because the associated saveset records that should reference them were not repaired. For these SIS parts, the DeleteSurplusReferences operation then deletes both the corresponding records in the fingerprint database and any uncollected SIS part files on disk. For this reason, we recommend that you only run a DeleteSurplusReferences operation when you know that your environment is consistent and any missing items are irrecoverable.