Upgrading VM Recovery Manager HA

If you are upgrading the VM Recovery Manager HA solution from the previous version to the latest version, you must install the packages that have updates to the existing software in your environment.

Prerequisites:
  • You must have root authority to perform the installation tasks.
  • When you install the new filesets, ensure that the existing version of the KSYS software is not running any active operations. The installation of the newer version of the KSYS software fails if the discovery, verification, or move operation is running in the existing version of the KSYS software.
  • All KSYS-related operations such as discover, verification, move, and cleanup must be complete before you attempt to upgrade the existing version of the VM Recovery Manager HA solution to the latest version. Run the ksysmgr query system status monitor=yes command to check the status of KSYS-related operations.
  • Before you install or upgrade VM monitor fileset, ensure that you set the virtual machine in the KSYS subsystem to unmanage, and run the discovery operation. Then, install or upgrade the VMM fileset at the VMM. You can set the unmanaged virtual machine to managed depending on your requirement. You must run the discovery operation after you have set the unmanaged virtual machine to managed.
  • It is recommended to stop the IBM.VMR daemon by running the stopsrc -s IBM.VMR command before starting the upgrade operation. You must restart the IBM.VMR daemon by running the startsrc -s IBM.VMR command after the upgrade operation completes.
The following table provides information about upgrade possibility from a lower version to the higher version of the VM Recovery Manager HA solution.
Table 1. VMRM HA upgrade table
Current version of KSYS subsystem Upgrade version of KSYS subsystem
VM Recovery Manager HA 1.5.0.0
  • VM Recovery Manager HA 1.5.0.1
  • VM Recovery Manager HA 1.6.0.0
  • VM Recovery Manager HA 1.7.0.0
  • VM Recovery Manager HA 1.7.0.1
VM Recovery Manager HA 1.5.0.1
  • VM Recovery Manager HA 1.6.0.0
  • VM Recovery Manager HA 1.7.0.0
  • VM Recovery Manager HA 1.7.0.1
VM Recovery Manager HA 1.6.0.0
  • VM Recovery Manager HA 1.7.0.0
  • VM Recovery Manager HA 1.7.0.1
  • start of changeVM Recovery Manager HA 1.8.0.0end of change
  • start of changeVM Recovery Manager HA 1.8.0.1end of change
VM Recovery Manager HA 1.7.0.0
  • VM Recovery Manager HA 1.7.0.1
  • start of changeVM Recovery Manager HA 1.8.0.0end of change
  • start of changeVM Recovery Manager HA 1.8.0.1end of change
  • start of changeVM Recovery Manager HA 1.9.0.0end of change
  • start of changeVM Recovery Manager HA 1.9.0.1end of change
start of changeVM Recovery Manager HA 1.7.0.1end of change
  • VM Recovery Manager HA 1.8.0.0
  • start of changeVM Recovery Manager HA 1.8.0.1end of change
  • start of changeVM Recovery Manager HA 1.9.0.0end of change
  • start of changeVM Recovery Manager HA 1.9.0.1end of change
VM Recovery Manager HA 1.8.0.0
  • start of changeVM Recovery Manager HA 1.8.0.1end of change
  • start of changeVM Recovery Manager HA 1.9.0.0end of change
  • start of changeVM Recovery Manager HA 1.9.0.1end of change
  • start of changeVM Recovery Manager HA 1.10.0.0end of change
VM Recovery Manager HA 1.8.0.1
  • start of changeVM Recovery Manager HA 1.9.0.0end of change
  • start of changeVM Recovery Manager HA 1.9.0.1end of change
  • start of changeVM Recovery Manager HA 1.10.0.0end of change
VM Recovery Manager HA 1.9.0.0
  • start of changeVM Recovery Manager HA 1.9.0.1end of change
  • start of changeVM Recovery Manager HA 1.10.0.0end of change
VM Recovery Manager HA 1.9.0.1 VM Recovery Manager HA 1.10.0.0
Complete the following procedures to upgrade the VM Recovery Manager HA solution.
  1. Upgrading the KSYS software.
  2. Upgrading VIOS to Version 4.1.2.10
  3. Upgrading VM agents in the virtual machines.
Note: You must have root authority to perform any uninstallation tasks.

