Installation guide

basic configuration schema:

<rm>

<failoverdomain name="name" restricted="[0|1]" ordered="[0|1]"

nofailback="[0|1]">

...

</failoverdomain>

...

</failoverdomains>

</rm>

The failover domains can be configured in different ways. The following configuration

attributes can be set to define the failover rules:

Attribute Description

restricted domain Services bound to the domain can only run on

cluster members which are also members of the

failover domain. If no members of the failover

domain are available, the service is placed in the

stopped state.

unrestricted domain Services bound to this domain can run on all cluster

members but will run on a member of the domain

whenever one is available. This means that if a

service is running outside of the domain and a

member of the domain comes online, the service

will migrate to that member.

ordered domain The order specified in the configuration dictates the

order of preference of members within the domain.

The highest-ranking member of the domain will run

the service whenever it is online. This means that if

member A has a higher-rank than member B, the

service will migrate to A if it was running on B if A

transitions from offline to online.

unordered domain Members of the domain have no order of

preference; any member may run the service.

Services will always migrate to members of their

failover domain whenever possible, however, in an

unordered domain.

nofailback Enabling this option for an ordered failover domain

will prevent automated fail-back after a more-

preferred node rejoins the cluster.