vRealize Automation is distributed as a virtual appliance in OVA format. The vRealize Automation appliance includes the cloud automation services, including an embedded vRealize Orchestrator, and database services.

Deployment Type

You consider the deployment type - standard or cluster - according to the design objectives for the availability and number of workloads that the system must support. vRealize Automation is deployed on the first cluster in the management domain. vRealize Automation uses the vRealize Suite Lifecycle Manager instance as its life cycle management engine.

In this design you deploy a vRealize Automation cluster of three nodes and a load balancer on the first cluster in the management domain in Region A. vSphere High Availability protects vRealize Automation by restarting each appliance on an alternate ESXi host if a primary ESXi host failure occurs. vSphere Distributed Resource Scheduler anti-affinity rules prevent the vRealize Automation cluster nodes from running on the same ESXi host.

All vRealize Automation services and databases are configured for high availability by using the underlying Kubernetes orchestration. The vRealize Automation cluster manages the workloads in each region.

Table 1. Design Decisions on Deployment of vRealize Automation

Decision ID

Design Decision

Design Justification

Design Implication


Deploy a single vRealize Automation installation on the first cluster in the management domain in Region A to provide cloud automation services to all regions.

  • vRealize Automation can manage one or more regions and provides a single cloud automation service, regardless of region.

  • vRealize Automation can also manage VMware Cloud on AWS and public cloud instances.

  • Because of the abstraction of the vRealize Automation over virtual networking, it is independent of any physical site locations or hardware.



Deploy vRealize Automation in a cluster configuration by using vRealize Suite Lifecycle Manager.

  • Deploying the cluster configuration that includes the three-node architecture satisfies the design objectives in scope for the design.

  • This design supports the future growth of virtual machines after you expand the cloud infrastructure.



Protect all vRealize Automation nodes by using vSphere High Availability.

Supports the availability objectives for vRealize Automation without requiring manual intervention during a failure event.



Apply vSphere Distributed Resource Scheduler (DRS) anti-affinity rules for the vRealize Automation nodes.

Using vSphere DRS prevents the vRealize Automation cluster nodes from residing on the same ESXi host and risking the high availability of the deployment.

  • You can place only a single ESXi host at a time into maintenance mode for a management cluster of four ESXi hosts.

  • Requires at least four physical hosts to guarantee the three vRealize Automation nodes continue to run if an ESXi host failure occurs.


Add a VM group for the vRealize Automation cluster nodes and set VM rules to restart the Workspace ONE Access VM group before the vRealize Automation VM group.

Defines the startup order of nodes regarding service dependency. The startup order ensures that vSphere HA powers on the virtual machines for vRealize Automation in the correct order.



When using two availability zones in Region A, add the vRealize Automation nodes to the primary availability zone VM group, sfo-m01-cl01_primary-az-vmgroup.

Ensures that, by default, the vRealize Automation nodes are powered on within the primary availability zone hosts group .

If vRealize Automation is deployed after the creation of the stretched clusters for management domain availability zones, the VM group for the primary availability zone virtual machines must be updated to include the vRealize Automation nodes.


Place all cross-region vRealize Automation nodes in a dedicated virtual machine folder, xreg-m01-fd-vra.

Provides the organization of cross-region vRealize Automation virtual appliances in the management domain inventory

You must create the virtual machine folder.

Sizing Compute and Storage Resources

A vRealize Automation cluster deployment has the following resource requirements.

Table 2. vRealize Automation CPU, Memory, and Storage Resources


Per Appliance

Cluster Deployment


12 vCPUs

36 vCPUs


40 GB

120 GB


  • 12.5 GB (thin provisioned)

  • 222 GB (thick provisioned)

  • 37.5 GB (thin provisioned)

  • 666.0 GB (thick provisioned)