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
- 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
- ResetEVClient
- Vault Store Usage Reporter
Backtrace file name format
The Backtrace log file names comprise the following items, separated by underscores:
The name begins with "EV".
Local date and time in the format YYYYMMDD_HHMMSSmmm
Server name. The name of the server on which the process is running.
Process name. The name of the process that is traced.
Process ID. The ID of the process that is traced.
Event IDs. The name contains a maximum of five IDs of the most recent events that are in the file.
The following example shows a log file name when error event 8938 from the Admin service triggers Backtrace on server "MYSERVER". The trigger event 8938 is followed by error event 8942:
EV20110908_095919784_MYSERVER_AdminService(2872)_8938E_8942E.log
By default, Backtrace stores its log files in the Backtrace
subfolder of the Enterprise Vault Reports
folder. You can edit the LogFolderPath registry value to specify a different location.