DDB Prunable Block Count

Hi @Eduardo Braga.

Could you help us know if the previous DDB engine was sealed and is this enabled for Macro pruning.
 

Yes, There is one sealed DDB and the option to physically prune is enabled. 

I check every Mount Path of the Disk Library and they permit pruning of aged data. At least, not directly.

The cvault-ma-03 and cvault-ma-04 MA servers don’t have access to any Mount Path. 

 No, It’s steady for days. Almost 26 milions of blocks for days. At least 30 days.

More info: the documentation you mentioned states that “If the CommServe job records to be deleted count is higher and is not reducing, then ensure the following”

In our case, we don't run the data verification job for a long time.

And “CommServe job records to be deleted count” is also high. See below.

@Eduardo Braga : Is the Prunable block count rising consistently?

There is this KB article you can refer for quick reference.

https://kb.commvault.com/article/53997

 

 No, It’s steady for days. Almost 26 milions of blocks for days. At least 30 days.

 

More info: the documentation you mentioned states that “If the CommServe job records to be deleted count is higher and is not reducing, then ensure the following”

In our case, we don't run the data verification job for a long time.

And “CommServe job records to be deleted count” is also high. See below.

 

I’ll try to increase the value of DedupPrunerThreadPoolSizeDisk additional setting

You can also run the Data Retention Forecast and Compliance Report on this library and see why jobs are not pruning?

Please check for the DDB and see if there are any warnings.