Upgrading the KSYS software

  1. Contact IBM sales team for information about download location of the VM Recovery Manager HA solution.
  2. Copy the filesets to the location where the existing filesets are installed.
  3. Decompress the filesets according to the guidelines that are provided with the package.
  4. To install the filesets by using SMIT panel, complete the following steps:
    1. To open the SMIT panel, enter the following command:
      smit install
    2. In the Install and Update Software screen, select Update Installed Software to Latest Level (Update All), and press Enter.
                                  Install and Update Software
                                                                                      
      Move cursor to desired item and press Enter.
                                                                                      
        Install Software
        Update Installed Software to Latest Level (Update All)
        Install Software Bundle
        Update Software by Fix (APAR)
        Install and Update from ALL Available Software
    3. In the Update Installed Software to Latest Level (Update All) screen, change the values according to your situation. You must also accept new license agreements. Press Enter after you make all other changes.
  5. Check the installation summary at the end of the installation output by scrolling to the end of the output. The output indicates whether the installation of your fileset was successful.

    If trace spooling is enabled and the trace file size is large, you must wait for a few minutes before you run the ksysmgr command. If the installation was not successful, check the reason of failure in the output.

  6. After upgrading of the KSYS software successfully, run the following script in the GUI server: /opt/IBM/ksys/ui/server/dist/server/bin/vmruiinst.ksh. Then, restart the GUI server by running the stopsrc -s vmruiserver and startsrc -s vmruiserver commands.

Upgrading VIOS to Version 4.1.2.10

Note: The following steps apply only to the migration process.
  1. Ensure that the VIOS version 3.1.4.21 above and the Postgres version 13 are installed on the VIOS. To check the Postgres version, run the following command:
    cat /var/vio/SSP/<cluster_name> /D_E_F_A_U_L_T_061310/VIOSCFG/DB/PG/PG_VERSION
    To check the mount point of the Postgres database, run the following command:
    mount
  2. Ensure that the SSP cluster and database are in a healthy state. To verify the state of the cluster, run the following command in the padmin command-line interface:
    cluster -status
    The padmin command-line interface must display OK state for all the VIOS that are part of the SSP cluster.
  3. Upgrade a VIOS, for example VIOS1, to version 4.1.1.0 then check the status of upgrade progress. To check the progress of the upgrade process, run the following command:
    viosupgrade -q -l
    An output that is similar to the following message must display: VIOS upgrade completed successfully.
    Note: After upgrading the VIOS to version 4.1.2.10, verify the status of the ksys_hsmon daemon in VIOS. If the daemon is inoperative, a reboot of the respective VIOS is required.
    To verify daemon status, run the following command:
    lssrc -s ksys_hsmon
  4. Wait for two minutes to get the cluster in the stable state. To check the state of the cluster, run the following command:
    cluster -status
    The output must display OK state for the upgraded VIOS.
  5. Please verify the VIOS release notes and apply if any mandatory efix required.
  6. Restart the VIOS after you have applied the efix.
  7. After the VIOS1 is up and running, you must wait for two minutes to get the cluster in the stable state. You can observe that the Postgres version of the VIOS is still version 13.
  8. Run the discovery operation on the KSYS controller node. Ensure that the discovery operation completes successfully.
  9. Similarly, upgrade all other VIOSes by repeating Step-4 to Step-7 for each VIOS. After all the VIOSes are upgraded, the Postgres version will be update to 15. To check the Postgres version, run the following command:
    cat /var/vio/SSP/<cluster_name> /D_E_F_A_U_L_T_061310/VIOSCFG/DB/PG/PG_VERSION
Note: During the migration of VIOS partitions from versions 3.1.4.60, 4.1.0.40 and 4.1.1.20 to version 4.1.2.10, it is observed that the ksys_hsmon daemon intermittently fails to start. In certain cases, the daemon shows an inoperative status, which impacts VM Recovery Manager HA operations. As a temporary workaround, a reboot of the affected VIOS brings the ksys_hsmon daemon back to an active state, allowing VM recovery manager HA operations to proceed normally

Upgrading VM agents

