sbhowan09
Contributor
Contributor

Secondary Region within VCF

Jump to solution

Hi all

I have a quesiton with regards to the bring up of the second region with VCF. If the second region is earmarked as a recovery site for the primary region does the script that makes the remote SDDC manager aware of the vRealize Suite within the primary allow SDDC manager to connect the second region workload domains to this "primary" instance as is the case in the primary region or is this a manual process?

A second question also arises in that do you than use vRLCM to deploy new proxy servers for the secondary region for vRA and remote collectors for vROPS and vRB?

Thank in advance

Regards

0 Kudos
1 Solution

Accepted Solutions
tenthirtyam
VMware Employee
VMware Employee

sbhowan09

Today, VMsare Cloud Foundation system instances are not natively aware of each other. As such, the system deployment in "Region B" or "recovery region" is not nativley aware of "Region A" or "primary region". Additionally, in the current version of Cloud Foundation, the addition of vRealize Operations remote collectors and vRealize Automation IaaS Proxy Agents are not automation.

You can, however, manually deploy these the traditional way or use vRealize Suite Lifecycle Manager. Note that you will need to add the vCenter Server instance from Region B into the vRealize Suite Lifecycle Manager instance in Region A, download/upload the peroduct binary from the BOM and then perform the organic expansion / scale to add the objects. However, these will not be added to and reflecting in the SDDC Manager inventory but they will be added to their respective deployment.

-- Ryan Johnson | Staff II Solutions Architect | VCIX-DCV 2020, VCIX-NV 2020, VCAP7-CMA, AWS-CSA, HC:TA, vExpert VMware Inc | CPBU - Solutions Architecture

View solution in original post

0 Kudos
3 Replies
tenthirtyam
VMware Employee
VMware Employee

sbhowan09

Today, VMsare Cloud Foundation system instances are not natively aware of each other. As such, the system deployment in "Region B" or "recovery region" is not nativley aware of "Region A" or "primary region". Additionally, in the current version of Cloud Foundation, the addition of vRealize Operations remote collectors and vRealize Automation IaaS Proxy Agents are not automation.

You can, however, manually deploy these the traditional way or use vRealize Suite Lifecycle Manager. Note that you will need to add the vCenter Server instance from Region B into the vRealize Suite Lifecycle Manager instance in Region A, download/upload the peroduct binary from the BOM and then perform the organic expansion / scale to add the objects. However, these will not be added to and reflecting in the SDDC Manager inventory but they will be added to their respective deployment.

-- Ryan Johnson | Staff II Solutions Architect | VCIX-DCV 2020, VCIX-NV 2020, VCAP7-CMA, AWS-CSA, HC:TA, vExpert VMware Inc | CPBU - Solutions Architecture
0 Kudos
sbhowan09
Contributor
Contributor

tenthirtyam

Thank you again. does makes sense though I am just not sure if there should be any concern if SDDC manager in the future manages upgrades even though its run through LCM for the manual proxies, collectors etc.

Regards

0 Kudos
tenthirtyam
VMware Employee
VMware Employee

sbhowan09​ - Yes, the manual expansion could lead to some potential untested issues for the vRealize Suite components in future automated upgrades if not included in the SDDC Manager inventory. For example, pre-flight checks and snapshots. The product managment team is aware of the need to perform the expansion, such as with vRealize Operations, and add this to the native product capability.

-- Ryan Johnson | Staff II Solutions Architect | VCIX-DCV 2020, VCIX-NV 2020, VCAP7-CMA, AWS-CSA, HC:TA, vExpert VMware Inc | CPBU - Solutions Architecture
0 Kudos