Purge Policies
Purge policies (Light, Medium, Aggressive and custom) implicitly defines the input parameters and makes it simple to define a purge scheduler or command.
The parameter -pp defines which policy needs to be used for a purge. You always have a choice of using a custom policy and defining all the required input parameters manually. Purge policy is applicable only for Recordversions and history modes.
The following table defines default parameter values set by each purge policy:
| Purge Policy | Record Version | Description | |
|---|---|---|---|
| Number of Retention Days | Number of Versions to Retain | ||
| Light | 365 | 3 | This policy retains all versions for a year, plus it retains three older versions from the past 365 days other than the golden version. |
| Medium | 0 | 3 | This policy retains three older versions other than the golden version. |
| Aggressive | 0 | 0 | This policy does not retain any older versions. Only the golden version is retained. |
| Purge Policy | History | Description |
|---|---|---|
| Number of Retention Days | ||
| Light | 365 | This policy retains all events for 365 days. |
| Medium | 90 | This policy retains all events for three months. Out of the box, scheduler is configured for History purge with the purge policy as Medium. |
| Aggressive | 0 | This policy purges all completed events. |
Copyright © Cloud Software Group, Inc. All rights reserved.