I would like to request your help as i’m quite new and have only basic knowledge of backup systems.
After reading the commvault documentation available online and tried to troubleshoot the issues, they were narrowed down to 3:
- Sealed DDB are not aging out.
- When I try to run a verification of existing jobs on disk and deduplication database it says DDB is corrupted.
- we have our disks full, as the backups all have stopped.
When i run the data retention forecast and compliance report it says “BASIC CYCLE” as reason why jobs are not aged out, i have this dedup policy to age out jobs after 1 cycle, so i guess that if i do a full backup, the previous will be aged out.. except i dont have any available disk space.
Also I was unable to find a DDB backup as it seems there was never one to begin with.
Should i reconstruct one new from the group up?
How can i reduce the size of sealed DDBs as they are quite old.
Best answer by Mike Struening
Before Deduplication, Data aging would free space pretty much instantly. With dedupe, there are several pieces involved before blocks qualify for deletion.
Check the Media Agent log files for SIDPrune (I don’t remember if SIDBPhysicalDelete.log existed in v10).
The pruning will likely be very slow (compared to non dedupe).
You can generally ignore the v10 ‘space to clear’ reporting as it was based on non-dedupe expectations.
The .PRUNABLE generally means something will be deleted in that folder if not the entire thing. I would suspend any jobs that are running to this library as well as running jobs will hog up the DDB related resources (things are FAR BETTER in v11).
Lastly, I would consider upgrading to v11 if possible. SO MUCH BETTER!