Enterprise Vault™ Utilities
- About this guide
- ArchivePoints
- Audit Viewer
- Backtrace
- CenteraPing
- Domino Archive Exporter
- Domino Profile Document Tool
- Domino Retention Plan Tool
- DTrace
- EVDominoExchangeMigration Tool
- Running the EVDominoExchangeMigration tool
- EVDuplicateCleaner
- EVEARemovalUtility
- EVFSASetRightsAndPermissions
- EVrights
- EVservice
- EVSPShortcutManager
- EVSVR
- About EVSVR
- About the EVSVR operation settings
- Using the output from one EVSVR operation as input for another operation
- Viewing the EVSVR output log file
- Running EVSVR in interactive mode
- FSARunNow
- FSAUndelete
- FSAUtility
- 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
- ResetEVClient
- Vault Store Usage Reporter
EVSVR repair procedures
Caution:
Procedure 1
- Using the information in the Verify log file to guide you, try to recover each missing file and corrupt file.
- Rerun the Verify operation that you previously ran until you have resolved all the errors.
- If you cannot recover all the SIS parts, run the BlacklistBadSISParts Repair operation to blacklist the fingerprint database records for the missing files.
Note:
This is unnecessary if you have previously run an ArchiveObjects Verify operation with a verification level of SavesetValid. This operation has already blacklisted the database records for the missing SIS parts.
Procedure 2
- Place the vault store groups that you want to repair in backup mode.
If none of the Enterprise Vault services is running then, to place a vault store group in backup mode, you must start the Admin and Directory services only.
- On each Enterprise Vault server, stop all Enterprise Vault services and related processes. Take care to ensure that storage-related processes such as
StorageServer.exe
andStorageFileWatch.exe
have stopped. - Restart the following Enterprise Vault services only:
Enterprise Vault Admin service.
Enterprise Vault Directory service.
Enterprise Vault Indexing service (and all Indexing services that are associated with the vault store groups that you want to repair).
Storage service (optional). If the Storage service is running, users can retrieve items from the vault stores that you are repairing but Enterprise Vault does not delete existing items or archive new ones. When a vault store that you want to repair is not in backup mode, EVSVR reports the fact and does not perform the repair operation. In some cases, the Storage service must be running to process migrated files. EVSVR checks for these cases and, if the Storage service is not running but needs to be, EVSVR reports the fact and does not perform the operation.
- Run a DatabaseReferences Repair operation.
Caution:
SIS parts can be shared between different partitions in a single vault store and between partitions in different vault stores. Depending on how you have configured sharing, it is possible that the recreation of savesets in one vault store partition is dependent on SIS parts that belong to a partition of another vault store. These SIS part records must be available before you can recreate the savesets. So, the situation can arise where EVSVR cannot recreate some saveset records in a vault store database because they are dependent on SIS part records that you have yet to recreate in the fingerprint database.
To avoid this issue, use the sharing level that you have set for the vault store groups as a guide to what to repair. When the sharing level is "Share within group", you must repair the entire vault store group instead of repairing the vault stores and partitions one at a time. When the sharing level is "Share within vault store", you must repair the entire vault store instead of repairing the partitions one at a time. When the sharing level is "No sharing", or the partitions contain pre-8.0 savesets only, you can repair the partitions individually.
An additional consideration is the database that you need to repair. When this database is the vault store database, all the partitions belonging to that vault store are affected and require repair. However, if you need to repair a fingerprint database then, regardless of the sharing level that you have chosen, the entire vault store group is affected and requires repair
If any of the following conditions applies, you may want to clear the EVSVR operation setting Require Index Entries:
You use deferred indexing (FSA).
You have a backlog of index operations outstanding on any archives.
An index rebuild is running.
The Require Index Entries operation setting controls whether EVSVR repairs database records based on the existence of index entries for the items.
- If the DatabaseReferences Repair operation reports that it cannot recreate saveset records because of missing information in the Directory database, and the archive type is Exchange Mailbox or File System, perform an Archives Repair operation. This operation may be able to recreate the missing saveset records by obtaining the required information from the target Exchange system or file system volume.
- Run a Complete Verify operation with EVSVR and investigate any errors.
Depending on the nature of the errors, you may want to contact Enterprise Vault Support before you proceed.
- Cancel all archive pending items in mailboxes and revert them to their normal state.
- When the databases are in an acceptable state, start the remaining Enterprise Vault services and take the system out of backup mode.
Procedure 3
- Place the vault store groups that you want to repair in backup mode.
If none of the Enterprise Vault services is running then, to place a vault store group in backup mode, you must start the Admin and Directory services only. Do not start the Storage service.
- On each Enterprise Vault server, stop all Enterprise Vault services and related processes. Take care to ensure that storage-related processes such as
StorageServer.exe
andStorageFileWatch.exe
have stopped. Restart the following Enterprise Vault services only:
Enterprise Vault Admin service
Enterprise Vault Directory service
Enterprise Vault Indexing service (and all Indexing services that are associated with the vault store groups that you want to repair).
Storage service (only if needed). If you need to start this service, the "initial database and partition checks" section of the EVSVR log file reports the fact.
- Run a DatabaseLinkages Repair operation.
- Run a Complete Verify operation, and investigate any errors.
Depending on the nature of the errors, you may want to contact Enterprise Vault Support before you proceed.
- If the vault store and fingerprint databases are still not consistent with each other or with the storage data in the affected partitions, run a DatabaseReferences Repair operation.
- Cancel all archive pending items in mailboxes and revert them to their normal state.
- When the databases are in an acceptable state, start the remaining Enterprise Vault services and take the system out of backup mode.