Chapter 4. Upgrading from previous Heartbeat versions
4.1. Upgrading from Heartbeat 2.1 clusters not using the CRM
For Heartbeat 2.1 clusters not using the CRM (i.e., clusters configured with the haresources file, an upgrade to 3.0 involves converting the current configuration to one that is suitable for Pacemaker.
Note
This upgrade procedure does incur application down time. However, when the upgrade is properly planned, tested, and executed, this down time amounts to minutes, possibly even seconds (depending on configuration).
4.1.1. Stopping Heartbeat services
You should commence the upgrade procedure on your current standby node, that is, the cluster node currently not running any resources. If your cluster is using an active-active configuration (both nodes running resources), select one and issue the following command to transfer all resources to the peer node:
# hb_standby
Then, and on that node only, stop Heartbeat services:
# /etc/init.d/heartbeat stop
While upgrading, it is important to recall that the monolithic Heartbeat 2.1 tree has been split up into modular parts. Thus you will replace Heartbeat with three individual pieces of software: Cluster Glue, Pacemaker, and Heartbeat 3 which comprises just the cluster messaging layer.
In the unpacked archive that you installed Heartbeat 2.1 from, run make uninstall. Then, install Cluster Glue and Heartbeat.
When installing packages manually, uninstall the heartbeat package first. Then install cluster-glue, the version 3 heartbeat package, resource-agents, and pacemaker.
When upgrading using an APT, YUM, or Zypper repository, you should just be able to run the install command for heartbeat version 3 and pacemaker, and the dependencies will be resolved automatically.
Do not restart Heartbeat services at this point.
4.1.3. Enabling the Heartbeat cluster to use Pacemaker
The cluster messaging layer must now be instructed to start Pacemaker on cluster start-up. To do so, add
crm respawn
to your
ha.cf configuration file.
Important
At this point, you should also check your
ha.cf file against the
ha.cf(5) manual page, and remove any deprecated options.
When your ha.cf modifications are complete, copy the file to the peer node.
4.1.4. Restarting Heartbeat
Your cluster is now ready to be restarted in Pacemaker-enabled mode. To do so:
Run /etc/init.d/heartbeat stop on your still-active node. This will shutdown your cluster resources.
Run /etc/init.d/heartbeat start on your standby node (the one where you created your CIB). This will start the local Heartbeat instance and Pacemaker, and wait for other cluster nodes to check in.
Run /etc/init.d/heartbeat start on your the other node. This will start the local Heartbeat instance and Pacemaker, fetch the CIB automatically, and start applications.
