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.
- 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.
- 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.
Upgrading LifeKeeper (MaxDB)
These steps will allow an upgrade when binaries are replicated.
- Take resource hierarchy (MaxDB) out of service in SIOS LifeKeeper (SPS-L) on Source.
- Pause the mirrors in the hierarchy because the binaries are being replicated.
- Start application (MaxDB) on target.
- Perform the application (MaxDB) update on the target.
- Verify the upgrade was successful on the target.
- Stop the application (MaxDB) on the target.
- Start the application (MaxDB) on the Source.
- Be sure to leave the MaxDB resource as OSU in LK.
- Perform the application (MaxDB) update on the source.
- Stop the application (MaxDB) on the source.
- Verify the upgrade was successful on the source.
- Bring the application (MaxDB) resource in-service through the LK GUI.
- Resume the mirrors.
- Allow the mirrors to resync completely.
- Perform a switchover and switchback of the resource hierarchy.
- Verify MaxDB restores on the target via LK and the application version has successfully upgraded.