7.2

n
For high-availability environments with load balancers, verify that you disabled all of the redundant
nodes and removed the health monitors for these items according to your load balancer documentation.
n
vRealize Automation appliance
n
IaaS Website
n
IaaS Manager Service
n
For high-availability environments with load balancers, verify that the trac is directed only to the
primary node.
n
Verify that the IaaS service hosted in Microsoft Internet Information Services (IIS) is running by
performing the following steps:
a Enter the URL https://webhostname/Repository/Data/MetaModel.svc to verify that the Web
Repository is running. If successful, no errors are returned and you see a list of models in XML
format.
b Log in to the IaaS Website and check that the status recorded in the Repository.log le reports OK.
The le is located in the VCAC home folder at /Server/Model Manager Web/Logs/Repository.log.
N For a distributed IaaS Website, log in to the secondary website, without MMD, and stop
Microsoft IIS temporarily. Check the MetaModel.svc connectivity to ensure that the load balancer
trac is only going through the primary Web node, and restart the Microsoft IIS.
n
If you have a Common Components Catalog component installed in your environment, uninstall the
component before you upgrade. For information, see the Common Components Catalog Installation Guide
or follow the steps provided in the “Checklist for Upgrading vRealize Automation 7.1,” on page 8.
n
Verify that all IaaS nodes are in a healthy state by performing the following steps:
a Go to the management console for your primary virtual appliance by using its fully qualied
domain name, hps://va-hostname.domain.name:5480.
b Log in with the user name root and the password you specied when the appliance was deployed.
c Select vRA  > Cluster.
d Under Last Connected in the table, verify that the IaaS nodes have a last connected time of less
than 3 minutes and that the virtual appliance nodes have last connected time of less than 10
minutes. If all the IaaS nodes are not in communication with the vRealize Automation appliance,
the upgrade fails.
To diagnose connectivity issues between the Management Agent and virtual appliance, log in to
the IaaS node that is not listed and check the Management Agent logs. Restart the Management
Agent if it is not running in the Services console.
e Note any orphaned nodes listed in the table. An orphaned node is a duplicate node that is reported
on the host but does not exist on the host. You must delete all orphaned nodes. For more
information, see “Delete Orphaned Nodes on vRealize Automation,” on page 42 .
n
If you have a replica virtual appliance that is no longer part of the cluster, you must delete it from the
cluster table. If you do not delete this appliance from the table, the upgrade process aempts to update
the appliance and displays a warning message that the replica update is unsuccessful.
n
Verify that all saved and in-progress requests have nished successfully before you upgrade.
n
If you plan to use the IaaS shell upgrade script to upgrade the IaaS components after you update the
vRealize Automation 7.1 appliance, see “Exclude Management Agents from Upgrade,” on page 46.
Upgrading from vRealize Automation 7.1 to 7.2
16 VMware, Inc.