Loading...

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 (roles):

  • 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 Role-Based 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.

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 fieldfound 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

ACTIVE_CLONE

Jobs in a cycle will be retained when an active clone is running. If a clone is running from jobs on a spool copy then it will be retained on the spool copy.

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 on Client

Data Aging feature is disabled on a client.

Data Aging Disabled on Client Group

Data Aging feature is disabled on a client group.

Data Aging Disabled on Copy

Data Aging feature is disabled on a storage policy copy.

Data Aging Disabled For Running Restore

Data Aging feature is disabled on a subclient or on a backupset for running restore job.

Data Aging Disabled for Case Manager

Data Aging feature is disabled by the Case Manager feature.

Data Aging Disabled On Instance

Data Aging feature is disabled on an instance.

Data Aging Disabled for Special Clients

Data Aging feature is disabled on special clients. For example: Edge Drive clients, Laptop clients.

DDB_BACKUP

Deduplication database (DDB) jobs are not pruned because:

  • The DDB backup for each substore is retained.
  • The DDB backup for each substore before the last disaster recovery is retained.
  • There is a configuration in place to retain more than one DDB backup.
  • There is a configuration in place to retain the DDB backups of a sealed store.
  • A DDB backup is manually retained.
  • If the configuration to pick DDB backup jobs for auxiliary copy operation is in place and a DDB backup job is not copied during the auxiliary copy operation, then that DDB job is retained.

RECONCILE_BACKUP_PENDING

Job is not prunable and will be retained until a synchronization operation runs when a new backup cycle starts. 

To skip jobs from being retained until a synchronization operation runs, disable the Retain jobs in previous cycle until Source Files and backup index are synchronized in latest cycle parameter on the Data Aging tab of the Media Management Configuration dialog box.

CATALOG_RUNNING

Snap job is currently being cataloged.

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.

EXT_LAST_FULL_JOB

Last full backup jobs for de-configured clients will be retained if the Retain last Full job of de-configured clients based on Extended Retention Rules parameter is enabled.

FOREIGN_DATA

Jobs that are migrated from third party backups.

IDA_NOT_SUPPORTED

Data Aging does not support specific iDataAgent.

INDEXING_JOB

Applies to Indexing Version 2 only. Index backup requirements that control aging have not been met. Note that:

  • Index data cannot be aged until the requirements described in Index Backup Retention have been met.
  • The schedule policy used for backing up Indexing Version 2 indexes is one created for that purpose, not one used for general backup operations. See Index Backup Schedule for details.

INFINITE

Storage Policy Copy is configured for infinite retention.

JOB_RETENTION

Job is not prunable based on the job count 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.

REFCOPY_PENDING

Reference copy job has not run on the these backup jobs.

REQ_BY_DATA

Job is required by a not yet prunable backup.

For VSA with Indexing V2 support, the job is required till associated VM jobs are retained. The parent job is pruned only after the last job of the associated VM is pruned.

REQ_BY_JOB

Jobs that are not prunable requires this job in order to be restorable. The job will be retained on the same storage policy copy that has the dependent jobs. If the dependent jobs are on a different storage policy copy, then the job will be retained on the storage policy copy that has the highest retention.

RETAINED_JOB

Manual Retention is set for this job and has not yet expired.

SP_CHANGE_KEEP_LAST_FULL

Change in Storage Policy subclient association. Retain the last full backup on the old Storage Policy until a new full backup job runs on the new Storage Policy.

Each Agent determines whether a job that completed with errors should be treated as valid or not. Based on the information provided by the Agent, data aging operation will display as follows:

  • If the agent treats the full backup job that completed with errors as valid, and a new full backup job from the new Storage Policy also completes with errors, then it will be considered as a valid full and the jobs from the old Storage Policy will no longer be retained with SP_CHANGE_KEEP_LAST_FULL reason.
  • However, if the agent treats  the full backup job that completed with errors as NOT valid, and a new full backup job from the new Storage Policy completes with errors, then it will NOT be considered as a valid full and the jobs from the old Storage Policy will continue to be retained with SP_CHANGE_KEEP_LAST_FULL reason, until a full backup job is successfully run from the new Storage Policy.

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.

SILO_JOB

When an active Silo DDB has been sealed and moved to storage, all the backup jobs that went to that DDB must meet the retention rules (defined in their associated storage policy copy) for the DDB to become aged. Once all of the jobs have met their retention criteria, the entire DDB is considered ageable, and the Silo (tape) backup jobs are then aged. The tape designated for the Silo storage is then refreshed and available for re-use.

Extended retention rules are not supported on Storage Policy Copies configured for Silo Storage.

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

DA0002: Aged Data is Not Being Pruned from the Cloud Storage

For more information, see KB Article DA0002.

Last modified: 3/1/2018 4:52:09 PM