Open topic with navigation
LifeKeeper for Linux may be upgraded to future releases while preserving existing resource hierarchies. Review this information carefully to ensure that you use the best upgrade procedure for your environment and minimize application downtime. Beta Customers should use the latest upgrade instructions included in the LifeKeeper Release Notes to upgrade from Beta Software to final versions of LifeKeeper for Linux.
If you are upgrading a LifeKeeper cluster with only two nodes, proceed directly to Step 2. If you are upgrading a LifeKeeper cluster with greater than two nodes, 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 LifeKeeper. It is recommended that you unextend all resources from a server that is to be upgraded prior to performing the operating system upgrade.
Upgrade your LifeKeeper distribution enabling packages using the LifeKeeper Installation Support CD. To upgrade the LifeKeeper distribution enabling packages, insert the LifeKeeper Installation Support CD, change to the CD-ROM directory and execute sh setup. If your server is not set up to automatically mount the CD-ROM drive, you will need to mount it explicitly, using the mount command, before running the setup script.
To upgrade LifeKeeper, insert the LifeKeeper for Linux Core CD and use any install interface that supports Red Hat Package manager (RPM).
Details for using the rpm command are provided below:
Upgrading via Command Line - When the CD is inserted, enter the command change directories to /mnt/cdrom/LifeKeeper/RPMS, and use ls to view the packages. Select the appropriate LifeKeeper and recovery kit packages to upgrade on that server and enter rpm -U <package name> from the command line for each package. You will see informational messages confirming that the packages are being upgraded.
Note: RPM performs an upgrade by installing the desired package and then erasing the older version of the package. In some cases, it may be necessary to use the force option to upgrade packages that are nearly identical (e.g. upgrading from the evaluation version of the LifeKeeper for Linux product).
After upgrading, stop and restart the LifeKeeper GUI in order to load the updated GUI client.
If you are upgrading a LifeKeeper cluster with greater than two nodes, switch all applications back to the upgraded server.
Repeat this procedure for each server in the LifeKeeper cluster to be upgraded.
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.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation