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 Dash Copy Job Chunk History |
Definition: Specifies the number of days for which chunk's metadata is stored in main database table which is used to identify which jobs were copied during the auxiliary copy operation. After the defined number of days, the chunk's metadata is transferred to the history table. Default Value: 7 Range: 0 to 30 |
|
Days to keep Data Management and Collection Job Histories |
Definition: Specifies the number of days the data management and data collection jobs histories are preserved. Default Value: 90 days Range: 0 to 5000 Usage: Retaining job history for longer or shorter periods may be required for compliance, auditing, or other reasons. If you want to retain the job history infinitely, then set the value to 0. If you specify any value between 0 and 7, then the job history will be retained for 7 days. |
|
Days to keep invalid chunks |
Definition: Specify the number of days that invalid chunks are preserved. Default Value: 3 Range: 3 to 10 (Values set to less than 3 are reset to 3). Usage: An invalid chunk is one where the job was interrupted and the chunk needed to be rewritten for integrity purposes. Data from these invalid chunks are usually unrecoverable, but could provide some data recovery in a DR situation where no other valid chunks exist. |
|
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 keep job pending reason |
Definition: Specifies the number of days to retain the job pending reason messages after the jobs are pruned. Default Value: 15 Range: 0 to 5000 Usage: Retaining the job pending reason messages for longer or shorter periods may be required for compliance, auditing, or other reasons. The messages are retained for the number of days specified here. After the specified days, the job history may be retained, but the job pending reason messages are deleted. |
|
Days to keep job status change history for GRC |
Definition: Specifies the number of days to retain the job status history performed in GRC. Default Value: 90 days Range: 7 to 180 |
|
Days to keep jobs of de-configured clients |
Definition: Specifies the number of days to retain the jobs of deconfigured clients. Note:
|
|
Days to keep Library Histories |
Definition: Specifies the number of days to retain the information about disk usage on magnetic libraries, before it is pruned. Default value is set at 14. Default Value: 14 days Range: 7 to 180 days Usage: Retaining disk usage for longer or shorter periods may be required for compliance, auditing or other reasons. |
|
Days to keep Pruning Status Histories |
Definition: Specifies the number of days to preserve the pruning status histories. Default Value: 15 days Range: 1 to 100 days Usage: The pruning status histories are deleted after the specified number of days to maintain available space in the database. |
|
Days to keep Replication Backup Job Histories |
Definition: Specifies the number of days to retain the replication backup job histories. The default value is set to 90 days. Default Value: 90 Range: 7 to 5000 days Usage: Retaining job history for longer or shorter periods may be required for compliance, auditing or other reasons. If you want to retain the job history infinitely, then set the value to 0. If you specify any value between 0 and 7, then the job history will be retained for 7 days. |
|
Days to keep the archiver restore job histories |
Definition: Specifies the number of days to retain the archiver restore job history data before it is pruned. This setting is applicable only for Exchange Compliance Archiver. All other archiver restore job histories will be pruned based on the Days to keep the backup job histories parameter. Default Value: 0 Range: 0 to 5000 Usage: Retaining job history for longer or shorter periods may be required for compliance, auditing, or other reasons. If you want to retain the job history infinitely, then set the value to 0. If you specify any value between 0 and 7, then the job history will be retained for 7 days. |
|
Days to keep the Restore job histories |
Definition: Specifies the number of days to retain restore jobs history. Note For stub recall and restore job history, this parameter applies to job start time. Default Value: 90 Range: 0 to 5000 Usage: Minimum time to retain the restore job history is a week. The software retains the restore job history for 90 days by default. To retain the restore job history infinitely, set the value to 0. |
|
Days to keep the failed/killed backup job and other job histories |
Definition: Specifies the number of days to retain backup job history data before it is pruned. This applies to: Auxiliary Copy jobs, Stub Recall jobs, failed jobs, killed jobs, jobs that failed to start, and replication backup jobs. Note: For auxiliary copy, stub recall, replication backup, and restore job history, this parameter applies to job start time. Default Value: 90 Range: 0 to 5000 Usage: Retaining job history for longer or shorter periods may be required for compliance, auditing, or other reasons. Before reducing this number you should consider that valid chunks associated with failed/killed jobs can be restored using the Restore by Job task. Minimum time to retain the job history is a week. The software retains the job history for 90 days by default. To retain the job history infinitely, set the value to 0. |
|
Days to keep the list of migrated foreign jobs to be pruned after processing them |
Definition: Specifies the number of days to maintain the history of the migrated foreign jobs. Default Value: 7 days Range: 3 to 30 Usage: This parameter is useful to retain the history of migrated foreign jobs for specified number of days. Once the specified number of days is reached the history of the migrated jobs gets pruned. |
|
Days to keep the Site Replication job histories |
Definition: Specifies the number of days to retain job history information for Live Sync operations after it is pruned. Default Value: 30 days Range: 0 - 5000 days Usage: Specify fewer days to limit the size of storage required for job history, or additional days to keep job history available for longer (only for audit purposes). |
|
Days to keep the successful backup job histories |
Definition: Specifies the number of days to retain successfully completed backup job history data after it is pruned. Default Value: 7 Range: 0 to 5000 Usage: Retaining job history for longer or shorter periods may be required for compliance, auditing, or other reasons. Successful backup job history is retained for as long as the data is restorable plus the number of days specified here. Increasing this number might be prudent if you are doing trend analysis on information contained within the backup job histories. |
|
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. For example: If the value for Days to consider for pending logical pruning for Deduplication Pruning threshold event is set at 7 days. The value for Max number of records pending pruning for non dedup pruning per mount path threshold event is set for 5000. Then an event message is generated if there are 5000 or more records pending for pruning on a mouth path for 7 or more days. 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) Usage: Set this option to 1 and run data aging job to prune index backups from inactive storage policies. |
|
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 from the day they were created:
Default Value: 1 Range: 0 (No) or 1 (Yes) Usage: By default, the value is set to 1 which means that clients that meet the preceding criteria are deleted. Set the value to 0 to not delete the clients that meet the preceding criteria. Notes: For tape library, the deconfigured clients are deleted only when all the media associated with the tape library are recycled. Tip: You can also use the Clients with no Archive Data rule to group client computers that meet the preceding criteria and may be deleted. |
|
Disable jobs for Auxiliary Copy that met its retention |
Definition: When this option is enabled, jobs that are not available on the destination copy that is, jobs with status To Be Copied or Partial are marked disabled for Auxiliary Copy, when those jobs meet the retention criteria defined on that destination copy. Applies to all storage policies in the CommCell. Default Value: 1 Range: 0 (disable) or 1 (enabled) Usage: Use this option to reduce the overhead on Auxiliary Copy job. For more information, see Disabling Jobs for an Auxiliary Copy that meets the Retention Criteria. |
|
Disable RMAN External Pruning |
Definition: You can use this configuration parameter to disable the deletion of the archive files when you use external RMAN scripts to clean up the backup pieces. Default Value: 1 Range: 0 or 1 Usage: The RMAN external pruning feature is disabled when this parameter is set to 1. |
|
Enable Dataset and Dataset Member Pruning |
Definition: You can use this configuration parameter to enable dataset and dataset member pruning or subscription and subscription context pruning on OnCommand Unified Manager (OCUM). Default Value: 0 Range: 0 or 1 Usage: Set this parameter to 1 to enable automatic deletion of OCUM dataset or subscription context and dataset or subscription context members after the corresponding subclient or subclient content is deleted or the subclient reassociated and all its jobs are pruned. The Enable Dataset and Dataset Pruning parameter set to 1 is a prerequisite for the Delete NetApp secondary vault/mirror volumes for aged members parameter, to enable the deletion of secondary volumes for aged dataset members for cases in which there is subclient deletion or reassociation, or subclient member deletion or reassociation. |
|
Honor copy retention for jobs with no data |
Definition: If the parameter value is set to 0, then the incremental backups with no data are aged immediately when the next data aging job is run. Default Value: 1 Range: 0 or 1 Usage: When the value is set to '1', then the incremental backup jobs with no data are not aged until the full backup is aged on the primary copy. When the value is set to '0', then the incremental backup jobs with no data are aged immediately. |
|
Honor cycle only retention for log rule |
Definition: Retain the logs using the retention cycle that is configured for the currently associated storage policy copies. Default Value: 0 Range: 0 or 1 Applies to: Database agents Usage:Log backups that run in parallel with a full backup job are linked to the full data backup job. Therefore, if you retain a full database backup, the linked log backups are retained until the software prunes the full database backup regardless of any lower retention setting for the logs.
Example1: If you are using separate storage policies for database (1 cycle with weekly full, 30 days) and archive logs (7 days), note the following behavior:
Example2: If you are using separate storage policies for database (1 cycle with weekly full, 365 days) and archive logs (7 days), and then you change the data backups to use a storage policy with retention (1 cycle with weekly FULL, 30 days), note the following behavior:
|
|
Honor Extended Retention and Selective Copy rules for Oracle/RAC/SAP regular Full Jobs |
Definition: Allow Oracle, Oracle RAC and SAP Oracle full backup jobs to be eligible for selective copy and extended retention rules. Default Value: 1 for new V11 installs, 0 for upgrades to V11 Range: 0 (No) or 1 (Yes) When the value is set to '1', full backups that you perform from the CommCell Console for Oracle, Oracle RAC and SAP Oracle databases, are eligible for selective copy and extended retention rules. When the value is set to '0', full backups that you perform from the CommCell Console for Oracle, Oracle RAC and SAP Oracle databases are not eligible for selective copy and extended retention rules. Oracle and Oracle RAC custom script full backup jobs and SAP Oracle selective online full command line backups are also eligible for selective copy and extended retention when the value is set to 1. Oracle, Oracle RAC, and SAP Oracle regular command line backups jobs are not eligible for selective copy and extended retention. Usage: By default, on installs, full backups that you perform from the CommCell Console for Oracle, Oracle RAC and SAP Oracle databases and custom script online full backups for Oracle and Oracle RAC databases are eligible for selective copy and extended retention rules. |
|
Honor SQL Chaining for Full jobs on Selective copy |
Definition: Specifies whether or not to honor SQL chaining for full jobs on a selective copy. Default Value: 1 Range: 0 (No) or 1 (Yes) When the value is set to '1', full jobs on selective copy retain logs that are chained. Full backups are not aged. When the value is set to '0', full jobs on selective copy are retained by basic retention criteria. Full backups do not retain the logs that are chained with SQL_CHAIN or SQL_LOG_RULE. Usage: By default, the value is set to 1. Full jobs on selective copy retain logs that are chained. Full backups are not aged. |
|
Number of days to keep history records for cloud vm management |
Definition: Specifies the number of days to preserve the power management history of the cloud virtual machines. Default Value: 14 days Range: 7 to 30 days Usage: The software deletes the power management histories after the specified number of days to maintain available space in the database. |
|
Retain jobs in previous cycle until Source Files and backup index are synchronized in latest cycle |
Definition: Specifies that a synchronization operation runs when a new backup cycle starts. If you do not want to prune the previous backup cycle until a synchronization operation has successfully run in the current cycle, then ensure that you select the Reconcile Backup check box on the Subclient Properties dialog box and enable the Retain jobs in previous cycle until Source Files and backup index are synchronized in latest cycle parameter. The Data Retention Forecast and Compliance report displays all the jobs which are not pruned as they do not qualify for the synchronization check. Note This configuration parameter is not applicable for subclients that have days only retention configured. For such subclients the backup jobs will be pruned depending on their respective data aging selection. Default Value: 1 Range: 0 (No) or 1 (Yes) When the value is set to '1', and the Reconcile Backup check box is selected on the Subclient Properties dialog box, then the previous backup cycle is not pruned until the synchronization operation runs successfully in the current cycle. When the value is set to '0' or the Reconcile Backup check box is cleared on the Subclient Properties dialog box, then the previous backup cycle is pruned depending on the storage policy copy data aging selection. Usage: By default, the value is set to 1 and the newly created subclients will have the option enabled by default. For subclients created prior to Service Pack 7, you can enable the Reconcile Backup check box in the Subclient Properties dialog box. |
|
Retain last Full job of de-configured clients based on Extended Retention Rules |
Definition: Specifies that for de-configured clients, the last full backup job will be retained for Where Default Value: 0 Range: 0 (disabled) or 1 (enabled) |
|
Ignore Completed With Errors job option for Extended Retention calculations |
Definition: Specifies whether or not to ignore the Completed With Errors job option for Extended Retention calculations. Default Value: 0 Range: 0 (No) or 1 (Yes) When the value is set to '1', the current value set for the Completed with Errors job in the agents' database is ignored for extended retention calculations. When the value is set to '0', the current value set for the Completed with Errors job is honored for extended retention calculations. Usage: Administrator may hold extended retention Jobs to a higher standard than those used to determine normal media/retention cycle. |
|
Ignore Compliance Policy Check For Job Data Aging |
Definition: Specifies whether or not to ignore the Compliance Policy Check for Job Data Aging. Default Value: 0 Range: 0 (No) or 1 (Yes) Usage: Applies to the Automated Content Classification Policy. During a data aging operation, if a particular job is qualified to be processed by an Automated Content Classification Policy, the data will be retained even though it is eligible to be aged, until it is acted upon by the Automated Content Classification Policy. Setting this value to 1 will allow data aging to prune the job regardless. |
|
Ignore Cycles Retention On backup activity disabled subclient |
Definition: Specifies whether or not to ignore the defined retention cycle rules for data associated with clients, agents, instances, and subclients that have backup activity disabled. Default Value: 0 Range: 0 (No) or 1 (Yes) Usage: Without cycle retention (parameter value set to 1), only days are used to retain data on agents, instances, and subclients that have backup activity disabled. |
|
Ignore Cycles Retention On De-Configured Clients |
Definition: Specifies whether or not to ignore the defined retention cycle rules for data associated with deconfigured clients, deconfigured agents, and deconfigured instances. Default Value: The following are the default values:
|
|
Ignore Reference Copy Rule to retain jobs on source subclients |
Definition: Specifies the retention of jobs on source subclients for the reference copy requirements Default Value: 0 Range: 0 (No) or 1 (Yes) Usage: This parameter specifies the retention of jobs on the source subclients when the reference copy subclients are configured for them. When the parameter value is set to 0, the jobs are retained on the source subclient until reference copy is done. When the value is set to 1, the jobs are not retained on the source subclient for reference copy requirements. |
|
Mark Oracle Backup piece as expired for aged archive files |
Definition: This setting applies to tape backups. Specify whether to mark an Oracle backup piece as expired (aged) even when the tape has not been deleted or overwritten. Default Value: 0 Range: 0 (No), 1 (Yes) Usage: By default, the Commvault software ages an Oracle backup piece as expired when the tape that the backup resides on is deleted or overwritten. You can set this value to 1 to have the backup piece marked as expired even when the tape has not been deleted or overwritten. Applies to: Oracle, Oracle RAC |
|
Max number of records pending logical pruning for Deduplication pruning threshold event |
Definition: Specifies the threshold value of the deleted records that are not pruned from the disk. Default Value: 10000 Range: 5000 – 1000000 Usage: For example, you have set the threshold value to 10,000 records, and the number of days in the Days to consider for pending logical pruning for Deduplication pruning threshold event parameter is set to four on Friday (01-20-2013). 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. |
|
Max number of records pending pruning for non dedup pruning per mount path threshold event |
Definition: Specifies that on reaching the maximum number of records pending for pruning threshold for non-deduplicated data on a mount path and on crossing the threshold configured for the Days to consider for pending logical pruning for Deduplication Pruning threshold event parameter, an event message is generated. For example: If the value for Days to consider for pending logical pruning for Deduplication Pruning threshold event is set at 7 days. The value for Max number of records pending pruning for non dedup pruning per mount path threshold event is set for 5000. Then an event message is generated if there are 5000 or more records pending for pruning on a mouth path for 7 or more days. Default Value: 25000 Range: 5000 – 1000000 |
|
Maximum job entries to use for calculation of media retention expire time |
Definition: Every few minutes the media retention time is recalculated for media that is written to in that time. This entry specifies how many entries are processed. Default Value: 5000 Range: 0 (all) to 9,999,999 |
|
Number of disk folders to process in a single Data Aging request |
Definition: Specifies the number of disk folders to be processed to a MediaAgent for physical pruning during a pruning cycle Default Value: 1000 Range: 1 to 5000 Usage: The pruning of aged jobs is initiated periodically by the CommServe. In this parameter, you can specify the maximum number of disk folders to be processed to a MediaAgent for physical pruning during a pruning cycle. This parameter is considered for batch processing when the number of disk folders exceed the value specified. |
|
Prune All Database Agent Logs Only By Days Retention Rule |
Definition: Specifies whether or not to ignore the log rule for all Database agents. Default Value: 0 Range: 0 (No) or 1 (Yes) Usage: Database logs retention can be linked to the retention of the related database file. Therefore, if you retain a full database backup, related transactional logs will also be retained until the full database backup is pruned regardless of any lesser retention setting for the logs.
|
|
Prune the jobs on tape media when the retention criteria is met |
Definition: Specifies the pruning of jobs on tape media completely when the retention criteria is met so that the jobs cannot be unaged or restored in future Default Value: 0 Range: 0 (No) or 1 (Yes) |
|
Retain DDB Backups of sealed stores |
Definition: Specifies whether or not to retain the DDB backup of a sealed DDB. When the value is set as 1 the last DDB backup job that was backed up before sealing the DDB is kept. Set value as 0 to not retain the DDB backup job. Default Value: 0 Range: 0 (No) or 1 (Yes) |
|
Specify the lower threshold of archive file count to keep cloud VMs online for pruning |
Definition: Specifies the lower threshold value of the prunable archive file count for the system to keep the cloud MediaAgent online to perform pruning operation. Default Value: 500 Range: 0 to 5000 Usage: The power management keeps the cloud MediaAgent online until the prunable archive file count meets the lower threshold value specified in this parameter. After the file count reaches the lower threshold value, the system turns off the MediaAgent when the MediaAgent is idle for the idle time configured. Note You can configure the idle time in the Idle time (Minutes) for power managed cloud VMs parameter in Service Configuration tab. |
|
Specify the lower threshold of volume count to keep cloud VMs online for pruning |
Definition: Specifies the lower threshold value of the prunable data volume count for the system to keep the cloud MediaAgent online to perform pruning operation. Default Value: 500 Range: 0 to 5000 Usage: The power management keeps the cloud MediaAgent online until the prunable data volume count meets the lower threshold value specified in this parameter. After the volume count reaches the lower threshold value, the system turns off the MediaAgent when the MediaAgent is idle for the idle time configured. Note You can configure the idle time in the Idle time (Minutes) for power managed cloud VMs parameter in Service Configuration tab. |
|
Specify the upper threshold of archive file count to power on cloud VMs for pruning |
Definition: Specifies the upper threshold value of the prunable archive file count for the system to turn on the cloud MediaAgent to perform pruning operation. Default Value: 5000 Range: 1000 to 5000 Usage: The power management turns on the cloud MediaAgent when the prunable archive file count reaches the upper threshold value specified in this parameter. |
|
Specify the upper threshold of volume count to power on cloud VMs for pruning |
Definition: Specifies the upper threshold value of the prunable data volume count for the system to turn on the cloud MediaAgent to perform pruning operation. Default Value: 5000 Range: 1000 to 5000 Usage: The power management turns on the cloud MediaAgent when the prunable data volume count reaches the upper threshold value specified in this parameter. |