Multiple datacenters in one region

Hi @John Robert , hope all is well.

Regions are meant to denote physical areas of geography and the storage within to tell clients to use those local resources.

For those following along, here’s the docs:

https://documentation.commvault.com/2022e/essential/107547_regions.html

In your case, you’re using the region functionality without using the intention (i.e. you are dividing resources but within the same geographic area).

I’m going to ask internally if there’s any better method here (or if we need a CMR).

You could also use tags to better set things up in this specific a scenario, though I totally see where you are thinking here.

https://documentation.commvault.com/2022e/essential/139220_creating_tag_for_entity.html

Hi @Mike Struening,

You can say I may want to use the intention of regionbased. But in my case the geographical area is a bit smaller especially in this usecase, and the only reason i discovered it was that one region was azure norway east located in oslo, and a local datacenter in oslo.  So the question is how big should a region be? 

Currently a region can be defined as two neighbouring areas. like Woodside and Jackson Heights in New York 2.2 km apart from each other (assuming that there is no other behind the scene logic than name of location deciding if it is identical). This works great for US and probably other big cities, as you have divided locations down to smaller locations. as the example of Woodside and Jackson heights. But in Norway, Oslo is one location. 20 km across.

---

In afterthought I see that for my environment I think plan rules would be the way forward for me, as they would scale more in a multi-tenant environment with company associations. as the regions would be visible for all and thus could not contain customer locations.