Description

This document explains how to obtain the Tagging Verbose Logging files to assist with investigating Enterprise Vault (EV) Compliance Accelerator (CA) Department Tagging issues. The Tagging information is kept in memory by the EVCompliance.exe process, which is a component of the EV Storage service, which is used to review each item during Archiving and Tag each item with any applicable Department Tags.

In order to see what information is contained in memory, Verbose Logging will need to be enabled, as below. This logging will also include information on each item being Tagged.

1. On the EV server edit the \Enterprise Vault\x64\EVCompliance.exe.config file as follows:

- Original lines:
              value="0" />

- Modified lines:
              value="2" />

2. Save the file and restart the EV Storage service.

3. Review the files generated by verbose Tagging logging. These logs can be found on the EV server in the \Enterprise Vault\x64\Reports\EVCompliance\Diagnostics\ sub-folder and will be listed in sub-folders labeled with the year and the month-day. As messages are tagged, they will be added to sub-folders under the year\month-day sub-folder structure. The folder structure for the Tagging Verbose Logging files for each item is the same as the folder structure in the Vault Store Partition location.

4. It is important to remember that the files generated by verbose Tagging logging are not automatically removed. After obtaining the required logs, disable Tagging verbose logging on the EV server by editing the EVCompliance.exe.config file to set the key="VerboseDiagnostics" back to value="0" and restarting EV Storage service. As the files generated by verbose Tagging logging are not automatically removed, they can be moved to an alternate location or deleted after verbose logging has been disabled.

Here is a description of each file that contains information on the CA Customers, Monitored Employees, Departments and Monitoring Policies:

- System Config: contains the entries from EnterpriseVaultDirectory.dbo.AcceleratorConfigEntry.

- CA Configuration | Customers in this configuration: contains the list of CA Customers.

- Customer X | Email Addresses -> Employee IDs: contains the list of Monitored Employees.

- Customer X | Employee ID -> Dept Memberships: contains the list of Monitored Employees and their Department memberships.

- Customer X | Dept Employee -> Sampling Policy: contains the effective monitoring policies for all Monitored Employees (including any overrides).

- Message log | Employee Depts Returned To Storage: contains Monitored Employee Department Tagging (Storage Tagging item XML Node) information used for Random Sampling.

- Message log | Dept Index Props Returned To Storage: contains Monitored Employee Department Tagging (Storage Tagging item XML Node) information used for Department Searches (non-Force Legacy Searching) and lists the KVSCA index attributes.

Additional sub-folders containing message log entries for each item as it is processed for Tagging will be created as items are Archived. In these logs, one per item, the following sections contain the Tagging information:

- The Employee Depts Returned To Storage section contains Monitored Employee Department Tagging information used for Random Sampling.

- The Dept Index Props Returned To Storage section contains Monitored Employee Department Tagging information used for Department Searches (non-Force Legacy Searching) and lists the KVSCA index attributes.

Here is a description of each node name used in the Employee Depts Returned To Storage section:

Node Name     Explanation
DS                    Departments
C                       Customer
D                       Department
E                       Employee
I                        (Mandatory Attribute) ID (Customer DB/Dept/Employee)
P                       (Mandatory Attribute) Percentage sampling rate at point of storage, expressed as a decimal.
A                       (Optional Attribute) Author
     0 (or omitted) = Recipient
     1 = Recipient and Author
     2 = Author, not listed as recipient – i.e. Author only

Example output of the Employee Depts Returned To Storage section of a correctly Tagged message diagnostic file. The explanation of each line is listed after -----.


       ----- CustomerID value.
         ----- CaseID value, Monitoring Percentage value.
           ----- PrincipalID value.
    
  


The corresponding entry in the Dept Index Props Returned To Storage section would be:


  
    
           ----- Shows a CA Tagging attribute was added.
             ----- Defines the KVSCA.Department attribute.
          501     ----- Lists the KVSCA.Department attribute value, which is the CaseID of the Department.
        
             ----- Defines the KVSCA.DeptAuthor attribute, indicating the Monitored Employee is the author of the item.
          501     ----- Lists the KVSCA.DeptAuthor attribute value, which is the CaseID of the Department containing the Monitored Employee. This could also include KVSCA.DeptRecips, which would be the corresponding recipient information.
        
      
    
  


If the Employee Depts Returned To Storage does not contain any Department information (D) or Employee information (E), and the Dept Index Props Returned To Storage does not contain any KVSCA entries, then the item was not considered eligible for Tagging.

If the Employee Depts Returned To Storage does not contain any Department information (D) or Employee information (E), and the Dept Index Props Returned To Storage does contain KVSCA entries, then the item was Tagged but not sent to CA for Random Sampling. This could be due to one or both of the following:

- The Employee is Suspended in the Employees tab.
- The Department has the Disable monitoring of employees in this department option enabled.

Notes 

- If a CA Customer has the Vault ID(s) field in EVBAAdmin not set to blank (Default Customer) or not set to target active Tagging-enabled Archives, i.e., the Vault ID(s) field is set to an invalid or dummy/fictitious VaultID entry, the CA Customer will not be used for Storage Tagging. As such, the CA Customer will not have a Customer X file listed when Tagging Verbose Logging is set to 2. Currently, the Tagging-enabled Archive types are Journal, SMTP and Shared.

- As the Storage Service is responsible for adding the Department Tagging information to the item, the Tagging data is added to the item’s Saveset (DVS) file when it is stored. Re-Indexing an item by Rebuilding the Index Volume containing that item will not change the Tagging information.