Skip to main content
commvault.com commvault.com

As far as I remember the Back-end Size for Disk Storage table below there was the expression disk instead of location. Any concept changes?

 

 

URL:

https://documentation.commvault.com/2022e/expert/111985_hardware_specifications_for_deduplication_mode.html

Anyway, why would we need two locations instead of one? To expand managed capacity? In the same Storage Pool? Let's imagine a storage pool with 4 nodes. Here storage pool and grid are synonyms. Right? So, each node with two disks of 2 TB SSD Class Disk/PCIe IO Cards?

 

This two-disk (two-locations) configuration appears to suit the "Cross-site Replication Sample Configuration" scenario. A cross-site replication setup is when data from one site is backed up on location and a secondary copy of the backup is maintained on site two. Also, the site two has its own data backed up on location and a secondary copy of that data is maintained on site one.

 

 

 

 

I think you are referring to extended mode which has a couple scenarios.

 

Partition extended mode: In this mode the MediaAgents host partitions from multiple storage pools (up to 20 storage pools per grid). Each storage pool can be configured with 1, 2, 4, or 6 partitions.

You can use the partition extended mode in the following scenarios:

  • When you want the primary copy of the data on the disk and the secondary copy on the cloud. In this case, create 1 disk storage pool and 1 cloud storage pool using the same MediaAgents.
  • In case of multi-tenancy, where the total back-end size of multiple tenants together is within the limit of the grid. In this case, to segregate data for each tenant you can configure the partition in extended mode by creating a separate storage pool for each tenant using the same MediaAgents.

In the past extended mode had a 3rd use case - where we’d separate out short and long term retention. Before the garbage collection DDB enhancements, mixed retention could reduce scale, and so extended mode was a way to avoid those issues. With DDB garbage collection that is no longer required.

Reply


Terms & ConditionsCookie settings