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
Note on reviewing the messages in the EVSVR log files
When an interactive mode operation has finished, it displays a message to indicate whether it was successful. If the operation failed for any reason, check the log file for more information.
Note that the underlying Enterprise Vault components may record a message in the event log in certain cases when errors are encountered, but the operation may still be considered a success. The event log messages that the Enterprise Vault code generates when EVSVR calls it are redirected to the log file, and they do not appear in the event log. So, it is important to review the log file to determine if any errors occurred. For example, the file may contain an event log-related message like the following, even though the overall status of the operation was "Completed operation with success":
2010-07-14 19:13:00 Event Output: Failed to recall a Saveset from its Collection. Reason: Failed to extract the file from the CAB file. The file name is not in the CAB file index.