Veritas Enterprise Vault™ Setting up Domino Server Archiving
- About this guide
- Setting up Domino mailbox archiving
- Preparation for Domino mailbox archiving
- Configuring Domino targets, tasks and policies in Enterprise Vault
- Adding Domino Server archiving targets
- Configuring mailbox policies for Domino mailbox archiving
- Using customized shortcuts for Domino mailbox archiving
- Configuring desktop policies for Domino mailbox archiving
- Adding a Provisioning Group when setting up Domino mailbox archiving
- Installing Enterprise Vault extensions for Notes and DWA clients
- About Enterprise Vault clients for Notes and DWA clients
- Granting Execution Control List permissions when setting up Notes and DWA clients
- Changes made by EVInstall.nsf when setting up Domino mailbox archiving
- How to edit automatic messages after installing Domino mailbox archiving
- Setting up a Vault Cache for offline users
- Setting up Domino Journaling archiving
- How to configure clients when setting up Domino Journal archiving
- Configuring filtering
- Configuring custom filtering
- Configuring registry settings for Domino custom filtering
- About custom filtering ruleset files
- About controlling default custom filtering behavior
- About the general format of ruleset files for custom filtering
- About rule actions for custom filtering
- About message attribute filters for custom filtering
- About the general format of Custom Properties.xml
- About content categories
- Defining how custom properties are presented in third party applications
Summary of default behavior for custom filtering
Table: Example custom filter and custom property configurations shows ten different configurations for custom filtering and properties.
The resulting actions taken by archiving tasks in each case are described in Table: Resulting actions for example configurations.
In all cases it is assumed that the appropriate registry settings have been configured to enable the archiving task for custom filtering. The following configuration entities are considered:
Named XML ruleset files in the folder,
Enterprise Vault\Custom Filter Rules
. In the example cases shown,Marketing.xml
andSales.xml
are named ruleset files for the provisioning groups Marketing and Sales respectively.The examples in this section show named ruleset files for provisioning. You can also create named ruleset files specific Domino journaling locations.
The default ruleset file for all types of archiving,
Enterprise Vault\Custom Filter Rules\Default Filter Rules.xml
.The custom properties file,
Enterprise Vault\Custom Filter Rules\Custom Properties.xml
, with custom properties defined for indexing.Content category entries in the
Custom Properties.xml
file.The registry setting, IGNORENODEFAULT, with a value of 1.
Table: Example custom filter and custom property configurations
Case | Custom properties file exists | Default content category defined | Named ruleset file exists: Marketing.xml | Named ruleset file exists: Sales.xml | Default ruleset file exists | IGNORENODEFAULT set |
---|---|---|---|---|---|---|
1 | No | No | No | No | No | No |
2 | No | No | No | No | No | Yes |
3 | No | No | Yes | No | No | No |
4 | No | No | Yes | No | No | Yes |
5 | No | No | Yes | No | Yes | No |
6 | No | No | Yes | No | Yes | Yes |
7 | Yes | No | No | Yes | No | No |
8 | Yes | No | No | Yes | No | Yes |
9 | Yes | Yes | No | Yes | No | No |
10 | Yes | Yes | No | Yes | No | Yes |
Table: Resulting actions for example configurations
Case | Resulting action |
---|---|
1 | An error is written to the event log and the archiving task stops, because custom filtering is enabled but there is no ruleset file or custom property file. |
2 | Missing defaults are ignored and both mailboxes are archived according to the default mailbox policy. |
3 | An error is reported for the Sales provisioning group, because no default ruleset file or custom properties file exists. |
4 | Marketing mailboxes are archived according to rules in |
5 | Marketing mailboxes are archived according to rules in No custom properties are indexed. Content categories cannot be used. |
6 | As for case 5. The fact that IGNORENODEFAULT is set makes no difference. |
7 | An error is reported for Marketing mailboxes, because there is no applicable named ruleset file or default ruleset file. |
8 | Marketing mailboxes are archived according to rules in the default mailbox policy. Sales mailbox are archived according to the rules in |
9 | All messages are archived from Marketing mailboxes and custom properties indexed. Messages are archived from Sales mailboxes according to the rules in |
10 | As for case 9. The fact that IGNORENODEFAULT is set makes no difference. |
More Information