Shut down the virtual machines of the SDDC management stack by following a strict order to avoid data loss and faults in the components.
Before you begin:
Verify that virtual machines are not running on snapshots.
Ensure verified backups of all management and tenant virtual machines are available.
If a data protection solution is running on the management clusters, verify that the solution is properly shutdown following the vendor guidance.
If the hosts in a vSAN cluster are to be shut down, appropriately shut down the tenant workloads in the shared edge and compute cluster.
Shutting down the ESXi hosts in the vSAN clusters:
Refer to VMware Knowledge Base article 2142676 for information on preparing and shutting down ESXi hosts in vSAN clusters.
Shutting down the management virtual machines:
Shut down the virtual machines of the SDDC management stack in the shutdown order provided in the following table.
Verify that the console of the virtual machine and its services are completely shut down before moving to the next virtual machine.
The vCenter Server instances, NSX load balancers for the Platform Services Controllers, the Platform Services Controllers, and the management clusters are the last virtual machines to be shut down.
Virtual Machine Name in Region A |
Virtual Machine Name in Region B |
Shutdown Order |
|---|---|---|
vRealize Suite Lifecycle Manager Total Number of VMs (1) |
vRealize Suite Lifecycle Manager Total Number of VMs (0) |
1 |
vrslcm01svr01a |
- |
1 |
vRealize Log Insight Total Number of VMs (3) |
vRealize Log Insight Total Number of VMs (3) |
2 |
sfo01vrli01c |
lax01vrli01c |
1 |
sfo01vrli01b |
lax01vrli01b |
1 |
sfo01vrli01a |
lax01vrli01a |
2 |
vRealize Operations Manager Total Number of VMs (5) |
vRealize Operations Manager Total Number of VMs (2) |
2 |
sfo01vropsc01b |
lax01vropsc01b |
1 |
sfo01vropsc01a |
lax01vropsc01a |
1 |
vrops01svr01c |
- |
2 |
vrops01svr01b |
- |
3 |
vrops01svr01a |
- |
4 |
vRealize Business for Cloud Total Number of VMs (2) |
Realize Business for Cloud Total Number of VMs (2) |
3 |
sfo01vrbc01 |
lax01vrbc01 |
1 |
vrb01svr01 |
- |
2 |
vRealize Automation Total Number of VMs (11) |
vRealize Automation Total Number of VMs (2) |
4 |
vra01dem01a |
- |
1 |
vra01dem01b |
- |
1 |
sfo01ias01b |
lax01ias01b |
1 |
sfo01ias01a |
lax01ias01a |
1 |
vra01ims01b |
- |
2 |
vra01ims01a |
- |
2 |
vra01iws01b |
- |
3 |
vra01iws01a |
- |
4 |
vra01svr01c |
- |
5 |
vra01svr01b |
- |
5 |
vra01svr01a |
- |
5 |
vra01mssql01 |
- |
6 |
Site Recovery Manager and vSphere Replication Total Number of VMs (2) |
Site Recovery Manager and vSphere Replication Total Number of VMs (2) |
5 |
sfo01m01vrms01 |
lax01m01vrms01 |
1 |
sfo01m01srm01 |
lax01m01srm01 |
2 |
Update Manager Download Service (UMDS) Total Number of VMs (1) |
Update Manager Download Service (UMDS) Total Number of VMs (1) |
5 |
sfo01umds01 |
lax01umds01 |
1 |
Core Stack Total Number of VMs (26) |
Core Stack Total Number of VMs (16) |
6 |
sfo01m01lb01 (0,1) |
lax01m01lb01 (0,1) |
1 |
sfo01m01udlr01 (0,1) |
- |
1 |
sfo01m01esg01 |
lax01m01esg01 |
1 |
sfo01m01esg02 |
lax01m01esg02 |
1 |
sfo01w01udlr01 (0,1) |
- |
1 |
sfo01w01dlr01 (0,1) |
lax01w01dlr01 (0,1) |
1 |
sfo01w01esg01 |
lax01w01esg01 |
1 |
sfo01w01esg02 |
lax01w01esg02 |
1 |
sfo01m01nsx01 |
lax01m01nsx01 |
2 |
sfo01w01nsx01 |
lax01w01nsx01 |
2 |
sfo01m01nsxc01 |
- |
3 |
sfo01m01nsxc02 |
- |
3 |
sfo01m01nsxc03 |
- |
3 |
sfo01w01nsxc01 |
- |
3 |
sfo01w01nsxc02 |
- |
3 |
sfo01w01nsxc03 |
- |
3 |
sfo01m01vc01 |
lax01m01vc01 |
4 |
sfo01w01vc01 |
lax01w01vc01 |
4 |
sfo01psc01 (0,1) |
lax01psc01 (0,1) |
5 |
sfo01w01psc01 |
lax01w01psc01 |
6 |
sfo01m01psc01 |
lax01m01psc01 |
6 |
