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
Backtrace examples
Table: Sample values when RuleType is set to Exclude shows an example of Backtrace registry values when RuleType is set to the default of 'Exclude'.
Table: Sample values when RuleType is set to Exclude
Registry value | Setting | Comments |
|---|---|---|
Enabled | 1 | Backtrace is enabled. Backtrace is triggered according to the setting of RuleType. |
RuleType | Exclude | Default of 'Exclude' for RuleType. All warnings and errors trigger Backtrace except for those that are listed in the Exclude value. |
Exclude | None | By default there is no value for Exclude. All errors and warnings trigger Backtrace. |
Include | 3310;3230;2776 | Backtrace ignores the Include setting because RuleType is set to 'Exclude'. |
LogFileKeepDays | 7 | The default is to keep log files for seven days. |
LogFolderPath | None | Default of no value for LogFolderPath. By default, Backtrace writes log files to the Backtrace subfolder of the Enterprise Vault |
MaxEventsOfEachTypePerDay | 5 | Default of 5 for MaxEventsOfEachTypePerDay. Backtrace creates log files for a maximum of five identical events each day for each process. The counter is reset when a process is restarted. |
Table: Sample values when RuleType is set to Include shows an example of Backtrace registry values when RuleType is set to 'Include'.
Table: Sample values when RuleType is set to Include
Registry value | Setting | Comments |
|---|---|---|
Enabled | 1 | Backtrace is enabled. Backtrace is triggered according to the setting of RuleType. |
RuleType | Include | Each of the events that are listed in Include triggers Backtrace. |
Exclude | None | Backtrace ignores the Exclude setting because RuleType is set to 'Include'. All errors and warnings trigger Backspace. |
Include | 3310;3230;2776 | A semicolon-separated list of the events that trigger Backtrace when RuleType is set to 'Include'. No other events trigger Backtrace. |
LogFileKeepDays | 7 | The default is to keep log files for seven days. |
LogFolderPath | None | Default of no value for LogFolderPath. By default, Backtrace writes log files to the |
MaxEventsOfEachTypePerDay | 5 | Default of 5 for MaxEventsOfEachTypePerDay. Backtrace creates log files for a maximum of five identical events each day for each process. The counter is reset when a process is restarted. |