this is now sorted by Commvault support; the issue was someone had ticked the option of “Enabled Managed Disk space for library” which was causing the jobs not to prune.
Hi @Theseeker
Usually the DDB Pruning works a little bit different as it does not follow the same standard retention associated to the Storage Policy. Usually a DDB backup is pruned when the job is not the last backup job associated to that DDB. Refer to: DDB Backup Pruning Process (at the end of the page)
https://documentation.commvault.com/commvault/v11/article?p=12504.htm
I would start looking at a Data Retention Forecast Report since that can give you a good start as to why some of the jobs are not getting pruned.
https://documentation.commvault.com/commvault/v11/article?p=39786.htm
Some reasons for not aging are; (according to Data Aging - Troubleshooting)
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.
DDB FAQ
https://documentation.commvault.com/commvault/v11/article?p=12643.htm#o12645