Administration Guide › Machine Administration › Event Purging › Configure Purges in the Machine Policy

Configure Purges in the Machine Policy

To implement database purging, you need to configure the common gateway and common client machine policies

1. In the Administration Console, expand the Machine Administration branch .
2. To configure event purging for:
   • The CMS, right-click the CMS and choose Edit Policy.
   • All gateways, right-click the CMS and choose Edit Common Gateway Policy.
   • All client machines, right-click the CMS and choose Edit Common Client Policy.
   • A specific machine, right-click the machine and choose Edit Policy.
3. In the Machine Policy Editor, browse to the Data Management folder.
4. Set the purge frequency: You can configure purges to run immediately after the data has been replicated, or you can schedule purges to run at regular intervals.
   • Scheduled purges: To schedule regular purges, set Purge Events on Replication? to False (clear the check box). Then configure the policy settings for the minimum retention period and purge frequency and time.
   • Purging after replication: Set Purge Events on Replication? to True (select the check box). This purges your database as soon as captured or imported data has been replicated to the parent server. No further policy changes are required. This setting is ignored on CMSs; it is intended for use only with gateways and client machines.
5. Configure purge performance: Other settings in the Data Management folder 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.
6. Save the policy. Database purging is turned on as soon as the new settings replicate to the target CA DataMinder machines.

More information:

Event Purging

Purge Policy Settings