The VMware vRealize Operations Software Update feature in the administration interface automatically copies the update PAK file to all cluster nodes. In some cases, you might want to reduce update time by manually pre-copying the PAK file to all nodes except the Master node before finishing the update using the administration interface.

Please note that per vRealize Operations Manager Best Practices (56491), the supported latency between analytic (primary, replica, data) nodes is sub 5ms, and between analytic nodes and Remote Collectors is sub 200ms.

VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations 8.x
VMware vRealize Operations Manager 6.x
VMware vRealize Operations Manager 7.5.x

To reduce update time by pre-copying software update PAK files, follow steps in:

• Part 1: on all nodes except the Primary node and
• Part 2: on the primary 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.

Part 1: On Nodes except the Primary node

1. Determine the destination directory for your version.
   
   (6.1-8.x) $STORAGE/db/casa/pak/dist_pak_files/{platform}
   
   where {platform} is VA_LINUX, NON_VA_LINUX, or NON_VA_WINDOWS depending on deployment type
   
   For example, on a vRealize Operations 8.x vApp deployment, the destination directory is:
   
   /data/db/casa/pak/dist_pak_files/VA_LINUX
    
2. Using a utility such as WinSCP or Filezilla, copy the PAK file to the destination directory of the vRealize Operations appliance
    
3. Note the ID of the PAK file by entering the following command.
   
   $VMWARE_PYTHON_BIN {path}/vcopsPakManager.py --action=query_pak_id --pak={pak-filename}
    
4. Determine the ID of the PAK file by noting the value to the right of "pak_id" as shown in the following examples.
   
   ∘ On a 6.0.x vApp deployment, the command and output resemble the following:
   
   $VMWARE_PYTHON_BIN $ALIVE_BASE/../vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action=query_pak_id --pak=vRealize_Operations_Manager-VA-6.1.0.2733055.pak
   {
   "pak_id": "vRealizeOperationsManagerEnterprise-6102733055"
   }
   
   ∘ On a 6.1 vApp deployment, the command and output resemble the following:
   
   $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/pakManager/bin/vcopsPakManager.py --action=query_pak_id --pak=vRealize_Operations_Manager-VA-6.1.0.5445359.pak
   {
   "invalid_reason": null,
   "is_signature_valid": true,
   "is_signature_valid_certificate_untrusted": null,
   "is_signed": true,
   "pak_id": "vRealizeOperationsManagerEnterprise-6105445359",
   "pak_version": "6.1.0.5445359",
   "platform": [
   "Linux VA"
   ],
   "vcopssuiteinstall_build_number": "5441604",
   "vcopssuiteinstall_build_type": "sb",
   "vcopssuitevm_build_number": "5441602",
   "vcopssuitevm_build_type": "sb"
   }
    
5. If needed - rename the PAK file so that the PAK ID becomes the base filename.
   
   For example:
   
   mv vRealize_Operations_Manager-VA-6.1.0.2733055.pak vRealizeOperationsManagerEnterprise-6102733055.pak
    
6. (Optional) Enter the following command to verify that the PAK file was correctly copied to the node and renamed:
   
   sha1sum {new-filename}.pak
   
   For example:
   
   $ sha1sum vRealizeOperationsManagerEnterprise-6102733055.pak
   610df3113d9f02e1931e34bed95f952b23b710b4 *vRealizeOperationsManagerEnterprise-6102733055.pak

Part 2: On the Primary Node

1. In the administration interface, click Software Update, click Install a Software Update, and follow the wizard to locate and upload the PAK file.
   
   Important: Do not select the option to force PAK upload and installation. The option will remove the PAK from nodes where it was manually copied.
    
2. Wait until the upload finishes.
    
3. (Optional) Use your REST client to verify that the PAK file is present on all nodes. The REST client will also need to pass the administrator username of admin and the admin password.
    
   1. Enter the following HTTP call to the master node.
      
      GET /casa/upgrade/cluster/pak/reserved/list
       
   2. Follow the href link to identify the PAK ID.
       
   3. Enter the following HTTP call to the master node.
      
      GET /casa/upgrade/cluster/pak/{PAK ID}/status
       
   4. Verify that the pak_state is DISTRIBUTED for nodes that have the manual copy.
      
      ∘ For example, first note the PAK ID of vRealizeOperationsManagerEnterprise-6102733055:
      
      https://pvd84/casa/upgrade/cluster/pak/reserved/list
      [
      {
      "links": [
      {
      "rel": "pak_cluster_status",
      "href": "https://pvd84:443/casa/upgrade/cluster/pak/vRealizeOperationsManagerEnterprise-6102733055/status"
      },
      {
      "rel": "pak_file_information",
      "href": "https://pvd84:443/casa/upgrade/slice/pak/vRealizeOperationsManagerEnterprise-6102733055/file_information"
      },
      {
      "rel": "pak_information",
      "href": "https://pvd84:443/casa/upgrade/cluster/pak/vRealizeOperationsManagerEnterprise-6102733055/information"
      }
      ],
      "pak_file": "vRealizeOperationsManagerEnterprise-6102733055.pak",
      "pak_id": "vRealizeOperationsManagerEnterprise-6102733055"
      },
      {
      "links": [
      {
      "rel": "pak_cluster_status",
      "href": "https://pvd84:443/casa/upgrade/cluster/pak/VMwarevSphere-602263102/status"
      },
      {
      "rel": "pak_file_information",
      "href": "https://pvd84:443/casa/upgrade/slice/pak/VMwarevSphere-602263102/file_information"
      },
      {
      "rel": "pak_information",
      "href": "https://pvd84:443/casa/upgrade/cluster/pak/VMwarevSphere-602263102/information"
      }
      ],
      "pak_file": "VMwarevSphere-602263102.pak",
      "pak_id": "VMwarevSphere-602263102"
      }
      ]
      
      ∘ Next, note that nodes 8.125.37.85 and 8.125.37.86, which have the manual copy, show a pak_state of DISTRIBUTED:
      
      https://pvd84:443/casa/upgrade/cluster/pak/vRealizeOperationsManagerEnterprise-6102733055/status
      {
      "cluster_pak_install_status": "CANDIDATE",
      "slices": [
      {
      "slice_address": "8.125.37.85",
      "http_code": 200,
      "document": {
      "pak_id": "vRealizeOperationsManagerEnterprise-6102733055",
      "pak_state": "DISTRIBUTED",
      "pak_install_status": "CANDIDATE",
      "node_unchanged": true,
      "failed_details": null,
      "log_links": []
      },
      "content_type": "application/json"
      },
      {
      "slice_address": "8.125.37.84",
      "http_code": 200,
      "document": {
      "pak_id": "vRealizeOperationsManagerEnterprise-6102733055",
      "pak_state": "STAGED",
      "pak_install_status": "CANDIDATE",
      "node_unchanged": true,
      "failed_details": null,
      "log_links": []
      },
      "content_type": "application/json"
      },
      {
      "slice_address": "8.125.37.86",
      "http_code": 200,
      "document": {
      "pak_id": "vRealizeOperationsManagerEnterprise-6102733055",
      "pak_state": "DISTRIBUTED",
      "pak_install_status": "CANDIDATE",
      "node_unchanged": true,
      "failed_details": null,
      "log_links": []
      },
      "content_type": "application/json"
      }
      ],
      "cluster_data": {
      "cluster_action_failed": false,
      "cluster_action_failed_time": null,
      "cluster_action": "NO_ACTION"
      }
      }
       
4. Continue the software update the way that you normally would, by clicking Next, accepting the EULA, clicking Next, and so on.