Thanks for your awnser Tom.
We have 2 Dedup databases and none is sealed.
Any other ideas?
Yes, I have come across this behaviour loads of times AND I have devised a method to work around it in our environment.
The issue only seems to affect mainly de-duped database library data and has the effect, over time, of consuming much more physical library space than can be accounted for. My suspicion is that this is due to the back-end storage device not supporting "hole drilling", which is a process that Simpana attempts to use during DataAging, to release library space. Hole drilling attempts to release space within chunk files back to the free pool, however, in practice, when Hole Drilling is not supported, ONLY when the deleted data blocks are at the end of the file, will that space be actually released. If it cannot be released, it is marked for some future deletion when all subsequent blocks within the file have, themselves, been deleted. In short, this is a fragmentation issue.
My strategy for reclaiming this lost library space involves:
1) demoting all associated SP primary copies to secondary
2) deleting the primary DDB and all associated library data
3) re-creating the primary DDB from scratch
4) re-populating the primary DDB from the secondary DDB via AuxCopy
5) promoting all associated SP secondary copies back to primary
This can be time consuming depending upon the nature of the data, however, the results can be quite staggering as it often releases many Tb of physical library space back to the pool. Note that this procedure can only work if all of your SPs have both Primary and Secondary copies targetting different storage appliances. Both copies need to be in-sync before any demotion/promotion is attempted.
For me, this is a proven method that I have used on many occassions to recover from imminant library capacity issues. The only downside is that you lose any DR protection whilst this procedure is in place, but this is a calculated risk.
I should point out that we run a completely tapeless environment, with our libraries located on very large enterprise NAS appliances. This procedure may, or may not, work well with tape!