Skip to main content

vROPS | Step by Step Upgrade Process

Hi Guys,

However, on Internet it is already well documented but I am getting few requests to share the process which I followed to upgrade :) So, for those guys, who requested it. However, who haven't requested it still can take benefit out of it, if they want. LOL!

Here you go...
Pre-Checks

• Take a snapshot of the vROPS virtual appliance ( all cluster nodes including Master, Replica, Data and collector nodes)
• Make sure that you have different upgrade files for Operating system and Virtual appliance (vROPS), there is NO roll back when an upgrade fails. Need snapshot to revert it back.
• Enough free space available on the vROPS Master virtual machine.( df -h $STORAGE/db) , around 20-25% free space

Pre-Upgrade Steps-
In order to reduce the upgrade time, we need to copy the .pak files manually to all nodes except Master node.
Note: If you do not pre-copy the PAK file to a node, the Software Update feature copies the PAK file to the node as usual when you finish the update using the administration interface

Below is the method to manually copy the .PAK files to nodes.

Step 1 -


Download the .PAK files to jump server (C:\Temp) from where VROPS server is accessible

Step 2 –

With the help of WINSCP copy downloaded PAK files to below VROPS’s server location

$STORAGE/db/casa/pak/dist_pak_files/VA_Linux (because it is a virtual appliance)

Step 3 –

Expose the ID of the PAK file by entering the following command

$VMWARE_PYTHON_BIN {path}/vcopsPakManager.py --action=query_pak_id --pak={pak-filename}

For example –



## /usr/lib/vmware-vcopssuite/utilities/pakManager/bin/vcopsPak Manager.py is location of Python script.

It will give the “PAK_ID” as shown above

Step 4 –

Rename the PAK file so the PAK ID become the base filename

For example -

mv vRealize_Operations_Manager-VA-6.1.0.2733055.pak vRealizeOperationsManagerEnterprise-6102733055.pak

Step 5 -

Enter the following command to verify that the PAK file was correctly copied to the node and renamed:

For example -

sha1sum vRealizeOperationsManagerEnterprise-6616163041.pak

Refer to below image

Now, Once all the files are copied, take the snapshot. You can follow my this post or let me know if you want this engine.

Please be cautious while taking the snapshot for below two points
- Uncheck Snapshot the Virtual Machine Memory
- Uncheck the Ensure Quiesce Guest File System (Needs VMware Tools installed)
Below is the reference VMware’s KB
https://docs.vmware.com/en/vRealize-Operations-Manager/6.5/com.vmware.vcom.core.doc/GUID-42502543-2451-4317-BA42-F7D12172C23B.html

Pre-staging of PAK file is done here. Now let's proceed for the actual upgrade.

We will do this upgrade in two phases. So...


Phase 1 – VRealize Operation Manager OS Upgrade

Login to vRealize Operations Manager Admin Console using https://<masternode -IP-address or FQDN name>/admin. You will see below console.



Once Snapshots for all nodes including master nodes are done then click on “Take offline” button as shown above in snippet.



It will bring cluster offline and vROPS user interface will be inaccessible from now. You will see below status of the cluster.



Now click on Software Update under Administration panel and then click on “Install a Software Update”



Browse and select the OS Upgrade PAK file (vRealize_Operations_Manager-VA-OS-6.6.1.6163041.pak) which you downloaded to C:\Temp location then click on Upload