To upgrade the VM agent on Linux® Virtual machine follow the below steps :
  • In Red Hat Enterprise Linux (RHEL) (little endian) virtual machines.
    To verify existing vmagent version, run the following commands:
    rpm -q vmagent
    vmagent-1.10.0.1-1.0.el7.ppc64le
    Upgrade vmagent from existing (1.9 SP1) to latest(1.10):
    rpm -Uvh vmagent-1.10.0.0-1.0.el7.ppc64le.rpm
    Verifying...                                                 ################################# [100%]
    Preparing...                                                 ################################# [100%]
    ksys_vmmd service is running. Stopping ksys_vmm daemon.
    ksys_vmm has been requested to stop.Warning: pax rpm is not installed. 
    Please install pax rpm to collect snap data.
    Updating / installing... 
             1:vmagent-1.10.0.0-1.0.el7     ################################# [ 50%]
    Starting ksys_vmm daemon.ksys_vmm has been started.
    DEBUG: Detected version in %preun (upgrade): 1.9.0.1
    Backed up: /var/ksys/config/samples/SAPHANAconfig.xml -> /var/ksys/config/samples/SAPHANAconfig.xml_1.9.0.1_Backup
    Backed up: /var/ksys/config/samples/POSTGRESconfig.xml -> /var/ksys/config/samples/POSTGRESconfig.xml_1.9.0.1_Backup
    Backed up: /var/ksys/config/samples/S4HANAconfig.xml -> /var/ksys/config/samples/S4HANAconfig.xml_1.9.0.1_Backup
    NOTICE: Configuration Backup Created
    - Backup files have '_1.9.0.1_Backup' suffix.
    - New defaults may appear as '.rpmnew'.
    - Please merge changes as needed.
    Cleaning up / removing... 2:vmagent-1.9.0.1-1.0.el7 ################################# [100%]
    Verify the version after upgrading vmagent:
    rpm -q vmagent
    vmagent-1.10.0.0-1.0.el7.ppc64le
  • In SUSE Linux Enterprise Server (SLES) (little endian) virtual machines.
    To verify existing vmagent version, run the following commands:
    rpm -q vmagent
    vmagent-1.10.0.0-1.0.suse123.ppc64le.rpm
    Upgrade vmagent from existing (1.9 SP1) to latest(1.10):
    rpm -Uvh vmagent-1.10.0.0-1.0.suse123.ppc64le.rpm
    Preparing...                                                      ################################# [100%]
    ksys_vmmd service is running. Stopping ksys_vmm daemon.
    ksys_vmm has been requested to stop.
    Updating / installing... 1:vmagent-1.10.0.0-1.0.suse123           ################################# [ 50%]
    Starting ksys_vmm daemon.
    ksys_vmm has been started.
    DEBUG: Detected version in %preun (upgrade): 1.9.0.1
    Backed up: /var/ksys/config/samples/SAPHANAconfig.xml -> /var/ksys/config/samples/SAPHANAconfig.xml_1.9.0.1_BackupBacked up: /var/ksys/config/samples/POSTGRESconfig.xml -> /var/ksys/config/samples/POSTGRESconfig.xml_1.9.0.1_BackupBacked up: /var/ksys/config/samples/S4HANAconfig.xml -> /var/ksys/config/samples/S4HANAconfig.xml_1.9.0.1_Backup
    NOTICE: Configuration Backup Created
    - Backup files have '_1.9.0.1_Backup' suffix.
    - New defaults may appear as '.rpmnew'.
    - Please merge changes as needed.Cleaning up / removing... 
    2:vmagent-1.9.0.1-1.0.suse123 ################################# [100%]
    Verify the version after upgrading vmagent:
    rpm -q vmagent
    vmagent-1.10.0.0-1.0.suse123.ppc64le

Upgrading AIX VM agents

These commands upgrades the VM agent software without modifying the current configured file and newly installed config file renames as <configfile>.xml.rpmnew

To overwrite VM agent on AIX virtual machine follow the below steps:

  1. Download the required filesets.
  2. Before overwriting the VM agent, take a backup of your application configuration file from the /var/ksys/config/samples directory.
  3. Install the filesets by using the installp command or smitty installp
    installp -aFXYd. <ksys.vmmon.rte>
    .
  4. After installation, scroll to the end of the output and check the installation summary to confirm that the fileset installation was successful.
  5. If any application was previously configured, restore the backed-up application configuration file to the /var/ksys/config/samples directory.

Upgrading AIX VM agents from version 1.10

Starting with version 1.10, VM Recovery Manager HA preserves user-modified configuration files during fileset upgrades. Before the upgrade begins, the system creates backup copies of existing configuration files and stores them in the following directory:
/var/ksys/config/backup
Note: When you upgrade from a release earlier than version 1.10 to version 1.10, the system does not create configuration backups because the earlier release does not contain the backup mechanism. After version 1.10 is installed, all subsequent upgrades automatically create configuration backups.
To verify that configuration files are preserved during a fileset upgrade, complete the following steps:
  1. Verify the currently installed version:
    lslpp -l ksys.vmmon.rte
  2. Upgrade the fileset:
    installp -acXYd fileset_location ksys.vmmon.rte
    Example:
    installp -acXYd . ksys.vmmon.rte
  3. Verify that the upgrade completed successfully:
    lslpp -l ksys.vmmon.rte
  4. Verify that backup files are available:
    ls -l /var/ksys/config/backup

The backup directory contains copies of configuration files that existed before the upgrade.

If you uninstall the fileset, the system removes the active configuration files but retains the backup files in the /var/ksys/config/backup directory.

Upgrading KSYS filesets for KSYS high availability supported with PowerHA SystemMirror
To upgrade the KSYS software in a KSYS LPAR on which PowerHA SystemMirror is configured, complete the following steps:
  1. Stop PowerHA SystemMirror cluster service on all KSYS nodes by using the smit clstop command.
  2. Upgrade the KSYS fileset on all KSYS nodes.
  3. Start the PowerHA SystemMirror cluster services by using the smit clstart command.