Before we delve deep into how clean up the space on the DDB Drive, can we please confirm the following
- The size of the data store on the Disk Library that is associated to the DDB ?
- Is there more then one DDB on the Drive where the DDB reside?
Depending on the above answers, I would recommend to review the following documentation - http://documentation.commvault.com/commvault/v11/article?p=system_requirements/commcell_sizing/ma_standard_mode.htm
Understanding the DDB sizing would be the first step to determine the cause of the DDB size consumption.
Technically there are various options that can be used to overcome DDB volume size issue:
- Add more disk space (whether it is virutal or physical) and then logicallly extend the DDB volume
- Confirm whether pruning is the cause of the issue, and jobs are not being pruned to free up space on the DDB and Disk Library
- Manually delete jobs that is not needed (note - this is dependent on the organizations need and requirement and should always be consulted before making and changes)
All the above are possible ways to approach DDB volume sizing problems, but please consider which one mets your requirement and needs before proceeding.