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-10 01:38:01

Allegiance Internet provides enterprise level Internet solutions to customers in the U.S.

This entry courtesy of KevinDwyer, Network Security Engineer.

We deployed several firewall pairs running heartbeat to protect the Network Operations Center and the Network Security/Abuse network. Heartbeat allows us to reuse older hardware without worrying about failures and thus interruptions in service.

Intercom TI is a Linux service company, offering commercial implementations of firewalls, Qmail servers and remote Linux server support and administration.

This entry courtesy of Francisco Jen Ou

We installed an HA pair for an ISP in Sao Paulo, Brazil, who offers wireless Internet access for some 2,500 users. The HA pair runs Conectiva Linux 8.0 (kernel 2.4.18) and heartbeat 0.4.9 over serial connection. Its main applications are:

bandwidth control, based on CQB, for limiting bandwidth usage by single users on the shared radio network.

firewall and NAT for the radio users

Apache with MySQL and Sun ASP (former ChiliSoft ASP), hosting CRM and ERP systems.

DNS cache and server based on djbdns.

Levonline AB is a Stockholm-based webhosting company using the latest technology based on Linux.

This entry courtesy of Jerker Nyberg

At Levonline, we use Heartbeat together with LVS for redundant load balancing of the webservers.

We also use Heartbeat for redundant MySQL (data is written to two servers and read from the active one), DNS and routing on the same machines. Here is a simple illustration of our setup:

Thank you for great software

The Norcross Group provides a comprehensive set of Internet Engineering resources (consulting services).

This entry courtesy of Greg Freemyer.

We've put in 2 HA installs for 2 different customers. Both are on Alpha's running Tru64 5.x I ported heartbeat 4.7 about 18 months ago, and that was what I used. With both I use externally shared storage, which I move from node to node.

One customer is an ISP and is running the typical suite of ISP apps: radius, ftp, web-server, smtp, pop.

The other is a small e-commerce company, and they are running Oracle DB and Oracle Application Server (OAS)., ltd. has been providing Linux system and network administration consulting services and hosting since 1995.

This entry courtesy of Sean Reifschneider

Heartbeat has allowed us to provide decreases in both planned and unplanned outages. To accomplish this, we created a fairly simple configuration involving switching the gateway IP address between the cluster nodes, and dynamic routing daemons for the links with our upstream ISPs.

Heartbeat and spare hardware allowed us to create a prototype pair of redundant routers at no cost beyond our time. Based on my experience with other commercial high availability solutions, I would estimate that heartbeat took no more time to learn and deploy than other high availability solutions.

After the initial test environment was set up and thoroughly tested, we were able to deploy the redundant routers with no additional cost outlay. We were able to re-purpose a recently released server to run as the standby node, bring that up in our network for a week to ensure there were no problems with it, and then re-load our regular router with the new configuration, and bring it up as the primary.

While we can now survive a number of networking and hardware failures, we're finding that one of the primary benefits of this solution is that we can do hardware and software maintenance on the routers while experiencing no downtime. A clean shutdown of the primary router results in a seamless fail-over to the secondary machine with no lost packets.

Heartbeat has allowed us to provide the benefits of a very expensive Cisco solution for the expense of a couple of dual-port gigabit cards. I haven't priced it out, but based on other hardware we've purchased I would estimate that a similar Cisco solution would have cost at least $20,000 and possibly up to $100,000. Heartbeat has allowed us to provide world-class service to our hosting clients at reasonable costs. Additionally, we were able to prototype the deployment and provide a proof-of-concept at no cost (more info).

Heartbeat is a great addition to the Linux software stack. Thanks Alan.

Editor's note:, ltd. is one of the Linux-HA ProjectFriends, providing mailing list, CVS and other services for the project, for which we are most appreciative.

Web-Com is a Santa Clara, CA based Internet development firm specializing in web based applications for small and mid-sized business.

This entry courtesy of Joel Fowler

Web-Com Development is a web systems development firm located in Santa Clara, California. We also offer hosting for sites we develop. Some examples include our own and

We are currently in the process of developing webSentry, a web site monitoring and service management application, which will be offered as a service. The application is not yet publically available.

High availability was a requirement of webSentry. It includes both batch and online elements that are managed by heartbeat. HA was also beneficial to the other virtual web sites supported by these clustered servers.

Our application infrastructure consists of the following components: RH Linux, MySQL (with two-way replication between the clustered servers), Apache (including perl cgi, mod_perl, mod_ jk, and mod_ssl), Tomcat

Resources under heartbeat control: production VIP,, webSentry Collectors (batch). is a perl script which (1) starts Tomcat, (2) monitors the health of important online resources (Apache, Tomcat, MySQL, DNS, and gateway access), and (3) takes appropriate remedial action (e.g. restarts Tomcat, initiates heartbeat failover, and reboots the system) to ensure online availability.