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
Format of the EVEARemovalUtility output and log files
The output of EVEARemovalUtility appears in the command prompt window, unless you specify the -l parameter to redirect the output to a log file.
The log file name format is EVEARemovalUtility--timestamp.log, where timestamp indicates when the log file was created. timestamp has the format yyyymmddmmsscc, where cc indicates hundredths of a second. For example, the log file EVEARemovalUtility--20100907142304.log was created at 14:23 and 04 hundredths of a second on 7th September 2010.
The following command generates a log file that lists the details of the extended attributes for the files in a folder and its subfolders:
EVEARemovalUtility.exe \\server1\e$\folder1 -d -s -l
Here is an example of the output from this command:
Extended Attribute Removal Utility.
Veritas Enterprise Vault.
Copyright (c) 2010. Veritas Technologies LLC.
List extended attributes from \\server1\e$\folder1
---------------------------------------------------------------
Filename ExtAttrSTATE Details
---------------------------------------------------------------
##
\\server1\e$\folder1\file1.txt PRESENT <EA1-Value>, <EA2-Value2>
\\server1\e$\folder1\file2.txt NOT PRESENT
\\server1\e$\folder1\file3.txt PRESENT <EA1-Value3>
\\server1\e$\folder1\file4.txt PRESENT <EA1-Value>
\\server1\e$\folder1\file5.txt NOT PRESENT
\\server1\e$\folder1\file6.doc NOT PRESENT
\\server1\e$\folder1\file7.txt NOT PRESENT
\\server1\e$\folder1\file8.doc NOT PRESENT
\\server1\e$\folder1\subfolder\file9.doc PRESENT <CS-12>, <AUTHOR-P1>
\\server1\e$\folder1\subfolder\file91.doc NOT PRESENT
##
Summary
---------------------------------------------------------------
Present Not present Start time End time
---------------------------------------------------------------
4 6 6-10-2010 At 20:51:22.137 6-10-2010 At 20:51:22.387
Total elapsed time : 0 hours 0 mins 0 seconds 249 msecIf you omit the -d parameter, the output omits the names and the values of the extended attributes.
If required, you can edit the contents of a log file before submitting it for processing with the -f parameter. For example, you may want to remove the extended attributes from all of the files that are listed in the example log file, except file4.txt. You can edit the log file to delete the line for file4.txt, and then submit the log file for processing.
Note:
Do not to change the format of the lines that are bounded by the ## characters, otherwise the utility may fail to read the file list correctly.
When you use the -r parameter to remove extended attributes and you also include the -q parameter, the command produces "quiet" output. The output then includes only summary information about the number of processed files.