VMware vROPS 6.4 – Upgrade Process From 6.3

Most people know by now that the VMware vRealize Operations Management version 6.4 was released by VMware on the 15th of November 2016, amongst a number of other new products.

Since then, I’ve been meaning to upgrade my vROPS appliance from the previous 6.3 version to 6.4 and finally tonight managed to get around to doing it. I’ve documented below (briefly though) the easiest migrations steps to follow.

  1. Backup any customised contents (such as custom views, definitions…etc.)
    1. This is required so that that during the vROps product update you can select “Reset default content, overwriting to a newer version provided by this update” option.
  2. Login to the vRops appliance’s admin page
    1. https://<fqdn of the vROps appliance>/admin
  3. Offline the vROps cluster
    1. Click on the “Take offline” button to offline the vROps cluster                                   
    2. Note that obviously this means downtime and this may take some time to complete
    3. You need to repeat if for each node in the cluster if you have a HA cluster of vROps nodes
    4. Verify its offline properly                                                                                      
  4. Take a snapshot backup
    1. Once offline, go to vSphere web client and take a snapshot of the vROps 6.3 appliance VM’s (precautionary best practise)
  5. Download the appropriate update files from My VMware for vROps 6.4 – I have the vROps appliance deployed rather than a Windows install and you need 2 update files here as follows
    1. Virtual Appliance OS system update PAK file: You need the file titled “vRealize_Operations_Manager-VA-OS-6.4.0.4635873.pak”
    2. vROps product update PAK file: I’m using “vRealize_Operations_Manager-VA-6.4.0.4635873.pak” file as I don’t have windows remote collectors configured (if you do, make sure you download the “vRealize_Operations_Manager-VA-WIN-6.4.0.4635873.pak ” file instead)
  6. Appliance OS update
    1. Go to Software Update and click on Install a software update and locate the .Pak file for the OS update (“vRealize_Operations_Manager-VA-OS-6.4.0.4635873.pak“)
    2. Click Upload. Once complete, read the warning messages (about the appliance restart) and click next
    3. Accept EULA and click next twice & finally click install. The vROps virtual appliance OS upgrade install with begin.  
    4. Once the OS install is complete, the appliance will restart and would prompt you to login back to the admin page.
    5. Login back to the Admin page and wait for the vRops services to become online.
    6. Go to the Software Update section and ensure that the OS update is successfully complete.          
  7. vROps product update
    1. Go to Software Update and click on Install a software update and locate the .Pak file for the OS update (“vRealize_Operations_Manager-VA-6.4.0.4635873.pak“)  
    2. Click Reset default content checkbox and click upload
    3. Once uploaded and staged on the appliance, ensure that the new version (to be upgraded to) is appearing correctly and click next
    4. Accept EULA and click next twice and then click install                                                                          
    5. During the install stage, you will be automatically logged out of the admin interface and will be prompted to log back in.
    6. Log back in to the admin interface and wait until the software update completes. This stage can be time consuming somewhat
    7. Once complete, go to System Status section and verify that the vROps version 6.4 is not showing successfully.  
  8. That’s it. vROps upgrade has successfully completed now for my cluster / node. If you have multiple nodes in your vROps cluster, you may need to repeat this process for each node.
  9. Also do remember to remove the snapshot if all operations are normal, after a while and that you can see all your views, dashboards…etc.

 

Cheers

Chan

 

 

Chan

Lead Solutions Architect & Hybrid Cloud Practice Lead

Leave a Reply

Your email address will not be published. Required fields are marked *