Previous Topic: OverviewNext Topic: What Data is Purged?


Purging Strategies

Event purging strategies

After installing CA DataMinder, you need to turn on database purging to periodically remove events from CA DataMinder databases. You need a separate purging strategy for your CMS, which holds event data for your entire organization, and one or more strategies for your gateways and client machines. To implement these strategies, you need to configure the CMS, common gateway and common client machine policies.

CMS purges

Compliance-seeking organizations need to implement an event purging strategy that meets regulatory requirements on the storage and retention of historical communications. Typically, this strategy requires scheduled purges. These run at regular intervals and are configurable in the CMS machine policy.

If you set up scheduled purging, you must also specify the minimum retention period for captured items before they become eligible for purging. For example, you may be required to retain e-mails for a minimum of three years.

Gateway and client machine purges

Events stored in the local database of a gateway or client machine are eventually replicated up to the parent server and ultimately to the CMS. The main reason for event purging on gateways and client machines is to prevent free disk space falling to dangerously low levels on these machines, with the attendant risk of the CA DataMinder infrastructure being suspended.

The simplest strategy is to implement purging after replication. Under this strategy, individual items of captured data are automatically excluded from purges until they have been replicated to the parent server. Only items that have already been replicated can become eligible for purging.

To roll out a purging strategy across all of your gateways and client machines, simply edit the Common Gateway Policy and Common Client Policy. If required, you can still specify a custom purge strategy for individual machines by editing their machine policy directly.

Partition-based purges

(Applicable to Oracle databases only)

The CA DataMinder database schema also includes support for Oracle database partitioning based on event time stamps, and for partition-based purging. For full details, see the Database guide; search for 'partition-based purging'.

More information:

Overview

Event Purging

Configure Purges in the Machine Policy

Minimum Retention Period