This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag


About Us

Contact Us

Legal Info

How To Contribute

Security Issues

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2019-12-06 10:48:06

The Bavarian Radio Station, Munich

This entry courtesy of Werner Schultheiß (, 1/2002. Web services "Olympic Games, Salt Lake City" for the German ARD with 2 IBM Netfinity a.k.a. x350 (4 CPUs, 2 GB RAM, 280 GB RAID5), heartbeat over 2 serial null modem cables, local iptables(8) firewall, rsync(8)-based data import by the inhouse staging and deploying system . System took a hit because of a typo, and heartbeat(8) took over once during the games. Nobody took any notice of it during the games ;-}. Gone to archive in 6/2002.

LVS evaluation cluster, 5/2002. Heartbeated (redundant) load balancer on 2 IBM x330 (2 CPUs, 1.2 GB RAM) with Linux LVS on Kernel 2.4.18, heartbeat over 1 serial and 1 ethernet cross cable connection which is also used by rsync(1) for data consistency. Worked great and is currently fall back solution if problems with BigIron switch persist.

firewall gateway internet-dmz, 7/2002. Hardware and system id. to "LVS evaluation cluster", plus 7 NIC ports and iptables firewall. It was a bit messy to include patches for 4-port-NIC D-LINK DFE-580TX into Kernel 2.4.18. System is up and running. The systems will migrate from HD to CDROM (diskless).

Several other installations are expected to be completed in 2002 and beyond. These include a firewall router (dmz-intranets), NFS fileserver, Samba file server, Oracle, MySQL and Postgres databases.

GREAT app, works perfectly. I would be happy to contribute with tech and work. Werner Schultheiß, Letras Berlin-Munich, 20020925.

The BBC exists to enrich people's lives with great programmes and services that inform, educate and entertain. Its vision is to be the most creative, trusted organisation in the world.

This entry courtesy of Neil Loffhagen

As an organisation we had the need to replace an old NT 4 Server running as a proxy for several overseas sites. It was decided to go for Squid, on a Linux box, distribution not initially decided. Company wanted some system with failover, so that if one server went down, another would automatically step in and take over the role. We needed a tool that would function over just a network connection, as the Servers would each be in different locations, although in the same site. After looking around the heartbeat tool was chosen. On paper it seemed very much to fill the function of swapping services between servers. Then we needed to chose a distro to run it on.

Initially was a bit hesitant as it seemed purely a text editing job. No real GUI to use for setup. On investigation realised that there was a GUI available with the SuSe, now Novell distribution. So installed SuSe on two Servers and went to use the GUI. Must admit to finding it a bit confusing :( So did a bit more reading of how the text files needed to be set up and found it not difficult at all. Like many an old Windows person, had a bit of an aversion of the command line and configuration text file editing. However, was pleasantly surprised. The two main files we edited are below:

bcast eth0
keepalive 2
warntime 10
deadtime 30
udpport 694
auto_failback on
node msquid01
node msquid02
respawn hacluster /usr/lib/heartbeat/ipfail


msquid01 squid

We found the following a good introduction to Linux High-Availability, which should explain our chosen settings in a bit more detail -

Once the above files were in place, we rebooted the Servers. Once rebooted, login as normal user and checked that the heartbeat and squid services are both running. And they were. Users were able to browse the web okay, using the virtual IP address. So, now the test. We did a ssh to the virtual IP and ended up logging in the main Server, which was what was expected. We then powered down the main server and users were able to continue browsing the web. We did another ssh to the virtual IP address and this time ended up on the backup server, which again was expected. Failover was working okay.

The above article recommends using serial connection, as well as Ethernet, but due to differing locations that was not possible in our case.

Another reason, we chose heartbeat, was the cost. Although we had to purchase SuSe we felt it was a cost saving compared to another major Linux distos that used their own failover tool. To save even more cost you should be able to use Debian or other "free" distros.

The Weather Channel® brings timely weather information to the world through cable networks, the internet, radio and newspapers.

This entry courtesy of Joe Henggeler

At The Weather Channel, we currently use heartbeat on a two-node cluster which handles transient storage for delivery/receipt of (1) critical weather data for our customers, and (2) video footage from cameramen. The hardware is : 2 Intel 1U's each connected to a 2-channel 350 GB RAID array. The services this cluster offers are ftp, nfs, http, and other custom services. The OS is Mandrake (to take advantage of ReiserFS). A future use for heartbeat within our organization is to port this to other operating systems (eg., Solaris, FreeBSD) for even more mission critical services.

From my experience, I was extremely impressed with the ease of installation/compilation on linux, and the stability of the cluster. This cluster has been running for approximately eight months (with forced manual failovers for updates and maintenance), and heartbeat has been running solid with virtually no interruptions in service.