Heartbeat is an alternative to Corosync for the cluster communications layer. Like Corosync, it constitutes the "lower" half of the high-availability stack (the "upper" half is cluster resource management, such as Pacemaker).

We have built and run Heartbeat clusters for years and know its capabilities inside and out. Whether you are planning a no-downtime migration to Corosync, or an upgrade of existing legacy systems, we'll be happy to help.

What's it good for?

Heartbeat is a solid cluster communication manager for small to medium-sized clusters of up to 8 nodes. It supports communications via UDP broadcast, unicast or multicast. Pacemaker supports Heartbeat out of the box in Ubuntu and Debian GNU/Linux. For SLES and RHEL, custom Pacemaker packages are needed; these, however, are obviously unsupported by the system vendors.

For high-availability Pacemaker configurations with cluster file systems such as OCFS2 or GFS2, Heartbeat is not an option. Heartbeat-based Pacemaker clusters do not support Distributed Lock Manager (DLM) integration.

If I run on Heartbeat, do I need Pacemaker?


Legacy versions of Heartbeat contain a simplistic resource manager that should no longer be used. We can assist you in a smooth transition.

Can I migrate my Pacemaker cluster?

If your Pacemaker cluster runs on Heartbeat and you'd like to move to Corosync, we can assist you in the migration. It's even possible without interruption to your cluster services.

If you're experiencing issues with Heartbeat, we can help rapidly. We can offer a wide array of Heartbeat consulting services. Talk to one of us within the next 15 minutes. Ask The Expert Now!