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. 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, see the lkbackup Known Issue for further information.
- 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.
- 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.
- 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 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.
Post your comment on this topic.