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:
2014-10-25 15:52:50

Note

In Heartbeat 2.x versions, haresources is no longer used if CRM is enabled. Instead /var/lib/heartbeat/crm/cib.xml is used, details can be found in GettingStartedV2.

Configuring the haresources file

The haresources file is one of the most important files to configure when using Heartbeat.

The general form of a line in the haresources file is simple:

preferred-node resourcename ...

The list of resources on a line is referred to as a resource group.

The preferred-node is the node that this resource group would prefer to be run on. Continuations of lines can be made with '\' characters at the end of the line.

Heartbeat resources are acquired in a left-to-right order, and released in a right-to-left order.

Note that it is absolutely mandatory for the haresources files to be identical on both machines.

This preferred-node is the nominal owner of the resources. That is, this is the machine who will own them if both machines are available and you have selected autofailback on. A fairly common error is to think that you have to tell each machine to own the same set of resources on both machines. By doing this, you have directed Heartbeat to make each machine owner of the same set of resources, and you wind up with both machines trying to run the same resources at the same time. If you do this, BadThingsWillHappen.

Note: Make sure that the first resource in each resource group is unique because the first resource will be used as resource group name.

See Also

hb_standby, hb_takeover, ha.cf, authkeys, Configuring Heartbeat, Getting Started - Configuring haresources