Upgrading LifeKeeper

!The version of Perl shipped with LifeKeeper for Linux v9.8.0 has been upgraded from 5.8.8 to 5.32.1. If you are using a Perl-based Generic ARK, please review the impact of this Perl upgrade before upgrading from LifeKeeper for Linux prior to v9.7.0 to LifeKeeper for Linux v9.8.0 or later. See Perl 5.8.8 to Perl 5.32.1 Upgrade for more information.

*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 LifeKeeper 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 LifeKeeper for Linux v9.5.0 must convert their existing SAP HANA gen/app based Recovery Kit to the new SAP HANA Recovery Kit.

LifeKeeper 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 LifeKeeper 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 LifeKeeper in 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. Refer to the Setting Server Shutdown Strategy for more information.

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

3. Switch all applications back to the upgraded server.

4. Repeat this procedure for each server in the LifeKeeper cluster to be upgraded. For clusters containing a dedicated Witness/Quorum node (a node with no resource instances) no switching of applications is required prior to upgrading LifeKeeper.

!CAUTION: The same version and release of LifeKeeper must be installed on all systems in a cluster. In general, different versions and/or releases of LifeKeeper 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.

Upgrading LifeKeeper (MaxDB)

These steps will allow an upgrade when binaries are replicated.

1. Take resource hierarchy (MaxDB) out of service in SIOS LifeKeeper (SPS-L) on Source.
2. Pause the mirrors in the hierarchy because the binaries are being replicated.
3. Start application (MaxDB) on target.
4. Perform the application (MaxDB) update on the target.
5. Verify the upgrade was successful on the target.
6. Stop the application (MaxDB) on the target.
7. Start the application (MaxDB) on the Source.
8. Be sure to leave the MaxDB resource as OSU in LK.
9. Perform the application (MaxDB) update on the source.
10. Stop the application (MaxDB) on the source.
11. Verify the upgrade was successful on the source.
12. Bring the application (MaxDB) resource in-service through the LK GUI.
13. Resume the mirrors.
14. Allow the mirrors to resync completely.
15. Perform a switchover and switchback of the resource hierarchy.
16. Verify MaxDB restores on the target via LK and the application version has successfully upgraded.