The system administrator can deploy and install multiple instances of the vRealize Appliance and individual IaaS components for scale, redundancy, high availability, and disaster recovery.

In this sample architecture, the IaaS components are distributed over multiple machines. This sample installation describes one possible deployment. Load balancers distribute the workload across the servers. In practice, the system administrator chooses a distribution architecture that is compatible with the company environment and goals.

For information about scalability and high availability, see VMware vRealize Automation Reference Architecture at https://www.vmware.com/support/pubs/vcac-pubs.html.

Load balancers distribute the workload across the computing environment. System administrators configure load balancers outside of the vRealize Automation framework.

The following figure shows the components of a distributed deployment. Each component is numbered to correspond to an entry the Distributed Deployment Components table. figure that shows all components of a distrubted deployment described in next table.

The Distributed Deployment Components table describes each component and presents requirements and options for using each component.

Table 1. Distributed Deployment Components

Diagram Number

Description

Requirements and Options

1

vRealize Appliance Load Balancer

Only necessary if you are deploying more than one vRealize Appliance.

Important:

Disable all nodes under the load balancer except for the node you are configuring. For example, if you have three nodes, disable nodes 1 and 2 when you configure node 3.

2

Single Sign-On Server Appliance

One instance of a single sign-on server is required. You can use the vRealize Appliance, which is a product component, or some versions of vSphere SSO, which might be preferable for high-availability deployments. Consult the vCloud Automation Center Support Matrix for information about supported versions.

3

vRealize Appliance 1

One instance required. Multiple instances can be used to support high availability and failover recovery. Multiple instances must be deployed with vSphere High Availability.

4

vRealize Appliance 2, 3, and so on

Deploy multiple instances under the vRealize Appliance Load Balancer.

5

Appliance Database

Appliance Database or cluster. If a two vRealize Appliances have been deployed with Appliance Databases, then they can be clustered. If only one vRealize appliance exists, then there is no highly available method for the database.

6

IaaS Web Load Balancer

Only necessary if you are installing more than one Website Component. Install Website Component 1 and Model Manager Data on one machine under this load balancer.

7

SQL Database Cluster

Install one instance during IaaS installation. Database administrator handles redundancy outside of IaaS context. See Choosing an IaaS Database Scenario.

8

Website Component 1 and Model Manager Data

Required. Install together on one machine under the IaaS Web load balancer. Only one instance of Model Manager Data is allowed. See Install the Primary IaaS Website Component with Model Manager Data

9

Website Component 2, 3, and so on

Optional. Install multiple instances under the IaaS Web load balancer for high availability and failover recovery.

10

IaaS Manager Service Load Balancer

Install the first instance of the Manager Service and the first instance of the DEM Orchestrator together on one machine under this load balancer. See Install the Primary Manager Service and Install the Distributed Execution Managers.

11

Manager Service 1 and DEM Orchestrator 1

Install the first instance of the Manager Service and the first instance of the DEM Orchestrator together on one machine under the IaaS Manager Service load balancer. The first Manager Service instance is active. Only one can be active at any given time. See Install the Primary Manager Service and Install the Distributed Execution Managers.

12

Manager Service 2, 3, and so on

Passive instances for backup only. If the Active Manager Service fails, start the service on the passive node.

13

Agents and DEMs

Install the first DEM Orchestrator on the active Manager Service machine. Install Agents, DEM Orchestrators, and DEM Workers together or on separate machines. See Installing Agents and Install the Distributed Execution Managers.