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
Editing an EVSVR operation file in which you have enabled checkpointing
When an operation for which you have enabled checkpointing is stopped, you can edit the settings in its operation file. However, if you change the selected operation type (Report, Verify, or Repair) or option, you cannot continue the execution of the operation file from the latest checkpoint; you must start the operation from the beginning. The EVSVR output log file reports this as follows:
However, you can change the other operation properties, such as the date range or number of threads, and then continue the operation from the latest checkpoint.