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
Table 3‑6. The Potential Replica Fails
Expected Behavior No deployment downtime.
Further Action
n
When the former potential replica comes online, it becomes a potential replica automatically.
No manual action is required.
n
If the former potential replica cannot be repaired, set the appliance database to
asynchronous mode.
Two Node Failure Scenarios
If two out of the three nodes fail simultaneously, vRealize Automation switches to read only mode until a
manual repair is performed.
The following table describes behavior and actions related to a master node and potential replica node
failure in a high availability deployment.
Table 3‑7. The Master Node and Potential Replica Fail
Expected Behavior
n
The sync replica is not promoted to master automatically. vRealize Automation will switch to
read only mode until a manual promotion is performed.
Further Action
n
Manual promotion is required. Set the appliance database to asynchronous mode.
n
When the master and potential replica are recovered, manually set them to synchronize
against the new master. At that point, you can switch vRealize Automation back to
synchronous mode.
n
When two out of three nodes are down simultaneously, vRealize Automation will switch to
read-only mode until you effect a manual repair. If only one database node is available,
switch your deployment to asynchronous mode.
The following table describes behavior and actions related to Sync and Potential node failure in a high
availability deployment.
Table 3‑8. The Sync and Potential Replicas Fail
Expected Behavior
n
The master is unable to process read/write transactions. vRealize Automation functions in
read only mode until a manual repair is performed.
Further Action
n
Manual promotion is required. Set the appliance database to asynchronous mode.
n
When the sync and potential replicas are recovered, they should be manually reset to
synchronize against the master. At this point, you can switch vRealize Automation back to
synchronous mode.
n
When two out of three nodes are down simultaneously, vRealize Automation will switch to
read-only mode until you effect a manual repair. If only one database node is available,
switch your deployment to asynchronous mode.
Links Failures Among Nodes
If a link failure occurs among nodes on a distributed deployment, the automatic failover agent attempts to
repair the configuration.
The following table describes behavior and actions related to a link failure between two sites in a high
availability deployment with the specified configuration when all nodes remain up and online.
Managing vRealize Automation
VMware, Inc. 32