Use the upgrade shell script to upgrade the IaaS Components after you update each vRealize Automation appliance.
About this task
The updated primary or master 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 the script is upgrading a component, the script runs until the upgrade is finished on the component. If any components on the node are not upgraded, you must run the script again.
When the upgrade finishes, you can review the upgrade result by opening the upgrade log file at /usr/lib/vcac/tools/upgrade/upgrade.log.
Verify the successful update of all vRealize Automation appliances.
If you reboot an IaaS server after you update all the vRealize Automation appliances, you must stop the IaaS Windows services. Before you upgrade the IaaS components, stop all the IaaS Windows services, except for the Management Agent service, on the server.
Before you run the upgrade shell script on the master or primary vRealize Automation appliance node, verify that each service is REGISTERED.
Go to the appliance management console for your virtual appliance by using its fully qualified domain name: https://va-hostname.domain.name:5480.
Log in with the user name root and the password you entered when the appliance was deployed.
Verify that each service, except the iaas-service, is REGISTERED.
Upgrade the Management Agent on each vRealize Automation IaaS virtual machine.
Open a browser and navigate to the VMware vRealize Automation IaaS Installation page on thevRealize Automation appliance using the fully qualified domain name: https://virtual_appliance_host:5480/installer.
Click Management Agent Installer.
By default, the installer is downloaded to the Downloads folder.
Log in to each vRealize Automation IaaS virtual machine, upgrade the Management Agent with the Management Agent Installer file, and restart the Windows Management Agent service.
Verify that your primary IaaS Website node where the Model Manager data is installed has JAVA SE Runtime Environment 8, 64 bits, update 111 or later installed. After you install Java, you must set the environment variable, JAVA_HOME, to the new version.
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.
Delete all orphaned IaaS nodes. See Delete Orphaned Nodes on vRealize Automation.
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 primary or master vRealize Automation appliance node and log in with the root account.
If you plan to run the upgrade script with SSH, open an SSH console session.
- Change directories to /usr/lib/vcac/tools/upgrade/.
- At the prompt, run this command to create the upgrade.properties file.
- Open the upgrade.properties file and enter all the required values.
This table shows the required values, which vary depending on the environment. For example, on a node that contains a DEM worker or orchestrator, DEM credentials are required.
User name for the primary Web node. Required only once.
Password for the primary Web node. Required only once.
User name for the DEM worker or DEM orchestrator. Required for each node where a DEM component is installed.
Password for the DEM worker or DEM orchestrator. Required for each node where a DEM component is installed.
User name for an agent such as a vSphere agent. Required for each node where an agent component is installed.
Password for an agent such as a vSphere agent. Required for each node where an agent component is installed.
The VIDM administrator password. Required only when you upgrade from vRealize Automation 6.2.5.
For security reasons, the upgrade.properties file is removed when you run the upgrade shell script. The properties in the file are defined using the information for each IaaS component that comes through the IaaS Management Agents. It is important that all IaaS Management Agents are upgraded and healthy before running the ./generate_properies or ./upgrade_from_62x shell scripts. If any IaaS Management Agent has a problem when you run the upgrade shell script, see Update Fails to Upgrade the Management Agent. To recreate the upgrade.properties file, repeat steps 2 and 3.
- Run the upgrade script.
- At the command prompt, enter ./upgrade_from_62x.
- Press Enter.
The script displays each IaaS node and all the components installed on it. The script validates each component before installing the upgrade. If there are incorrect values in the upgrade.properties file, the script fails.
The first IaaS server component can take about 30 minutes to finish. During the upgrade, you see a message similar to
Upgrading server components for node web1-vra.mycompany.com.
If the upgrade shell script is unsuccessful, review the upgrade.log file.
You can run the upgrade script again after you fix a problem. Before you run the upgrade script again, recreate the upgrade.properties file, open it, and enter all the required values.
- (Optional) Enable automatic Manager Service failover. See Enable Automatic Manager Service Failover After Upgrade.