MongoDB Protection Large Sharded Cluster ( 100+ nodes )

Hi ​@Mohit Chordia 

Can you confirm CV, DB and node's OS version here?

OS - Rocky Linux 8.10 
CV - 11.44.15

DB version - Checking 

Hi Mohit , 

can you please share these details about your cluster .
1. Number of Shards in the cluster 
2. Typical number of Nodes in a shard​​​​​​​.
3. MongoDB Data path is on local disk LVM or some external Storage vendor ​​​​​​​
4. MongoDB and Commvault Version .
5. Nodes are local machines hosted on hypervisor or cloud VM’s​​​​​​​

1. Number of Shards in the cluster - 40 
2. Typical number of Nodes in a shard - 3 
3. MongoDB Data path is on local disk LVM or some external Storage vendor ​​​​​​​ - Local Disk LVM 
4. MongoDB and Commvault Version - Percona db version v6.0.9-7 , 11.44.15 
5. Nodes are local machines hosted on hypervisor or cloud VM’s​​​​​​​ - all data nodes are physicals - 3 config nodes are VMs
​​​​​​​

Hi Mohit , 

We reviewed the configuration,
MongoDB environment in the 70-80 TB range is within the capabilities of the Commvault solution

However, cluster scaling across 40 shards and 120 Nodes is something we need to replicate and validate internally before we can provide recommendations.

Could you please confirm the maximum number of shards, replica sets, nodes, and overall cluster size that have been tested and validated by Commvault?

Additionally, the current approach of taking snapshots on the secondary node needs to be reviewed. Most of our physical nodes do not have sufficient free space available in the VG (Volume Group), and adding additional space is not straightforward in the existing setup.

We would like to understand if Commvault supports any alternative approach that does not require additional VG space on the secondary nodes.