Hello Commvault Community,
I need help with data pruning issue after Seal DDB (every 3 months) - micro pruning is disabled, but jobs shouldn't be held for that long anyway. (screen1.png)
Micro pruning is disabled due to the cost of operations in the Cloud Storage.
As I remember correctly, Commvault also recommended disabling micro pruning on the cloud library.
We have generated a Forecast report, where some of the described Jobs are actually kept by not being copied to Secondary Copy, but it's about 30TB, and for example (screen2.png) it says that the data is 126TB within one of the Sealed DDBs. There are several such databases and a total of about 600TB of data remains in the Cloud, which should probably be deleted.
I am asking for help in solving the problem. Screenshots and Forecast report are attached.
Thanks & Regards
Best answer by Mike StrueningView original