Use the upgrade shell script to upgrade the IaaS Components after you update each vRealize Automation 7.1, 7.2 appliance to 7.3 or after you update each vRealize Automation 7.1, 7.2, 7.3 appliance to 7.3.1.
The updated vRealize Automation appliance contains a shell script that you use to upgrade each IaaS node and component.
You can run the upgrade script by using the vSphere console for the virtual machine or by using an SSH console session. If you use the vSphere console, you avoid intermittent network connectivity problems that can break the execution of the script.
If you stop the script while it is upgrading a component, the script stops when it finishes upgrading the component. If other components on the node still must be upgraded, you can run the script again.
When the upgrade finishes, you can review the upgrade result by opening the upgrade log file at /opt/vmware/var/log/vami/upgrade-iaas.log.
Verify the successful update of all vRealize Automation appliances.
If you reboot an IaaS server after you update all the vRealize Automation appliances but before you upgrade the IaaS components, stop all the IaaS services on Windows, except for the Management Agent service.
Before you run the upgrade shell script on the master vRealize Automation appliance node, click the Services on the appliance management console. Verify that each service, except for iaas-service, is REGISTERED.
To install the IaaS Management Agent manually on each IaaS node, finish these steps.
On the Open a browser and navigate to the VMware vRealize Automation IaaS Installation page on the appliance at https://virtual_appliance_host_FQDN:5480/installer.
Download the Management Agent installer, vCAC-IaaSManagementAgent-Setup.msi.
Log in to each vRealize Automation IaaS machine and upgrade the Management Agent with the Management Agent installer. Restart the Windows Management Agent service.
Verify that your primary IaaS Website and Model Manager node has JAVA SE Runtime Environment 8, 64 bits, update 161 or later installed. After you install Java, you must set the environment variable, JAVA_HOME, to the new version on each server node.
Log in to each IaaS Website node and verify that the creation date is earlier than the modified date in the web.config file. If the creation date for the web.config file is the same as or later than the modified date, perform the procedure in Upgrade Fails for IaaS Website Component.
To verify that each IaaS node has an upgraded IaaS Management Agent, perform these steps on each IaaS node:
Log in to the vRealize Automation appliance management console.
Expand the list of all installed components on each IaaS node, and locate the IaaS Management Agent.
Verify that the Management Agent version is current.
Verify that the IaaS Microsoft SQL Server database backup is accessible in case you must roll back.
Verify that snapshots of the IaaS servers in your deployment are available.
If the upgrade is unsuccessful, return to the snapshot and database backup and attempt another upgrade.
- Open a new console session on the vRealize Automation appliance host. Log in with the root account.
- Change directories to /usr/lib/vcac/tools/upgrade/.
It is important that all IaaS Management Agents are upgraded and healthy before running the ./upgrade shell script. If any IaaS Management Agent has a problem when you run the upgrade shell script, see Update Fails to Upgrade the Management Agent.
- Run the upgrade script.
- At the command prompt, enter ./upgrade.
- Press Enter.
For a description of the IaaS upgrade process, see Updating the vRealize Automation Appliance and IaaS Components.
If the Upgrade Shell Script is unsuccessful, review the upgrade-iaas.log file.
You can run the upgrade script again after you fix a problem.
What to do next
If your deployment uses a load balancer, re-enable the vRealize Automation health monitors and the traffic to all nodes.
For more information, see vRealize Automation Load Balancing.