Data Aging - Troubleshooting

Data Aging Operation Completes With Error Code: 32:465

Symptom

The data aging job completes with error and the following message is displayed in the job history:

Error Code: [32:465]
No clients, copies or libraries are selected for pruning. Please check the required capabilities/associations for clients/copies/libraries OR there is no data available on the associated clients/copies/libraries.

Cause

The data aging job completes with error and no jobs will be pruned in the following cases:

  • If the user does not have required permissions.
  • If there is no eligible data on the selected CommCell entities. For example, libraries, storage policies etc.

Resolution

To resolve this issue run a data aging job with one of the following permissions:

  • Administrative Management permissions
  • Agent Management, Storage Management, Library Management

For more information, see What permissions are required to perform a data aging job?.

To add security associations at user, user-group level or on an entity, see Getting Started with User Administration and Security.

Data Aging Operation Is Not Aging The Data

Symptom

Data aging operation is not aging the data.

Cause

When a storage policy changes its subclient association without converting the next backup operation to a full backup, data aging operations will not age the data after the last full backup until a new full backup operation is run on the subclient for which the storage policy changed and it has met its retention criteria.

Resolution

Run a full backup operation on the subclient for which the storage policy changed. Once the retention criteria is met, the data will be aged.

Space on a Disk is not Reclaimed even when Jobs are Aged

Symptom

The aged data is not getting pruned, and space on a disk is not getting reclaimed.

Cause

The space on a disk might not get reclaimed if DDB Activity is disabled.

Resolution

To resolve this issue, enable DDB Activity.

  1. From the CommCell Browser, right-click the <CommServe> node and then click Properties.
  2. In the CommCell Properties dialog box, on the Activity Control tab, select the Enable DDB Activity check box, and then click OK.

Data Retention Forecast and Compliance Report Error Codes

The following table contains the error codes that may be displayed in the Reason for Not Aging field found in the Data Retention Forecast and Compliance Report. This field is populated with one of these codes when data is not aged. Code descriptions are provided to assist users with troubleshooting.

Reason for Not Aging Error Code Description
ASR CYCLES Data will be retained past its retention period until another ASR backup is run.
BASIC_CYCLES Job did not meet its retention cycle requirements. More full backup operations are required to meet retention rules.
BASIC_DAYS Job did not meet its retention days requirements.
Data Aging Disabled Data Aging feature is disabled on Storage Policy Copy, Client or Client Group level.
DEL_SUBCLIENT Job is not prunable as the subclient was changed and the days retention*, which is applicable in this case, has not yet expired.
DIFF_POLICY Job is not prunable as the storage policy was changed and the days retention*, which is applicable in this case, has not yet expired.
EXT_ALLFULL Job has been selected for extended retention, which has not yet expired. It has been set to retain all full jobs.
EXT_FIRSTOFHALFYEAR Job has been selected for extended retention, which has not yet expired. It has been set to retain the first full of each half year.
EXT_FIRSTOFMONTH Job has been selected for extended retention, which has not yet expired. It has been set to retain the first full of each month.
EXT_FIRSTOFQUARTER Job has been selected for extended retention, which has not yet expired. It has been set to retain the first full of each quarter.
EXT_FIRSTOFWEEK Job has been selected for extended retention, which has not yet expired. It has been set to retain the first full of each week.
EXT_FIRSTOFYEAR Job has been selected for extended retention, which has not yet expired. It has been set to retain the first full of each year.
EXT_LASTOFHALFYEAR Job has been selected for extended retention, which has not yet expired. It has been set to retain the last full of each half year.
EXT_LASTOFMONTH Job has been selected for extended retention, which has not yet expired. It has been set to retain the last full of each month.
EXT_LASTOFQUARTER Job has been selected for extended retention, which has not yet expired. It has been set to retain the last full of each quarter.
EXT_LASTOFWEEK Job has been selected for extended retention, which has not yet expired. It has been set to retain the last full of each week.
EXT_LASTOFYEAR Job has been selected for extended retention, which has not yet expired. It has been set to retain the last full of each year.
IDA_NOT_SUPPORTED Data Aging does not support specific iDataAgent.
INFINITE Storage Policy Copy is configured for infinite retention.
JOBRUNNING Job is running.
LOG_RULE Log backup is newer than a data backup for the same instance, which has not yet met basic retention.

Note: The LOG_RULE reason does not apply to a data backup that is part of a selective copy.

Managed Disk Space Managed Disk Space option is enabled. Data has met retention and will be available until the disk space is required for new backup operations.
NOT_COPIED Job must be copied prior to aging.
NOT_MOVEDTOMEDIA Snap job was not copied to primary copy.
POLICY_PENDING Job is still pending for the Automated Content Classification policy and may be retained until the policy job is completed.

To resolve this issue, enable Ignore Compliance Policy Check For Job Data Aging parameter on the Data Aging tab of the Media Management Configuration dialog box.

PRUNABLE Job is prunable.
REQ_BY_DATA Job is required by a not yet prunable full backup.
REQ_BY_JOB Data not prunable by BASIC_DAYS requires this job in order to be restorable.
RETAINED_JOB Manual Retention is set for this job and has not yet expired.
SPCHANGE_KEEPLASTFULL Change in Storage Policy subclient association. Retain the last full backup.
SQL LOG RULE
  • Jobs are required by log backups, which have not yet met basic retention days (BASIC_DAYS). Older data may be retained due to a restore and subsequent transaction logs that were run and now require this data to be restorable.
  • Log backups are required by other jobs. This may be because the cycles have not been met for the corresponding last full backup for one or more of the databases backed up in this transaction log backup.
SQL_CHAIN Jobs are required by log backups, which have not yet met basic retention days (BASIC_DAYS). Older data may be retained due to a restore and subsequent transaction logs that were run and now require this data in order to be restorable.
SUBCLIENT_UNINSTALLED Job is not prunable as the subclient was uninstalled and the days retention*, which is applicable in this case, has not yet expired.

* - For these backup operations, restorability is ensured for the copy's retention days. If retention days is set at 0 or this is a spool copy, then these backup operations are kept, by default, for 30 days. This is configurable through the Media Management Configuration (Service Configuration).