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

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.
To get rid of this notice, you may want to browse the old wiki instead.

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:
2017-11-24 22:16:42

Active/Passive HA configuration

An active/passive configuration is the most basic HA configuration. In this type of configuration, one node is active running a ResourceGroup, and the other node is passive, simply waiting for the active side to fail.

The advantages of this configuration are that failing over causes no service degradation, provided that the passive machine is similar to the active machine. In addition, services are only restarted when machines fail, which typically results in half as many services interruptions as an active/active configuration.

The disadvantage of this configuration is that the passive machine isn't providing any kind of useful service, and is sometimes viewed as an inefficient use of resources.

To instruct Heartbeat to operate in active/passive mode, simply make sure you configure the auto_failback directive in your ha.cf file like this:

auto_failback off

If you wish to fail resources back to failed machines manually, then configure your system as an active/passive arrangement, and use the hb_standby command to move resources back to their preferred machines under administrator control.

See Also

Active/Active