Data Aging - DB2 MultiNode iDataAgent

Table of Contents

Getting Started

Data Aging is the process of removing old data from secondary storage to allow the associated media to be reused for future backups.

You can change the retention of your data based on your needs.

Setting Up the Basic Retention Rule

  1. From the CommCell Browser, expand Policies > Storage Policies > storage_policy.
  2. Right-click the appropriate storage policy copy, and then click the Properties.
  3. In the Copy Properties dialog box, on the Retention tab, under Basic Retention Rule for All Backups, click the Retain For.
    • Enter number of days to retain the data.
    • Enter number of cycles to retain the data.
  4. Click OK.
  5. In the Confirm Basic Retention dialog box, click Yes.
  6. On the ribbon in the CommCell Console, on the Reports tab, click Forecast, and then click Run.

  7. The Data Retention Forecast and Compliance report displays the data to be pruned when a data aging job is run.


    • To ensure only data intended for aging is actually aged, it is important to identify the data that will be aged based on the retention rules you have configured. Hence, ensure this report includes only the data you intend to age.

      If necessary, fine-tune your rules so that only the intended data is aged.

Running the Data Aging Job

  1. From the CommCell Console, right click the CommServe node, click All Tasks > Data Aging.
  2. In the Data Aging Options dialog box, in the Job Initiation area, define whether the data aging job runs immediately or if it will be scheduled.

  3. Click OK.

    If you chose to run the job immediately, the data aging job starts now.

    If you chose to run the job according to a schedule, the data aging job runs according to the schedule that you defined.

    After data aging job is run, the data will be pruned from the storage.

Advanced Options

Log Backups (transaction, archive, or logical logs) are not considered part of the backup cycle. Therefore, storage policy cycle retention parameters do not apply to them. However, log backups may be linked to data backup operations, which can affect their retention as follows:
  • Log backups are linked to a full backup if they are run at the same time. This is regardless of whether the full backup included data only or data and logs. Such backups follows the standard data aging rules.
  • If a full backup job is run on data, then the next log backup job will be linked to this full backup job.

    These are considered as linked or chained log backups and are not aged until the linked data is aged. In addition, the following is also considered:

    • Logs that need to be copied to secondary copies will not be aged both on primary and non-primary source copy
    • Logs that exist only on one copy will be aged when they are older than the oldest data
    • Logs that exist on multiple copies will be aged according to copy retention days
    • Logs that exist on multiple copies with the longest retention days will be aged when they are older than the oldest data
    • Partial, disabled logs will be aged when they are older than the oldest data
  • If a full backup job is run on data and logs, then the next log backup will not be linked to this full backup job.

    As this is an unlinked log backup, by default, this will follow the unique data aging rules for log backups. If you want such log backups to be aged according to the defined days retention rule for the data, you can do so as follows:

    1. From the CommCell Console, click the Storage tab.
    2. Click the Media Management icon.
    3. Click the Data Aging tab.
    4. In the Prune All Database Agent Logs Only By Days Retention Rule, type 1 to enable pruning for all database agent logs based on the days retention.
    5. Click OK.

Data Aging Rules for Selective Copy

A selective copy allows you to copy specific full backup jobs from a source copy. The source copy can be either a primary or a synchronous copy. Selective copy facilitates better tape rotation. Consider the following :

  • A full backup will be copied to a selective copy if the log job is done after the data job. If this is not the case, the data job is not copied to the selective copy and will have a "Log Link Pending" status.
  • A full backup has a one hour delay before it is copied to the  selective copy.
  • Log jobs are not copied if they are using a different storage policy. The log jobs will be retained by the log policy rules.
  • Online data only full backups from that you perform from the CommCell Console on a DB2 MultiNode database that is version 9.5 or above are eligible for selective copy.

Additional details on Selective Copy can be found here.