Data Aging - Frequently Asked Questions

Table of Contents

What permissions are required to perform a data aging job?

User or User group with the following permissions can perform a data aging job:

  • Administrative Management permissions at CommCell level

Or, the following permissions configured together:

  • Agent Management permission at Client level to prune the data for Clients/iDataAgent/BackupSet/Instances/Subclients
  • Storage Management permission at Storage Policies level to prune the data on Storage Policies
  • Library Management permission at Libraries level to prune on those copies which are associated with minimum of one library

    For example, if Administrator has created da_group01 as user group and the following are specified in the User Group Properties dialog box:

    • Agent Management, Library Management and Storage Management permission
    • Entities client01, SP01, library01
    • user01 is associated to group da_group01 in User tab

    Then, when user1 performs the data aging job, the prunable data on SP01 which is associated to Library01 and client01 will be aged.

What happens to Jobs Retention when I re-associate a subclient to a different Storage Policy?

If a subclient is re-associated to a new storage policy, the retention days specified in the old storage policy is honored until the full backup job is performed using the new storage policy.

During this re-association, if Do not convert to Full option was selected and there is a cycle split between two storage policies, then the jobs in different cycles will use different retention criteria.

How is data aged when data retention is set to one day and one cycle?

When retention on a storage policy copy is set to one day and one cycle, the entire cycle is retained until the last job of a cycle meets its day retention criteria, i.e., the last job in that cycle is older than one day.

How does zero cycle retention work?

If zero cycle retention is configured on a storage policy copy, the data aging process follows the days retention criteria.

Based on the backup jobs, zero cycle retention works as follows:

  • If backups continue to run, it is considered as one cycle retention. Since, all dependent jobs require the Full job to be retained.
  • If no backups are run for x days (x being days retention), the full and dependent jobs that are more than x days old are pruned.

    For example, if retention is set to five days and zero cycle, and no backups run for more than five days, then there are no dependent jobs within the five day retention period. In this scenario, it is considered as zero cycle and the full and any dependent jobs that are more than five days old will be pruned resulting in no data being retained.