Hello,
I have a DASH copy from the Prod site to the DR site. The DDUP partition on the DR site appears to be running out of space, so the Aux copy has been stopped.
What should I do to resume the auxiliary copy? I can’t add more space.
Thanks
Solved
DDUP Partition ruining out of space.
- Apprentice
Best answer by Collin Harper
Hello
Deleting deduplicated jobs will not gain you much space back. This is because DDB Baseline (unique data written to storage) does not get deleted until all jobs that ran after the baseline was written have aged. Once no jobs reference the block in baseline, the baseline block(s) will age. If you delete data you will only be deleting Secondary References which are of a few Kb in size.
Can you check SIDBEngine.log and search for Pending Deletes? This will tell you if prunable records are being deleted. SIDBPrune.log will also tell you if there are any pruning errors.
If there are no errors can you make sure Garbage Collection is enabled? This is an enhanced pruning and cleanup change we made to DDBs a few Services Packs back.
It may also be worth it to run DDB Primary Compaction as ArunKumar suggested.
Thank you,
Collin
+9- Vaulter
Hi
Please confirm.
+9- Vaulter
https://documentation.commvault.com/v11/expert/111985_hardware_specifications_for_deduplication_mode.html
If the DDB is not sized as per our recommendation then I would advice you to increase it. If not possible, then I would advise creating a new disk as per our recommendation and move the DDB to the new location.
https://documentation.commvault.com/2022e/expert/12576_moving_deduplication_database.html
If its sized as per the recommendation then there is process to compact the DDB to release some space. But, to run the compacting process, the free space must be double the size of the largest data file. If the free space is not sufficient, then the compacting process might fail and the DDB might get corrupted.
https://documentation.commvault.com/2022e/expert/12613_compacting_deduplication_database.html
Kindly let me know if you have any queries.
- Vaulter
- Answer
Hello
Deleting deduplicated jobs will not gain you much space back. This is because DDB Baseline (unique data written to storage) does not get deleted until all jobs that ran after the baseline was written have aged. Once no jobs reference the block in baseline, the baseline block(s) will age. If you delete data you will only be deleting Secondary References which are of a few Kb in size.
Can you check SIDBEngine.log and search for Pending Deletes? This will tell you if prunable records are being deleted. SIDBPrune.log will also tell you if there are any pruning errors.
If there are no errors can you make sure Garbage Collection is enabled? This is an enhanced pruning and cleanup change we made to DDBs a few Services Packs back.
It may also be worth it to run DDB Primary Compaction as ArunKumar suggested.
Thank you,
Collin
Readiverse Academy Certifications
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.