7.0
Table Of Contents
- Managing vRealize Automation
- Contents
- Updated Information
- Managing vRealize Automation
- 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
- Updating the vRealize Automation Appliance Management Site Certificate
- Replace a Management Agent Certificate
- Managing the vRealize Automation Postgres Appliance Database
- Backup and Recovery for vRealize Automation Installations
- Configuring the Customer Experience Improvement Program for vRealize Automation
- Adjusting System Settings
- Monitoring vRealize Automation
- Monitoring and Managing Resources
- Bulk Import, Update, or Migrate Virtual Machines
- Managing Machines
- Managing Virtual Machines
- Running Actions for Provisioned Resources
Managing the vRealize Automation Postgres Appliance
Database
vRealize Automation requires the appliance database for system operation. You can manage the
appliance database through the vRealize Appliance Virtual Appliance Management Console (VAMI).
You can configure the database as a single node system or with multiple nodes to facilitate high
availability through failover. The appliance database is set up initially when you install the
vRealize Automation system, and it requires no maintenance unless a machine configuration changes or,
in the case of a clustered system, you need to promote a different node to be the master for some reason.
Note The database clustered configuration is set up automatically when you join a virtual appliance to
the cluster using the Join cluster operation. However, the database cluster is not directly dependent upon
the virtual appliance cluster. For instance, a virtual machine joined to a cluster could be operating
normally even if the embedded Postgres appliance database is not started or has crashed.
There are several options to configuring a high availability appliance database configuration. The most
important consideration is to choose the replication mode for your system. The replication mode
determines how your vRealize Automation deployment maintains data integrity and, for high availability
configurations, how it fails over should the master or primary node fail. There are two available replication
modes: synchronous and asynchronous.
Both replication modes support database failover, though each has advantages and disadvantages.
Synchronous mode minimizes the chances of data loss, but at the cost of system performance and the
need for more hardware. Synchronous mode also requires at least three nodes. Asynchronous mode is
more flexible and affects system performance less at the cost of some increased risk of data loss.
vRealize Automation supports both modes, but operates in asynchronous mode by default and provides
high availability only if there are at least two appliance database nodes. The Database tab on the Virtual
Appliance Management Interface enables you to switch synchronization modes and to add database
nodes as needed. If you start with one node in a non-high availability configuration, you can add nodes
later as desired to enhance high availability. If you have the appropriate hardware and require maximum
protection against data loss, consider configuring your deployment to operate in synchronous mode.
Configure the Appliance Database
Use the Virtual Appliance Management Interface (VAMI) Database page to monitor or update the
configuration of the appliance database. Also, use it to change the master node designation and the
synch mode used by the database.
The appliance database is installed and configured during vRealize Automation system installation and
configuration, but you can monitor and change the configuration from the Administration tab on the Virtual
Appliance Management Interface (VAMI.
The Connection Status field indicates whether the database is connected to the vRealize Automation
system and is functioning correctly.
Managing vRealize Automation
VMware, Inc. 23