Full DDB disk - Expand drive or Add DDB-partitions?

  • 4 January 2024
  • 2 replies

Userlevel 3
Badge +8
  • Commvault Certified Expert
  • 38 replies


We have a situation with filled up DDB drives in a 3-MA grid setup. XL-sized MAs but with 1.3TB DDB NVMe (should be 2TB according to sizing recommendations). 

The reson for the large DDBs seems to be due to a customer backing up a lot of small files that deduplicate quite well, we see between 25-30 billion secondary records and 2.7 billion unique records on the File DDB partitions. 94-95% dedup and performance is exceptional good with this amount of data in the Storage Pool, 60-70µs and ca 660TB. 

We also see pruning working as lowering retention also reduces the secondary records and give us GB back on the DDB volumes. 

We have two options in this hardware…

  • We can expand the DDB volumes by concatenating (in Windows) another 1.3TB NVMe to the existing one, giving us 2.6TB on the DDB drives.
  • Add one, two or three additional DDB-partitions (one per server) to the DDB, placing them on the extra, available 1.3TB NVMe (MAs in extended mode with 6 DDB partitions, each on a dedicated drive) 

As I see it, the first option will immediately provide more space on the DDB partitions, but is it an optimal setup, with OS-concatenated drives in Windows?

Will the second option help freeing up space on the filled DDB-drives when they already are full or will we still have issues until data is aged off? 


What would be the recommended approach here? 




Best answer by Albert Williams 8 January 2024, 00:18

View original

2 replies

Userlevel 6
Badge +14

Hello @Patrik 

Thanks for the great question! 
First things i will highlight that our Hardware guidelines make a number of assumptions and are just guidelines. Your Dedup rate is much high then what the documentation is written for so you will have to adjust for it to fit your environment. 

Both solutions you provided are suitable from what i can see as they both end in more DDB storage being available and that is your issue. I would lean towards to 3 extra DDB partitions as that will improve performance and be more of a scalable long term solution. 

That being said the first solution will still get you over the line, as more DDB storage is your solution, simple as that.

Kind regards

Albert Williams 

Userlevel 3
Badge +8

Thanks Albert, 

I agree, I like the option to add DDB-patitions as we are able to move to a future forth Media Agent and make the setup more flexible.