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 registry values
Enterprise Vault automatically creates the Backtrace registry values on each Enterprise Vault server. By default, Backtrace is disabled. If you want to enable Backtrace, you must edit the registry on the server on which you require tracing.
The Backtrace registry values are in the following location on each Enterprise Vault server:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\BacktraceTable: Backtrace registry values describes the Backtrace registry values.
Table: Backtrace registry values
Registry value | Description |
|---|---|
Enabled | Controls whether Backtrace is enabled (1) or disabled (0, the default setting). Note that enabling Backtrace can affect performance, so you should only do so if you experience issues with Enterprise Vault. With Backtrace enabled, each Enterprise Vault process on the server maintains Backtrace information in memory. When a trigger event occurs, Backtrace writes trace information to a log file. |
Exclude | Provides a semicolon-separated list of the events that must not trigger Backtrace. For example, 3310;3230;2776. Set RuleType to Exclude to activate this list. |
Include | Provides a semicolon-separated list of events that must trigger Backtrace. For example, 3310;3230;2776. Set RuleType to Include to activate this list. |
LogFileKeepDays | Specifies the number of days to keep Backtrace log files. Enterprise Vault automatically deletes old Backtrace log files. Backtrace checks for log files to delete when the Admin service starts and then every hour on the hour. |
LogFolderPath | Specifies the location for Backtrace log files. If no value is specified for LogFolderPath, Backtrace stores its log files in the |
MaxEventsOfEachTypePerDay | Specifies the maximum number of log files to create each day for each event. The default is 5. |
MaxEventsOfEachTypePerDayAcrossAllProcesses | Specifies the maximum number of log files to create each day for each event for all processes. The default is 40. |
MaxSizeOfAllLogsPerDayMB | Specifies the maximum total size of all Backtrace log files that can be generated in a single day. The default is 200 (megabytes). |
RuleType | Controls the manner in which Backtrace is triggered. When RuleType is set to Exclude (the default setting), all error events and warning events trigger Backtrace, except for those that are listed in the Exclude registry value. When RuleType is set to Include, all the events that are specified in the Include registry value trigger Backtrace. Other events do not trigger Backtrace. |
See the "Backtrace" chapter in the Registry Values guide for details of the Backtrace registry values.