7.2
Table Of Contents
- Reference Architecture
- Contents
- vRealize Automation Reference Architecture Guide
- Updated Information
- Initial Deployment and Configuration Recommendations
- vRealize Automation Deployment
- vRealize Business for Cloud Deployment Considerations
- vRealize Automation Scalability
- vRealize Business for Cloud Scalability
- vRealize Automation High Availability Configuration Considerations
- vRealize Business for Cloud High Availability Considerations
- vRealize Automation Hardware Specifications
- vRealize Automation Small Deployment Requirements
- vRealize Automation Medium Deployment Requirements
- vRealize Automation Large Deployment Requirements
- Index
vRealize Automation High Availability
Configuration Considerations 6
If you require maximum system robustness, congure your vRealize Automation system for high
availability in accordance with VMware guidelines.
vRealize Automation Appliance
The vRealize Automation appliance supports active-active high availability for all components except the
appliance database. To enable high availability for these appliances, place them under a load balancer. For
more information, see Installing vRealize Automation 7.2. Beginning with the 7.0 release, the appliance
database, and vRealize Orchestrator are automatically clustered and available for use.
vRealize Automation Appliance Database Server
Though the appliance database is automatically clustered within the vRealize Automation appliance,
failover is a manual operation. In the event of a failure, you must promote a node to be the new master on
the Virtual Appliance Management Console vRA > Database tab.
vRealize Automation Directories Management
Each vRealize Automation appliance includes a connector that supports user authentication, although only
one connector is typically congured to perform directory synchronization. It does not maer which
connector you choose to serve as the sync connector. To support Directories Management high availability,
you must congure a second connector that corresponds to your second vRealize Automation appliance,
which connects to your Identity Provider and points to the same Active Directory. With this conguration, if
one appliance fails, the other takes over management of user authentication.
In a high availability environment, all nodes must serve the same set of Active Directories, users,
authentication methods, etc. The most direct method to accomplish this is to promote the Identity Provider
to the cluster by seing the load balancer host as the Identity Provider host. With this conguration, all
authentication requests are directed to the load balancer, which forwards the request to either connector as
appropriate.
For more information about conguring Directories Management for high availability, see Conguring
vRealize Automation.
Infrastructure Web Server
The Infrastructure Web server components all support active-active high availability. To enable high
availability for these components, place them under a load balancer.
VMware, Inc.
23