You begin upgrading VMware Validated Design from the previous version by upgrading the cloud management layer. In the context of the cloud management layer, you start with by upgrading vRealize Automation because it connects to the rest of the cloud management layer components.

You first upgrade the vRealize Automation virtual appliances in Region A. You then perform an automated upgrade of the vRealize Automation Infrastructure-as-a-Service (IaaS) components in Region A and Region B.

Table 4. vRealize Automation Nodes in the SDDC

Region

Role

IP Address

Full Qualified Domain Name

Region A

vRealize Automation Server VIP

192.168.11.53

vra01svr01.rainpole.locall

vRealize Automation Server Appliance

192.168.11.51

vra01svr01a.rainpole.local

192.168.11.52

vra01svr01b.rainpole.local

vRealize Automation for IaaS Web VIP

192.168.11.56

vra01iws01.rainpole.local

vRealize Automation for IaaS Web Server

192.168.11.54

vra01iws01a.rainpole.local

192.168.11.55

vra01iws01b.rainpole.local

vRealize Automation IaaS Model Manager VIP

192.168.11.59

vra01ims01.rainpole.local

vRealize Automation IaaS Model Manager Server

192.168.11.57

vra01ims01a.rainpole.local

192.168.11.58

vra01ims01b.rainpole.local

vRealize Automation IaaS DEM Worker

192.168.11.60

vra01dem01a.rainpole.local

192.168.11.61

vra01dem01b.rainpole.local

vRealize Automation IaaS Proxy Agent

192.168.31.52

sfo01ias01a.sfo01.rainpole.local

192.168.31.53

sfo01ias01b.sfo01.rainpole.local

Microsoft SQL Server for vRealize Automation

192.168.11.62

vra01mssql01.rainpole.local

Region B

vRealize Automation IaaS Proxy Agent

192.168.32.52

lax01ias01a.lax01.rainpole.local

192.168.31.53

lax01ias01b.lax01.rainpole.local

Prerequisites

Verify that all vRealize Automation components have the required compute and storage resources to perform the upgrade, including space for temporary objects created during the process.

Table 1. Hardware Requirements for Upgrading vRealize Automation

Node

Hardware Requirement for Each Node

Description

vRealize Automation Appliances

Available disk space

  • Disk1 with 50 GB

  • Disk3 with 25 GB

  • Disk4 with 50 GB

  • At least 4.5 GB of free disk space on the root partition to download and run the upgrade.

  • At least 4.5 GB of free space on the /storage/db

  • /storage/log subfolder cleaned of older archived ZIP files to free up disk space.

Memory

18 GB

vCPU

4

vRealize Automation IaaS Windows virtual machines and Microsoft SQL Server database

Available disk space

5 GB

Verify that third-party software components required for the upgrade are available on the vRealize Automation nodes.

Table 2. Software Requirements for Upgrading vRealize Automation

Node

Software Requirement

Description

Primary vRealize Autonation IaaS Model Manager Server: vra01iws01a.rainpole.local

Java

  • Java SE Runtime Environment 8 64-bit Update 161 or later installed. Remove versions prior to Update 161.

  • After you install Java, set the JAVA_HOME environment variable to the directory path of the new version.

Download the required software for the upgrade is available on the vRealize Automation nodes and verify the current condition of vRealize Automation .

Table 3. Configuration Prerequisites for Upgrading vRealize Automation

Prerequisite Category

Description

Compatibility

Verify all third-party integrations that might have been configured for use with vRealize Automation are compatible with vRealize Automation version 7.4. Contact the third-party integration vendor or developer to ensure compatibility.

Backup

  • Verify that current backups of the vRealize Automation virtual appliances and the Infrastructure-as-a-Service (IaaS) virtual machines exist.

  • Verify that a current backup of the external vRealize Automation database exists. The default name of the Microsoft SQL Server database is VRADB-01.

Downloads

Download the vRealize Automation VMware-vR-Appliance-7.4.0.xxx-xxxxxxx-updaterepo.iso upgrade file to a shared datastore. If you have space on an NFS datastore, upload the upgrade file to the NFS datastore to save space on your vSAN datastore. You can then mount the .iso file to the vRealize Automation virtual appliances from the vSphere Web Client.

Cluster Integrity and Health

  • Examine the health of vRealize Automation by using the vRealize Production Test Tool to ensure that it is in good health. Remediate any issues prior to beginning the upgrade. See the product download page version 1.7.1.

  • Open a Web browser and log in to the VAMI management interfaces by navigating to https://vra01svr01a.rainpole.local:5480. Select vRA Settings > Cluster and verify that all vRealize Automation IaaS Windows Server nodes meet the following requirements:

    • Have a Last Connected status of less than 30 seconds.

    • Have a Time Offset status of less than 1 second.

  • Open a web browser and log in to both VAMI management interfaces by navigating to https://vra01svr01a.rainpole.local:5480 and https://vra01svr01b.rainpole.local:5480. Select vRA Settings > Cluster and verify that both vRealize Automation virtual appliances meet the following requirements:

    • Have a Last Connected status of less than 10 minutes.

    • The PostgreSQL database is connected and reporting a Status state of Up, indicating that the master and replica nodes are running.

    • The PostgreSQL database is connected and reporting a Valid state of Yes, indicating synchronization between the master and replica nodes.

  • Open a Web browser and log in to both VAMI management interfaces by navigating to https://vra01svr01a.rainpole.local:5480 and https://vra01svr01b.rainpole.local:5480. Select Services and verify that all Services are reporting a status of REGISTERED.

Preparing the vRealize Automation Environment

  • Make the vRealize Automation environment unavailable to end users and any automated integrations during the upgrade maintenance window.

  • Verify that the vRealize Automation environment has been quiesced for all activities, including but not limited to, users ordering new virtual machines and third-party integrations that may automate the ordering of new virtual machines. Without quiescing the environment, rollback operations may be disruptive, generating orphaned objects after snapshots have been created. Remediating such situation might require extending the maintenance window.

  • Verify that you have access to all databases and load balancers that are impacted by, or participate in, the vRealize Automation upgrade.

What to do next

  • Verify that vRealize Automation is operational after the upgrade.