Enterprise Vault™ Classification using the Veritas Information Classifier
- About this guide
- Preparing Enterprise Vault for classification
- Setting up Veritas Information Classifier policies
- Defining and applying Enterprise Vault classification policies
- About Enterprise Vault classification policies
- Defining classification policies
- About the PowerShell cmdlets for working with classification policies
- Associating classification policies with retention plans
- About the PowerShell cmdlets for working with retention plans
- Applying retention plans to your Enterprise Vault archives
- Running classification in test mode
- Using classification with smart partitions
- Appendix A. Enterprise Vault properties for use in custom field searches
- About the Enterprise Vault properties
- System properties
- Attachment properties
- Custom Enterprise Vault properties
- Custom Enterprise Vault properties for File System Archiving items
- Custom Enterprise Vault properties for SharePoint items
- Custom Enterprise Vault properties for Compliance Accelerator-processed items
- Custom properties for use by policy management software
- Custom properties for Enterprise Vault SMTP Archiving
- Appendix B. PowerShell cmdlets for use with classification
- About the classification cmdlets
- Disable-EVClassification
- Get-EVClassificationPolicy
- Get-EVClassificationStatus
- Get-EVClassificationTestMode
- Get-EVClassificationVICTags
- Initialize-EVClassificationVIC
- New-EVClassificationPolicy
- Remove-EVClassificationPolicy
- Set-EVClassificationPolicy
- Set-EVClassificationTestMode
- Appendix C. Classification cache folder
- Appendix D. Migrating from FCI classification to the Veritas Information Classifier
- Appendix E. Monitoring and troubleshooting
How Enterprise Vault caches the items that it submits for classification
Note:
Enterprise Vault restricts access to the cache location to the Local System account and members of the built-in Administrators group.
Before Enterprise Vault invokes the Veritas Information Classifier to process the items that it has submitted for classification, it stores plain-text versions of these items in a nominated cache location on the storage server. Each item is represented by a set of two or more plain-text files, which are as follows:
One or more files contain the text content and subject line of the item. For very large items, Enterprise Vault splits this content into multiple plain-text files.
Typically, these content files have names like the following:
EV$704348C690A05389A4292971F3C6E691~0D84E700VC.txtWhere the
VCsuffix that precedes the period indicates that this is a content file. If Enterprise Vault has created multiple content files to store the text of a large item, the rollover files have the suffixesVC_1,VC_2, and so on.In any set of rollover files, the last 5000 characters of each file appear at the start of the next file in the sequence. This feature allows Veritas Information Classifier policies that look for proximity matches to work correctly.
One file contains only the metadata properties and associated values with which Enterprise Vault has indexed the item. The file provides this information in the form property:value, as in the following example:
Indexed items can have a large number of properties, but only a subset is of interest for classification purposes. These are the properties and associated values that Enterprise Vault stores in this metadata file and that you can configure your Veritas Information Classifier policies to search for.
A metadata file has the same name as its equivalent content file, except that it has an
VMDsuffix before the period rather thanVC. For example:EV$704348C690A05389A4292971F3C6E691~0D84E700VMD.txt
By default, Enterprise Vault deletes the plain-text files from the cache folder as soon as it has finished classification, but this behavior is configurable.