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 (v9.8.0). If upgrading from a previous version 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 acceptable versions, and then perform the upgrade to the current version. For example, to upgrade from v9.5.0 to v9.9.0, first upgrade to v9.7.0 and then proceed to v9.9.0.
*Note: If using lkbackup during your upgrade, refer to the known issues of lkbackup for further information.
- While upgrading LifeKeeper in a cluster, switch all applications away from the server to be upgraded now.
- Upgrade LifeKeeper by referring to How to Use Setup Scripts.
- Switch all applications back to the upgraded server.
- 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.
Post your comment on this topic.