CommVault Data Aging job fails with the error “Failed to get prunable data”

Data Aging is the process which deletes the data once the retention has been superseded. Additionally the data aging process defines the extended- and basic retentions.

Last week – after 1 year of successful execution – ┬áthe data aging jobs started to fail with the following error: “[32:329] Failed to get prunable data“.

In the log files (jobmanager.log) I found the following references:
12380 4340 09/10 12:37:59 44445 Scheduler Set pending cause [Failed to get prunable data.]::Client [commserve] Application [DataAging] Message Id [536871241] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].
12380 4f6c 09/10 12:37:59 44445 Scheduler Ignored pending cause [Failed to prune data due to database problem.]::Client [commserve] Application [DataAging] Message Id [218103857] RCID [0] Reservation Id [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].
12380 4340 09/10 12:38:06 44445 Scheduler Ignored pending cause [Failed to prune data due to database problem.]::Client [commserve] Application [DataAging] Message Id [218103857] RCID [0] Reservation Id [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0].
12380 4f6c 09/10 12:38:06 44445 Scheduler Phase [Failed] message received from [commserve] Module [DataAging] Token [] restartPhase [0] 12380 4f6c 09/10 12:38:07 44445 JobSvr Obj Phase [1-Data Aging] for job Failed and will be restarted.

After some research and help of CommVault support, we found out the issue was correlated with the timezone configuration on the storage policies. One storage policy was defined in the local time zone (UTC-05:00) of the remote site, instead of the timezone of the CommServe (UCT+01:00).

After changing the timezone configuration on the storage policy to “CommServe Time Zone“, the data aging is executed properly and the magnetic libraries are free’ed up properly.

CommServeTimeZoneDataAgingIssue-1

I encountered this issue on a CommVault Simpana 10 Service Pack 8 environment.

Thanks for reading!

Leave a Reply