@NikkyArt the DDB should age on its own once there are no jobs that reference the blocks within the DDB.

I covered the best way to find the jobs in another thread here:

Here’s the instructions:

If you have access to the SQL studio manager on the CS, below queries can be run to confirm if there are any jobs stuck in the DB for the DDB store.

use Commserv

select * from idxsidbstore

Next run the following query to list jobs associated to this DDB.

use Commserv

select * from archjobsonstoreinfo where storeid = n

If this query outputs any jobs, run a Data Retention Forecast and Compliance report on those copies to see why they are not aged.

If they don’t show up in the gui at ALL, then you will have to run qoperation per instructions in BoL link for qoperation agedata

https://documentation.commvault.com/commvault/v11_sp20/article?p=45239.htm

Now if that turns up empty, then we need to look at the SIDBPrune and SIDBPhysicalDelete log files on the Media Agents to see why data is not being removed.

@NikkyArt - Please share some additional information with us.  

• Are jobs associated with the GDP’s
• Are there any depended storage policies/storage pools?
• Do the media agents that were assigned to the GDP still exist? 

Please provide any errors or log snippets, that are issued when you attempt to deleted.

@NVFD411 

• Are jobs associated with the GDP’s
• Are there any depended storage policies/storage pools?
• Do the media agents that were assigned to the GDP still exist? 

no, no jobs for this GDP and others. I can not show/find delete button for DDB.