7.4
Table Of Contents
- Managing vRealize Automation
- Contents
- Managing vRealize Automation
- 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
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.
e From a console session as root, restart the haproxy service.
service haproxy restart
f Log in to the new vRealize Automation appliance master node management interface as root.
g Click vRA Settings > Database.
h Locate the former master node, and click Reset.
i After a successful reset, restart the former master node.
j With the former master powered on, verify that the following services are running.
haproxy
horizon-workspace
rabbitmq-server
vami-lighttp
vcac-server
vco-server
k Re-add the former master node to the external load balancer.
Note If a master node that was demoted to replica is still listed as master, you might need to
manually re-join it to the cluster to correct the problem.
Managing vRealize Automation
VMware, Inc. 33