Please enter search query.
Search <book_title>...
Veritas Enterprise Vault™ Utilities
Last Published:
2017-07-28
Product(s):
Enterprise Vault (12.1)
- 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
- Provisioning API scripting properties for Policy Manager scripts
- Provisioning API Advanced settings for Policy Manager scripts
- Provisioning API Interface methods for Policy Manager scripts
- ResetEVClient
- Vault Store Usage Reporter
About the checkpointing information in the EVSVR log file
When you start a checkpointed operation for the first time, the log file reports that EVSVR has created a new checkpoint file. For example:
If you choose to continue an operation from the last checkpoint, EVSVR appends the new log information to the existing log file and provides information about the last checkpoint. For example:
When EVSVR completes a checkpointed operation, the log file reports the fact. For example:
If you issue a continue command for a checkpointed operation that has already completed, the log file provides the following information: