Hi @Egor Skepko, thanks for the question.

Please would you confirm if the DDB itself is getting full or if the disk hosting the DDB is getting filled and running low on free space?

In the meantime, please take a look at Deduplication Management:
https://documentation.commvault.com/commvault/v11/article?p=12560.htm

In particular, there are options for Compacting DDB or Moving Clients from a Full DDB to new DDB.

Thanks,

Stuart

Hi @Stuart Painter

The disk self getting full, we have 2 MA with same amount of Disk space 1.4TB, on first MA DDB disk olny 60% full and on another MA only like 50GB free space. We can't add new disk to make new partition for new DDB, there is nog more space. 

For the Compacting you have to move DDB to another partition, If its so we dont have it and cant add it.

And i think the trigger of the problem is, that the DDB data verification wasnt enable for this DDB.

Hi @Egor Skepko, 

The best practice is to run compaction and enable garbage collection.

With garbage collection enabled it can significantly reduce bloat on the DDB partitions.

https://documentation.commvault.com/commvault/v11/article?p=12613.htm

Example steps:

1 - Suspend any running jobs to the Media Agent
2 - ensure no SIDB2 process is running on the Media Agent
3 - Run compaction:
sidb2 -compactfile secondary -i <DDB_ID> -split <split_number>

Note: 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. 

When compaction has been run you can then enable the garbage collection option on the DDB engine. 

https://documentation.commvault.com/commvault/v11/article?p=108822.htm

 

Hi @Martin Williams 

The garbage collecation is alrdy enabled and for compaction you need more space on the disk wich we dont have it. 

@Egor Skepko , is it possible to move the DDB to a larger drive or allocate more space where it lives now?  If you can then follow @Martin Williams ‘s advice, you may gain space and no longer need the allocated extra.

@Mike Struening No we cant add extra disk or move to another. There is DDB reconstruction going and we wil see after how much free space we have and if enough free space we gonna try Comapcting.

Run a Full recon .. it would for sure  free space for you

@ravikasappa The full reconstruction is running alrdy, we wil. Thank you for the tips.

Ok, good.  I misunderstood your original post that you lacked space to do any recon or compaction.  @ravikasappa is right.

Keep us posted!!

De Full Recon, finish and we made 180G free space. Is there any userfull rteport where i can see how much DDBu space left after each aux or backup. Or does someone know how much GB used for each aux GB or backup? 

@Egor Skepko , I think this will make your day:

https://documentation.commvault.com/11.22/expert/39443_deduplication_database_size_and_growth_report.html

You can schedule this to run as frequently as you’d like until you get a hang for the changes and expected growth.

I was going to ask the same question, thanks for the advice..

@gary mcneely , be sure to mark the Best Answer as helpful so more people see it