7.3
Table Of Contents
- Managing vRealize Automation
- Contents
- Managing vRealize Automation
- Updated Information
- Maintaining and Customizing vRealize Automation Components and Options
- Broadcast a Message on the Message Board Portlet
- Starting Up and Shutting Down vRealize Automation
- Updating vRealize Automation Certificates
- Extracting Certificates and Private Keys
- Replace Certificates in the vRealize Automation Appliance
- Replace the Infrastructure as a Service Certificate
- Replace the IaaS Manager Service Certificate
- Update Embedded vRealize Orchestrator to Trust vRealize Automation Certificates
- Update External vRealize Orchestrator to Trust vRealize Automation Certificates
- Updating the vRealize Automation Appliance Management Site Certificate
- Replace a Management Agent Certificate
- Change the Polling Method for Certificates
- Managing the vRealize Automation Postgres Appliance Database
- Backup and Recovery for vRealize Automation Installations
- The Customer Experience Improvement Program
- Adjusting System Settings
- Monitoring vRealize Automation
- Monitoring vRealize Automation Health
- Monitoring and Managing Resources
- Monitoring Containers
- Bulk Import, Update, or Migrate Virtual Machines
Appliance Database Failover
In a high availability configuration, the master constantly streams transactions to the replica servers. If the
master fails, the active and working replica is ready to proceed with read-only requests. When the new
master is promoted, either manually or automatically, all of the upcoming requests are moved to it.
Three Node Appliance Database Automatic Failover Scenarios
There are several appliance database high availability failover scenarios, and vRealize Automation
behavior varies depending on appliance database configuration and the number of nodes that fail.
Single Node Failure Scenarios
If one of the three nodes fails, vRealize Automation will initiate an auto failover. No additional auto failover
operations can occur until all three nodes are restored.
The following table describes behavior and actions related to a master node failure in a high availability
deployment.
Table 3‑4. The Master Node Fails
Expected Behavior
n
The configured sync replica node becomes the master and automatically picks up appliance
database functionality.
n
The potential sync replica becomes the sync standby node.
n
The vRealize Automation deployment functions in read only mode until the automatic failover
completes.
Further Action
n
When the former master is recovered, it will be reset as replica automatically by the failover
agent repair logic. No manual action is required.
n
If the former master cannot be recovered, manually set the appliance database to
asynchronous mode.
The following table describes behavior and actions related to a sync replica node failure in a high
availability deployment.
Table 3‑5. The Sync Replica Fails
Expected Behavior
n
The vRealize Automation deployment experiences no downtime. There will be a delay of a
couple of seconds for database requests until the potential replica becomes the new sync
replica. The appliance database performs this action automatically.
Further Action
n
When the former synch replica comes online, it will become a potential replica automatically.
No manual action is required.
n
If the former sync replica cannot be repaired, manually set the appliance database to
asynchronous mode.
The following table describes behavior and actions related to a master node failure in a high availability
deployment.
Managing vRealize Automation
VMware, Inc. 31