Skip to main content
commvault.com commvault.com
Solved

Issue about The number of partitions created automatically by Commvault 11.40

  • May 11, 2026
  • 1 reply
  • 17 views
E
Apprentice
Forum|alt.badge.img+10

The number of partitions created is determined by the number of DDB MediaAgents selected during configuration:

  • 1 MediaAgent selected

    • Two partitions are created on the single MediaAgent.

  • 2 MediaAgents selected

    • Two partitions are created on each MediaAgent, for a total of four partitions.

  • 3 to 6 MediaAgents selected

    • A total of six partitions are created and distributed evenly across the selected MediaAgents.

  • More than 6 MediaAgents selected

    • The first six MediaAgents are used to create the six partitions.

    • The remaining MediaAgents are assigned the Deduplication Database (DDB) role only.

The software automatically assigns the deduplication database (DDB) path on the MediaAgent without requiring user input.

Link Configuring Disk Storage

I couldn't quite understand the final part where more than 6 MediaAgents are selected. Can someone explain it in other words?

Best answer by Paul G

Hi ​@Eduardo Braga,

When you would create storage with more than 6 Media Agents, Media agents 7 and up are assigned the DDB role only but will not host a DDB partition. They can still perform signature generation if you do not want to perform this on the client but will do Q&I actions on a DDB partition on another MA.

I have never created a storage setup where I use more than 6 MA's for a single storage library so I don't have experience with this setup but I know of the option to implement a deduplication MA that does not host it's own DDB partition.

If you just configure this for 6 MA's or less, it won't impact your situation.

Kind regards,

Paul

    1 reply

    Paul G
    Explorer
    Forum|alt.badge.img+1
    • Paul GExplorer
    • Explorer
    • Answer
    • May 12, 2026

    Hi ​@Eduardo Braga,

    When you would create storage with more than 6 Media Agents, Media agents 7 and up are assigned the DDB role only but will not host a DDB partition. They can still perform signature generation if you do not want to perform this on the client but will do Q&I actions on a DDB partition on another MA.

    I have never created a storage setup where I use more than 6 MA's for a single storage library so I don't have experience with this setup but I know of the option to implement a deduplication MA that does not host it's own DDB partition.

    If you just configure this for 6 MA's or less, it won't impact your situation.

    Kind regards,

    Paul

    Terms & ConditionsAccessibility statement