When you upgrade the Cloud Management Platform as a part of the upgrade from VMware Validated Design 4.0 to VMware Validated Design 4.1, you start with vRealize Automation. vRealize Automation is the central engine that connects to the rest of the Cloud Management Platform components like vRealize Orchestrator and vRealize Business.

About this task

When you update the vRealize Automation instance as a part of the upgrade from VMware Validated Design 4.0 to VMware Validated Design 4.1, you first upgrade the vRealize Automation Appliances in Region A. Then, you perform automated upgrade of the 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.local

vRealize Automation Server Appliance

192.168.11.51

vra01svr01a.rainpole.local

192.168.11.52

vra01svr01b.rainpole.local

vRealize Automation for IaaS Web Server 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 Model Manager IMS VIP

192.168.11.59

vra01ims01.rainpole.local

vRealize Automation Model Manager IMS

192.168.11.57

vra01ims01a.rainpole.local

192.168.11.58

vra01ims01b.rainpole.local

vRealize Automation DEM Workers

192.168.11.60

vra01dem01a.rainpole.local

192.168.11.61

vra01dem01b.rainpole.local

vRealize Automation 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 Proxy Agent

192.168.32.52

lax01ias01a.lax01.rainpole.local

192.168.31.53

lax01ias01b.lax01.rainpole.local

Note:

VMware Validated Design 4.1 introduces a new convention for host and object names in the SDDC. The step-by-step upgrade guidance uses the new names for both the pre- and post-upgrade SDDC setups. For information about the new convention, see Mapping Component Names Between Versions 4.0 and 4.1 of VMware Validated Design.

Prerequisites

Verify that the vRealize Automation nodes have enough compute and storage resources for the operations and temporary objects created during upgrade.

Table 1. Hardware Requirements for Upgrading vRealize Automation

Node

Hardware Requirement for Each Node

Description

vRealize Automation Appliances

Disk space

  • Disk1 with 50 GB, Disk3 with 25 GB, and 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 database

Disk space

5 GB

Verify that the software that is required for the upgrade is available on the vRealize Automation nodes.

Table 2. Software Requirements for Upgrading vRealize Automation

Node

Software Requirement

Description

Primary IaaS Model Manager Windows virtual machine vra01iws01a.rainpole.local

Java Version

  • Java SE Runtime Environment 8 64- bits Update 111 or later installed. Remove versions earlier than Update 111.

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

Verify that the condition of the SDDC and download the software that is required for the upgrade is available on the vRealize Automation nodes.

Table 3. Configuration Prerequisites for Upgrading vRealize Automation

Prerequisite Category

Description

Compatibility

Verify that any third-party integration that might have been configured with vRealize Automation is compatible with version 7.3. Contact the vendor of the third-party software to check compatibility and availability.

Backup

  • Verify that backups of the vRealize Automation Virtual Appliances and the Infrastructure-as-a-Service (IaaS) Virtual Machines exist. See the VMware Validated Design Backup and Restore documentation.

  • Verify that a backup the vRealize Automation database exists on the appliance. The default name of the database is VRADB-01.

Downloads

  • Download the vRealize Automation VMware-vR-Appliance-7.3.0.xxx-xxxxxxx-updaterepo.iso upgrade file to a shared datastore. You can then mount the .iso file to the vRealize Automation virtual machines from the vSphere Web Client.

    If you have space on your NFS datastore, upload the file there.

  • Download the vRealize Automation IaaS Management Agent .msi file to the Windows host that you use to access the data center. See the product download page for vRealize Automation.

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 of the upgrade. See the product download page version 1.7.0.

  • Verify that all IaaS Windows nodes meet the following requirements in the appliance management interface at https://vra01svr01a.rainpole.local:5480:

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

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

  • Verify that both vRealize Automation appliances meet the following requirements in the appliance management interface at https://vra01svr01a.rainpole.local:5480 and https://vra01svr01b.rainpole.local:5480 :

    • 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.

    • All Services are reporting a status of REGISTERED

Preparing the vRealize Automation environment

  • Make the system unavailable to end users and any automated components while you perform the upgrade.

  • Verify that the vRealize Automation environment has been quiesced of all activities, including but not limited to, users ordering new virtual machines and third-party integration that might automate the ordering of new virtual machines. Without quiescing the environment, rollback operations might be disruptive, generating orphaned objects that were created after snapshots have been created. You might also have to extend the time of 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. See Validate vRealize Automation in the VMware Validated Design Operational Verification documentation.