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
DTrace troubleshooting
In the unlikely event that you experience problems when you run DTrace, Table: Potential DTrace problems gives instructions on how to resolve them.
Table: Potential DTrace problems
Problem | What to do |
|---|---|
Lines being skipped. | The first figure on each trace line is the sequence number as it was captured. If there is insufficient CPU time available to process and write entries to the log file, DTrace may skip some lines. If you are tracing an agent task, try to lower the number of threads for the task and monitor a single thread only. If there are multiple tasks of the same type (for example, Archiving), stop all but one of them. DTrace does not differentiate between the different services. |
No output on the screen after monitor command, or no trace in log file. | Ensure that you have selected the correct processes for DTracing. If you are running DTrace over Terminal Services or another remote control application that does not use the primary operating system console, note that DTrace events are written to the primary console and so may not appear when using Terminal Services. In Enterprise Vault, a message is posted in the log file to say that Terminal Services was used. |
Too much information in the log file. | You can filter and trigger DTrace content based on specific words or events. If you need to focus on the root cause of a problem, you can also limit the number of processes and threads that you monitor. |
When attempting to set trace options, "Unable to determine current trace options" is displayed. | To run DTrace on a separate application computer that has the Enterprise Vault API Runtime installed, and User Account Control (UAC) enabled, you need to run DTrace as administrator. See Running the Enterprise Vault command-line utilities with administrator privileges. |