Linbit Becomes Heartbeat 2 Maintainer

Apr 16, 2010

The Linbit firm out of Vienna will take over care of the Heartbeat 2 cluster manager.

By supporting the proven but orphaned software, the Linbit high-availability (HA) specialists are offering users planning security. Heartbeat also adds some tread to their existing DRBD replication technology in the Linux HA environment.

The Heartbeat 2 cluster management software can provide the messaging and application layers for HA clusters. For the application layer, Pacemaker is increasingly taking over as the cluster resource manager from what was historically Heartbeat's own. The advantage being that Pacemaker uses Corosync. Heartbeat ended a long development freeze period with its version 3.0.2 in February.

Related content

  • DRBD Merged into Mainline Kernel

    The HA technology, Distributed Replicated Block Device (DRBD), is to be merged into the official Linux kernel, probably from version 2.6.33.

  • SUSE Linux Enterprise 11 Arrives

    Novell announced today that SUSE Linux Enterprise Server (SLES) is officially out in version 11. The SLES extensions for Mono and the desktop version SLED 11 should also concurrently hit the market. A high-availability extension is to follow.

  • High Availability: Linbit Merges DRBD+ with DRDB into Open Source

    Austrian company Linbit has announced that it is merging its DRBD+ commercial high availability (HA) software with the open source version DRBD to make a free software solution.

  • Pacemaker

    When a cluster node fails, the Pacemaker high-availability tool launches the services on another node. A lesser known feature is Pacemaker’s ability to put failed services back on their feet in the cluster manager.

  • RHEL 7

    On June 10, Red Hat launched a new major release of its enterprise distribution, RHEL 7. We take a look to find out where RHEL is headed.

comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More