Use this dialog box to establish data aging parameters.
|
Parameter |
Description |
|---|---|
|
Allow CI pruning of backup jobs which aged from all copies |
Definition: Specifies that the data aging must prune the content index from the Search Engine even if the backup data is spread across tape and magnetic libraries. Default Value: 0 Range: 0 (disabled) or 1 (enabled) |
|
Consider inactive copy for Auxiliary Copy check by Data Aging |
Definition: Specifies that the source copy data will not be pruned if it is not copied on the inactive copy. Default Value: 1 Range: 0 (disabled) or 1 (enabled) Usage: If a secondary copy is created for a storage policy, all source copy data required by that destination copy – either synchronous (all data) or selective must be retained until a successful auxiliary copy operation has been completed. This action may not be desired if (a) you are creating secondary copies now with the intention of them holding data at a later point-in-time. Or (b) you forgot to delete a secondary copy and the data movement is no longer required. In either case, you can set the copy status to inactive and set this parameter to 0 (disabled), enabling subsequent Data Aging operation to prune all data being retained solely for pending auxiliary copy operations to now inactive copies. |
|
Days to consider for pending logical pruning for Deduplication pruning threshold event |
Definition: This parameter allows you to generate an event message when the number of deleted records are older than the 7 days and meets the threshold value specified in the Max number of records pending logical pruning for Deduplication pruning threshold event parameter. Default Value: 7 days Range: 1 – 100 days Usage: For example, you have set the number of days to four on Friday (01-20-2013) and the threshold value in the Max number of records pending logical pruning for Deduplication pruning threshold event parameter is set to 10,000. If the number of deleted records older than past Monday (01-16-2013) is greater than the threshold value that is 10,000, then an event message is generated. Once the value is set the check is performed every day to verify both the criteria. |
|
Days to keep job options for a completed job |
Definition: Specifies the number of days to retain the job option information (such as job resource history, Job failure reason, miscellaneous information and so on) in the CommServe database for a completed job. Default Value: 15 days Range: 7 to 999,999,999 days Usage: Retaining job options for longer or shorter periods may be required for compliance, auditing, or other reasons. |
|
Days to retain the jobs when cycles are ignored and retention days on copy is 0 |
Definition: Specifies the number of days to retain a job when its cycles are ignored and retention days are 0. This parameter will take effect when days retention on a storage policy copy and Days to keep jobs of de-configured clients parameter is set to 0. Default Value: 30 Range: 1 to 999 Usage: This is to protect you from inadvertently deleting data by incorrectly setting a storage policy copy’s retention criteria. |
|
Days to consider for pending logical pruning for Deduplication Pruning threshold event |
Definition: Specifies that on crossing the number of days threshold configured for the parameter and on reaching the maximum number of records pending for pruning threshold for non-deduplicated data on a mount path, an event message is generated. Default Value: 7 Range: 1 – 100 |
|
Delete archive files of indexing backup associated with deleted backup sets |
Definition: Use this parameter to specify the deletion of the index backup information after the deletion of associated backup set. Default Value: 0 Range: 0 (disabled) or 1 (enabled) |
|
Delete checkpoints for not currently active storage policies |
Definition: When this option is enabled, checkpoints (Index backups) from inactive storage policies will be pruned with data aging job. Default Value: 0 Range: 0 (disabled) or 1 (enabled) |
|
Delete deconfigured clients that have no protected data |
Definition: During a data aging job, clients that meet the following criteria are deleted after 30 days. |
|
Disable jobs for Auxiliary Copy that met its retention |
Definition: When this option is enabled, jobs are marked disabled for Auxiliary Copy when they meet retention criteria. |
|
Disable RMAN External Pruning |
Definition: Use this configuration parameter to disable deletion of archive files when using external RMAN scripts. |
|
Enable Dataset and Dataset Member Pruning |
Definition: Enables dataset and dataset member pruning. |
|
Honor copy retention for jobs with no data |
Definition: Specifies retention behavior for incremental backups with no data. |
|
Honor cycle only retention for log rule |
Definition: Retains logs using cycle retention only. |
Honor SQL Chaining for Full jobs on Selective copy ///// |
Definition: Specifies whether SQL chaining is honored. |
|
Retain DDB Backups of sealed stores |
Definition: Specifies whether to retain DDB backups of sealed stores. |