Veritas 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
Improving EVSVR performance when processing CAB collections
When the following EVSVR operations process CAB collection files, they can cause high CPU usage and take a long time to complete:
DatabaseLinkages Verify
DatabaseLinkages Repair
DatabaseReferences Repair
If you experience this problem, you can markedly improve performance by creating an index for each fingerprint database that you want to verify or repair. Then, after you have run the EVSVR operation, you can either remove the index or leave it in place for when you next run the operation
Note:
Creating an index for a fingerprint database can marginally reduce archiving performance and increase the size of the database. However, you may consider these to be acceptable drawbacks if you run EVSVR regularly.
To improve EVSVR performance when processing CAB collections
- On the SQL Server computer, start SQL Server Management Studio.
- In the left pane of the SQL Server Management Studio window, expand the tree until the required fingerprint database is visible.
- Click the fingerprint database, and then click New Query.
Do one of the following:
To create an index, enter the following query and then click Execute:
DECLARE @RC int DECLARE @Create bit DECLARE @ByteRangeStart tinyint DECLARE @ByteRangeEnd tinyint DECLARE @debug bit SET @Create = 1 SET @ByteRangeStart = 0 SET @ByteRangeEnd = 255 SET @debug = 0 /* Set to 1 to view debug information */ EXECUTE @RC = [dbo].[Factory_EVSVR_Index_01] @Create, @ByteRangeStart, @ByteRangeEnd, @debug
To remove an existing index, enter the following query and then click Execute:
DECLARE @RC int DECLARE @Create bit DECLARE @ByteRangeStart tinyint DECLARE @ByteRangeEnd tinyint DECLARE @debug bit SET @Create = 0 SET @ByteRangeStart = 0 SET @ByteRangeEnd = 255 SET @debug = 0 /* Set to 1 to view debug information */ EXECUTE @RC = [dbo].[Factory_EVSVR_Index_01] @Create, @ByteRangeStart, @ByteRangeEnd, @debug