Upgrading VM Recovery Manager DR

Edit online

If you have an earlier version of the KSYS software, you can upgrade the VM Recovery Manager DR solution to the current version by installing the latest KSYS filesets. The latest filesets will overwrite the existing software on the KSYS logical partition.

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 operations must be complete before you attempt to upgrade to the current version. Run the ksysmgr query system status monitor=yes command to check the status of KSYS-related operations.
If you attempted a move operation in the earlier VM Recovery Manager DR version and the move operation failed, the virtual machines might be in Recovery state. In this case, you must recover the virtual machines successfully or move the virtual machines to a proper state before upgrading to the current version.
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 VM Recovery Manager DR solution by running the stopsrc -s IBM.VMR command before initiating upgrade. You must restart the VM Recovery Manager DR solution by running the startsrc -s IBM.VMR command after the upgrade has finished.

When you upgrade the existing VM Recovery Manager DR version to the current version, the KSYS configuration settings (for example, details about HMCs, hosts, host pairs, storage agents, and so on) are retained without any change. After the upgrade operation is complete, you must run a discovery operation before you add, delete, or modify any configuration settings in the KSYS subsystem.

Note: After you upgrade to the latest version of filesets in the migration path, you cannot roll back to the previous version of the VM Recovery Manager DR.

The following table provides information about upgrade possibility from a lower version to the higher version of the VM Recovery Manager DR solution.

Table 1. VMRM DR upgrade table
Current version of KSYS subsystem	Upgrade version of KSYS subsystem
VM Recovery Manager DR 1.5.0.0	VM Recovery Manager DR 1.5.0.1 VM Recovery Manager DR 1.6.0.0 VM Recovery Manager DR 1.7.0.0 VM Recovery Manager DR 1.7.0.1
VM Recovery Manager DR 1.5.0.1	VM Recovery Manager DR 1.6.0.0 VM Recovery Manager DR 1.7.0.0 VM Recovery Manager DR 1.7.0.1
VM Recovery Manager DR 1.6.0.0	VM Recovery Manager DR 1.7.0.0 VM Recovery Manager DR 1.7.0.1 VM Recovery Manager DR 1.8.0.0 VM Recovery Manager DR 1.8.0.1
VM Recovery Manager DR 1.7.0.0	VM Recovery Manager DR 1.7.0.1 VM Recovery Manager DR 1.8.0.0 VM Recovery Manager DR 1.8.0.1 VM Recovery Manager DR 1.9.0.0 VM Recovery Manager DR 1.9.0.1
VM Recovery Manager DR 1.7.0.1	VM Recovery Manager DR 1.8.0.0 VM Recovery Manager DR 1.8.0.1 VM Recovery Manager DR 1.9.0.0 VM Recovery Manager DR 1.9.0.1
VM Recovery Manager DR 1.8.0.0	VM Recovery Manager DR 1.8.0.1 VM Recovery Manager DR 1.9.0.0 VM Recovery Manager DR 1.9.0.1 VM Recovery Manager DR1.10.0
VM Recovery Manager DR 1.8.0.1	VM Recovery Manager DR 1.9.0.0 VM Recovery Manager DR 1.9.0.1 VM Recovery Manager DR1.10.0
VM Recovery Manager DR 1.9.0.0	VM Recovery Manager DR 1.9.0.1 VM Recovery Manager DR 1.10.0
VM Recovery Manager DR 1.9.0.1	VM Recovery Manager DR 1.10.0

To upgrade the KSYS software in the existing KSYS LPAR, complete the following steps:

Contact IBM sales team for information about download location of the VM Recovery Manager DR solution.
Copy the filesets to the location where the existing filesets are installed.
Decompress the filesets according to the guidelines that are provided with the package.

To install the filesets by using SMIT panel, complete the following steps:

To open the SMIT panel, enter the following command:
```
smit install
```

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

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.

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. Contact IBM support, if necessary.
After upgrading 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. For more information about upgrading and setting up the GUI, see Installing GUI filesets.

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:

Stop PowerHA SystemMirror cluster service on all KSYS nodes by using the smit clstop command.
Upgrade the KSYS fileset on all KSYS nodes.
Start the PowerHA SystemMirror cluster services by using the smit clstart command.

Upgrading VIOS to Version 4.1.2.10

Note: The following steps apply only to the migration process in the HADRHA cluster type.

Ensure that the VIOS version 3.1.4.21 above and the Postgres version 13 are installed on your KSYS subsystem. 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
```
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.
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
```
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.
Please verify the VIOS release notes and apply if any mandatory efix required.
Restart the VIOS after you have applied the efix.
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.
Run the discovery operation on the KSYS controller node. Ensure that the discovery operation completes successfully.
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
```

Setting up the VM Recovery Manager DR GUI

To use the VM Recovery Manager DR by using the graphical interface, you must install the GUI server fileset on a system to manage KSYS nodes by using the GUI. For more information about installing the GUI fileset and setting up the GUI, see Installing GUI filesets.