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
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.
Scenario: Perform a Maintenance Database Failover
As a vRealize Automation system administrator, you must perform an appliance database maintenance
failover operation.
This scenario assumes that the current master node is up and running normally. There are two database
failover maintenance steps: maintenance of the master and maintenance of a replica node. When a
master node has been replaced so that it becomes a replica, you should perform maintenance on it so
that it is suitable to become the master again should the need arise.
Note Do not stop or restart the HAProxy service on the applicable host machine while performing a
maintenance failover.
Prerequisites
n
vRealize Automation is installed and configured according to appropriate instructions in the Installing
vRealize Automation 7.3.
n
Log in to the vRealize Automation management console as root.
n
Install and configure an appropriate embedded Postgres appliance database cluster.
n
If your database uses synchronous replication mode, ensure that there are three active nodes in the
cluster.
Procedure
1 Remove the master node IP address from the external load balancer.
Managing vRealize Automation
VMware, Inc. 36