Table of Contents
- 6.1. Upgrading from Heartbeat 2.1 clusters not using the CRM
- 6.2. Upgrading from CRM-enabled Heartbeat 2.1 clusters
- 6.2.1. Placing the cluster in unmanaged mode
- 6.2.2. Backing up the CIB
- 6.2.3. Stopping Heartbeat services
- 6.2.4. Wiping files related to the CRM
- 6.2.5. Restoring the CIB
- 6.2.6. Upgrading software
- 6.2.7. Restarting Heartbeat services
- 6.2.8. Returning the cluster to managed mode
- 6.2.9. Upgrading the CIB schema
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]](images/note.png) | 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). |
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.
-
Upgrading from source: In the unpacked archive that you installed
Heartbeat 2.1 from, run
make uninstall. Then, install Cluster Glue and Heartbeat. -
Upgrading using locally built packages: When installing packages
manually, uninstall the
heartbeatpackage first. Then installcluster-glue, the version 3heartbeatpackage,resource-agents, andpacemaker. - Upgrading using a package repository: 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.
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]](images/important.png) | Important |
|---|---|
At this point, you should also check your ha.cf file
against the |
When your ha.cf modifications are complete, copy the file to the peer
node.
Your cluster is now ready to be restarted in Pacemaker-enabled mode. To do so:
-
Run
/etc/init.d/heartbeat stopon your still-active node. This will shutdown your cluster resources. -
Run
/etc/init.d/heartbeat starton 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 starton your the other node. This will start the local Heartbeat instance and Pacemaker, fetch the CIB automatically, and start applications.