You can use virtual machine groups to define the startup order of virtual machines. vSphere HA follows this order when powering on the virtual machines in the group. In Region B, create the virtual machine groups defining the startup order of the cloud management virtual machines that are failed over from Region A.
VM-Host Group Name | VM-Host Group Member |
---|---|
vRealize Automation IaaS Database | vra01mssql01 |
vRealize Automation Virtual Appliances | vra01svr01a |
vra01svr01b | |
vra01svr01c | |
vRealize Automation IaaS Web Servers | vra01iws01a |
vra01iws01b | |
vRealize Automation IaaS Managers | vra01ims01a |
vra01ims01b | |
vRealize Automation IaaS DEM Workers | vra01dem01a |
vra01dem01b | |
vRealize Automation IaaS Proxy Agents | lax01ias01a |
lax01ias01b |
VM/Host Rule Name | First Restart Virtual Machines in Group | Then Restart Virtual Machines in Group |
---|---|---|
SDDC Cloud Management Platform 01 | vRealize Automation IaaS Database | vRealize Automation Virtual Appliances |
SDDC Cloud Management Platform 02 | vRealize Automation Virtual Appliances | vRealize Automation IaaS Web Servers |
SDDC Cloud Management Platform 03 | vRealize Automation IaaS Web Servers | vRealize Automation IaaS Managers |
SDDC Cloud Management Platform 04 | vRealize Automation IaaS Managers | vRealize Automation IaaS DEM Workers |
SDDC Cloud Management Platform 05 | vRealize Automation IaaS Managers | vRealize Automation IaaS Proxy Agents |