Upgrading SPS

*Beginning in v9.5.0 SIOS has released the new SAP HANA Application Recovery Kit. SIOS will continue to support the SAP HANA gen/app based Recovery Kit with the 9.4.x releases until March 31, 2022.
• The existing SAP HANA gen/app based Recovery Kit is not supported with v9.5.0.
• If you are using SIOS Protection Suite for Linux v9.5 or later you must use the new (built-in) SAP HANA Application Recovery Kit.
• Users who wish to upgrade to the SIOS Protection Suite for Linux v9.5.0 must convert their existing SAP HANA gen/app based Recovery Kit to the new SAP HANA Recovery Kit. Refer to Upgrading from the SAP HANA Gen/App to the SAP HANA Recovery Kit for details.

SPS for Linux may be upgraded to future releases while preserving existing resource hierarchies. Review this information carefully to ensure that you minimize application downtime.

*Note: LifeKeeper can be upgraded to the current version from up to two versions back.
(An example of a two version upgrade is from 9.1.x -> 9.3.x) If upgrading from a version previous to that, the older version will need to be uninstalled, and SIOS Protection Suite for Linux will have to be reinstalled. An alternative to uninstalling the older version would be to upgrade from the older version to one of the two acceptable versions, then perform the upgrade to the current version.

*Note: If using lkbackup during your upgrade, refer to the known issues of lkbackup for further information.

1. While upgrading a cluster, switch all applications away from the server to be upgraded now. Do this manually or by setting the LifeKeeper shutdown strategy to “Switchover” which causes the applications to be switched when LifeKeeper is stopped or the server is shut down.

2. If necessary, upgrade the Linux operating system before upgrading SPS. It is recommended that you unextend all resources from a server that is to be upgraded prior to performing the operating system upgrade.

3. Upgrade LifeKeeper by referring to How to Use Setup Scripts.

4. Switch all applications back to the upgraded server.

5. Repeat this procedure for each server in the SPS cluster to be upgraded.

!CAUTION: The same version and release of SPS must be installed on all systems in a cluster. In general, different versions and/or releases of SPS are not compatible. For situations other than rolling upgrades, LifeKeeper should not be started when a different version or release is resident and running on another system in the cluster.

NOTES:

When upgrading the OS, make sure the currently installed version of LifeKeeper supports the upgraded version of the OS. If it is not supported, LifeKeeper will need to be upgraded as well provided a version of LifeKeeper has been released that supports the new OS version. If no version of LifeKeeper has been released that supports the new OS version you may not be able to upgrade the OS. Refer to the Supported Operating Systems.

Before upgrading the OS, it is recommended that the LifeKeeper configuration be backed up via the lkbackup command.

*Note: When using lkbackup, refer to the known issues of lkbackup.

1. When upgrading the cluster, all the resource hierarchies and thus the applications they protect, must be switched from the server to be upgraded to a standby node in the cluster. This can be done manually, or, by setting the LifeKeeper Shutdown Strategy to “Switchover”. By setting the Shutdown Strategy to “Switchover”, the resource hierarchies are switched over to a standby node when LifeKeeper stops or the servers are shutdown.

2. Stop LifeKeeper.

3. Upgrade and reboot the OS.

4. Upgrade LifeKeeper when required. If you do not upgrade, run setup again and update the settings corresponding to the new OS.

5. Start up LifeKeeper.

6. Switch all the resource hierarchies to the upgraded server.

7. Execute these steps for all the nodes in the SPS cluster.

*Note: All nodes in the cluster must be running the same version of the OS and the same version of LifeKeeper to be considered supported. Only during the upgrade process can the nodes differ in the OS and LIfeKeeper versions as this would be considered a temporary condition.