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
Scenario: Perform Manual vRealize Automation Appliance
Database Failover
When there is a problem with the vRealize Automation appliance Postgres database, you manually fail
over to a replica vRealize Automation appliance node in the cluster.
Follow these steps when the Postgres database on the master vRealize Automation appliance node fails
or stops running.
Note Once a node goes into a unhealthy state, do not attempt to use its virtual appliance management
interface for any operations including failover.
Prerequisites
n
Configure a cluster of vRealize Automation appliance nodes. Each node hosts a copy of the
embedded Postgres appliance database.
Procedure
1 Remove the master node IP address from the external load balancer.
2 Log in to the vRealize Automation appliance management interface as root.
https://vrealize-automation-appliance-FQDN:5480
3 Click vRA Settings > Database.
4 From the list of database nodes, locate the replica node with the lowest priority.
Replica nodes appear in ascending priority order.
5 Click Promote and wait for the operation to finish.
When finished, the replica node is listed as the new master node.
6 Correct issues with the former master node and add it back to the cluster:
a Isolate the former master node.
Disconnect the node from its current network, the one that is routing to the remaining
vRealize Automation appliance nodes. Select another NIC for management, or manage it directly
from the virtual machine management console.
b Recover the former master node.
Power the node on or otherwise correct the issue. For example, you might reset the virtual
machine if it is unresponsive.
c From a console session as root, stop the vpostgres service.
service vpostgres stop
d Add the former master node back to its original network, the one that is routing to the other
vRealize Automation appliance nodes.
Managing vRealize Automation
VMware, Inc. 35