In this post i will go over upgrading my 8.x vROPS appliance to 8.6 using vRSLCM (vRealize Suite Lifecycle Manager). As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.6. Instructions can be found here. The upgrade already includes the latest Product Support Pack so an update to the Product Support Pack is not required.

To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware)

The image shows the “Settings” page with options for system administration and servers/accounts.

Click on Add Binaries under Product Binaries

Binary Mapping page in vRealize Suite Lifecycle Manager for adding product binaries.

Select My VMware and click on Discover

Add Product Binary wizard step, select “My VMware” and click “Discover”.

We can see a list of binaries that have been discovered. Make sure we select the upgrade package not the install package. We can select what we need and click on Add

Select vRealize Operations 8.6.0 upgrade, then click Add.

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Binary mapping request submitted; check status via hyperlink.

Click on the in Progress button to view the details

Upgrading to vROPS 8.5.0 via vRSLCM in progress.

We now have to wait for the download to complete

Request for vROPS upgrade is in Stage 1, downloading VMware files.

After the download is complete we can go to Environments -> View Details on the environment that includes vROPS

The image shows a vRSLCM interface with an “Environments” section, displaying “Corp Local” and its products and health status.

Click on Upgrade

The vRealize Operations Manager interface shows upgrade options, with a note about inventory sync and upgrade buttons visible.

An Inventory sync is recommended if the environment has changed since LCM performed the last sync. We trigger the sync from the UI or click on Proceed to continue

Upgrade wizard step with sync recommendation and proceed buttons.

Select product Version 8.6.0 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

Upgrade vRealize Operations wizard showing version selection with 8.6.0 and repository URL.

Run the Upgrade Assessment tool to make sure the currently used dashboards, reports, metrics etc are still compatible with the new version

Upgrade vRealize Operations wizard shows “APUAT” step, with a button to run assessment for compatibility.

Once the report has finished running we can either Download or view the report. Once everything has been reviewing we can click on the I have viewed the report and agree to proceed box and click next to proceed to the next step.

The image shows a step in upgrading vRealize Operations Manager via vRSLCM, where a report assessment is completed.

A new feature that was added was the capability to automatically create a snapshot prior to the upgrade and remove it after the upgrade. On this screen we also have the ability to chose if we want to keep the snapshots post upgrade for validation testing for example. Click next

Upgrading vROPS via vRSLCM wizard step: Snapshot. Select ‘Take product snapshot’ and ‘Retain snapshot’ for validation.

Run the Precheck to make sure there are no errors or issues.

Precheck screen for vRSLCM upgrade, click RUN PRECHECK to validate data.

Once the check is complete we can review the checks that were performed and we can continue by clicking Next.

Precheck results show all validations passed for vRealize Operations Manager upgrade.

Review the upgrade details and click on Next. We are taken to the progress screen where we can follow the progress.

Upgrading vROPS via vRSLCM: Progress screen showing stages and status.

The system will get rebooted and once its back up we will be on 8.6

Since we are doing a major upgrade i strongly recommend to clean the cache before using the new vROPS version.