7.0
Table Of Contents
- Reference Architecture
- Contents
- vRealize Automation Reference Architecture Guide
- Updated Information
- New Features in vRealize Automation Since Release 6.2
- Initial Deployment and Configuration Recommendations
- vRealize Automation Deployment
- vRealize Business Standard Edition Deployment Considerations
- vRealize Automation Scalability
- vRealize Business Standard Edition Scalability
- vRealize Automation High Availability Configuration Considerations
- vRealize Business Standard Edition High Availability Considerations
- vRealize Automation Hardware Specifications
- vRealize Automation Small Deployment Requirements
- vRealize Automation Medium Deployment Requirements
- vRealize Automation Large Deployment Requirements
Prior versions of the product that use an external database are still supported. If a deployment has been
upgraded from 6.2 and uses an external database, VMware recommends migrating the database to an
internal configuration. For more information about migrating the database and setting up appliance
database replication, see the vRealize Automation 6.2 product documentation.
MSSQL Database Server for Infrastructure Components
Use an SQL Server Failover Cluster instance for high availability. vRealize Automation does not support
AlwaysOn Availability Groups because the Microsoft Distributed Transactions Coordinator is used.
vRealize Orchestrator
An internal highly-available instance of vRealize Orchestrator is supplied as part of the vRealize
Automation appliance. If you require an external instance of vRealize Orchestrator, you can configure
vRealize Orchestrator in an active-active mode under a load balancer. See the vRealize Orchestrator
documentation.
Reference Architecture
VMware, Inc. 19