If you have already installed vRealize Operations, you can update your software when a newer version becomes available.

Note: Installation might take several minutes or even a couple hours depending on the size and type of your clusters and nodes.
Note: vRealize Application Remote Collector virtual appliance is deprecated and is no longer available for download from the vRealize Operations​​ user interface when you upgrade to vRealize Operations 8.6. VMware recommends that you use cloud proxy to monitor your application services. You can migrate on-prem standalone ​ vRealize Application Remote Collector to on-prem cloud proxy​. For information about migrating from vRealize Application Remote Collector to cloud proxy, see KB 83059.

Prerequisites

  • Create a snapshot of each node in your cluster. For information about how to perform this task, see the vRealize Operations Information Center.
  • Obtain the PAK file for your cluster. For information about which file to use, see the vRealize Operations Information Center.

  • Before you install the PAK file, or upgrade your vRealize Operations instance, clone any customized content to preserve it. Customized content can include alert definitions, symptom definitions, recommendations, and views. Then, during the software update, you select the options named Install the PAK file even if it is already installed and Reset out-of-the-box content.

  • Since version 6.2.1, vRealize Operations update operation has a validation process that identifies issues before you start to update your software. Although it is good practice to run the pre-update check and resolve any issues found, users who have environmental constraints can disable this validation check.

    To disable the pre-update validation check, perform the following steps:

    • Edit the update file to /storage/db/pakRepoLocal/bypass_prechecks_vRealizeOperationsManagerEnterprise-buildnumberofupdate.json.
    • Change the value to TRUE and run the update.
    Note: If you disable the validation, you might encounter blocking failures during the update itself.

Procedure

  1. Log into the master node vRealize Operations administrator interface of your cluster at https://master-node-FQDN-or-IP-address/admin.
  2. Click Software Update in the left pane.
  3. Click Install a Software Update in the main pane.
  4. Follow the steps in the wizard to locate and install your PAK file.
    This updates the OS on the virtual appliance and restarts each virtual machine.
  5. Read the End User License Agreement and Update Information, and click Next.
  6. Click Install to complete the installation of software update.
    Note: After you click Install, the installer will restart the vRealize Operations administrator interface, and you will be logged out. Log in once again to the vRealize Operations administrator interface when it is ready, and follow the update status in the software update page.
  7. Log back into the master node administrator interface.
    The main Cluster Status page appears and cluster goes online automatically. The status page also displays the Bring Online button, but do not click it.
  8. Clear the browser caches and if the browser page does not refresh automatically, refresh the page.
    The cluster status changes to Going Online. When the cluster status changes to Online, the upgrade is complete.
    Note: If a cluster fails and the status changes to offline during the installation process of a PAK file update, then some nodes become unavailable. To fix this, you can access the administrator interface and manually take the cluster offline and click Finish Installation to continue the installation process.
  9. Click Software Update to check that the update is done.
    A message indicating that the update completed successfully appears in the main pane.
    Note:

    When you update vRealize Operations to a latest version, all nodes get upgraded by default.

    If you are using cloud proxies, the cloud proxy upgrades start after the vRealize Operations upgrade is complete successfully. For more information, see the Monitoring the Health of Cloud Proxies from the Admin UI topic in the vRealize Operations Configuration Guide.

What to do next

Delete the snapshots you made before the software update.
Note: Multiple snapshots can degrade performance, so delete your pre-update snapshots after the software update completes.