Note: This topic and the linked topics below refer to scheduled event purges driven by the CA DataMinder infrastructure. But for Oracle databases, CA DataMinder also supports partition-based purging. For details, see the Database guide; search for 'partition-based purging'.
After installing CA DataMinder, you need to turn on database purging to periodically remove events from CA DataMinder databases. By default, purging is turned off on CA DataMinder machines, but we recommend that you enable purging, especially on your gateways and client machines.
You need a separate purging strategy for your CMS, which holds captured 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.
CA DataMinder events become eligible for purging when their minimum retention period expires. Each event purge removes eligible database records plus any associated blob (binary large object) files.
Settings in the machine policy control how often events are purged from the local machine. Other settings provide further control over purge operations. For example, you can choose to suspend the CA DataMinder infrastructure during purge operations or you can specify a purging timeout.
|
Copyright © 2014 CA.
All rights reserved.
|
|