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
- About the EVDominoExchangeMigration tool
- Client requirements for the EVDominoExchangeMigration tool
- Adding the EVDominoExchangeMigration tool to the Windows Server firewall exceptions list
- EVDominoExchangeMigration tool and Binary Tree
- Using Quest Notes Migrator for Exchange and the EVDominoExchangeMigration tool
- Requirements for other migration software with the EVDominoExchangeMigration tool
- Running the EVDominoExchangeMigration tool
- EVDuplicateCleaner
- EVEARemovalUtility
- EVFSASetRightsAndPermissions
- EVrights
- EVservice
- EVSPShortcutManager
- EVSVR
- About EVSVR
- Starting EVSVR
- EVSVR commands
- EVSVR application states
- Creating an EVSVR operation file
- Editing an EVSVR operation file in which you have enabled checkpointing
- Running an EVSVR operation
- 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
- Improving EVSVR performance when processing CAB collections
- FSARunNow
- FSAUndelete
- FSAUtility
- NTFS to Centera Migration
- About NTFS to Centera Migration
- Managing migrator jobs using NTFS to Centera Migration
- Creating migrator jobs using NTFS to Centera Migration
- Deleting active jobs using NTFS to Centera Migration
- Deleting source files after migration using NTFS to Centera Migration
- NTFS to Centera Migration log files
- Permissions Browser
- Policy Manager (EVPM)
- About Policy Manager
- Policy Manager syntax
- Saving a Policy Manager initialization file as a Unicode file
- Policy Manager initialization file syntax
- Sections and keynames in Policy Manager initialization file
- [Directory] section of the Policy Manager initialization file
- [Archive] section of the Policy Manager initialization file
- [ArchivePermissions] section of the Policy Manager initialization file
- [Filter] section of the Policy Manager initialization file
- [Mailbox] section of the Policy Manager initialization file
- [Folder] section of the Policy Manager initialization file
- [PublicFolder] section in the Policy Manager initialization file
- [PSTdefaults] section in the Policy Manager initialization file
- [PST] section in the Policy Manager initialization file
- [PSTcheckpoint] section in the Policy Manager initialization file
- [NSFDefaults] section in the Policy Manager initialization file
- [NSF] section in the Policy Manager initialization file
- [NSFCheckPoint] section in the Policy Manager initialization file
- Policy Manager initialization file examples
- Policy Manager initialization file example 1
- Policy Manager initialization file example 2
- Policy Manager initialization file example 3
- Policy Manager initialization file example 4: PST migration
- Policy Manager initialization file example 5: NSF migration
- Policy Manager initialization file example 6: folder permissions
- About using the Provisioning API to run Policy Manager scripts
- ResetEVClient
- Vault Store Usage Reporter
[NSFCheckPoint] section in the Policy Manager initialization file
Do not include this section, which Policy Manager generates automatically.
Policy Manager creates an [NSFCheckPoint] section when it writes a new initialization file. This section contains information about the new initialization file, and statistics about the run of Policy Manager that created the file.
In some cases the values that Policy Manager writes to the new initialization file depend on the setting of MigrationMode on the [NSFDefaults] section.
Shows the creation date and time of the new initialization file.
Shows the number that was appended to the name of the new initialization file that Policy Manager generates. This number is incremented each time you run Policy Manager.
Shows the path and the file name of the original initialization file.
This value is generated when Policy Manager runs in Process mode.
Shows the number of NSF files that are listed in this initialization file, but cannot be migrated. For each NSF file that cannot be migrated, Policy Manager writes JobStatus = Failed in the relevant [NSF] section of the new initialization file.
This value is generated when Policy Manager runs in Report mode.
Shows the number of NSF files that are listed in this initialization file, but are not ready. For each NSF file that is not ready, Policy Manager writes DoNotProcess = True in the relevant [NSF] section of the new initialization file.
This value is generated when Policy Manager runs in Process mode.
Shows the number of NSF files that are listed in the initialization file, and contain one or more items that cannot be migrated. All these items have been placed in a folder that is called NSF Migration Failed Items in the NSF file. If Policy Manager is interrupted, NSFPartialCount also includes the number of NSF files that were being processed when the interruption took place.
For each NSF file that is partially processed, Policy Manager writes JobStatus = Partially_Processed in the relevant [NSF] section of the new initialization file.
This value is generated when Policy Manager runs in Process mode.
Shows the number of NSF files that are listed in the initialization file, and were successfully migrated on the previous Policy Manager run. These files are still listed in the initialization file. However, for each NSF file that is processed, Policy Manager writes JobStatus = Processed in the relevant [NSF] section of the new initialization file. This setting prevents Policy Manager from processing the files again when you use the new initialization file.
This value is generated when Policy Manager runs in Process mode.
Shows the number of NSF files that were listed in this file but ignored in the last Policy Manager run. Policy Manager ignores any NSF files with the following settings:
JobStatus = Processed
DoNotProcess = True
For each NSF file that is ignored because DoNotProcess is set to True, Policy Manager writes JobStatus = Unprocessed in the relevant [NSF] section of the new initialization file.