This topic describes failover and failback settings for a clustered service or application. It also provides links to information about other settings that you can modify for a clustered service or application.

Modifying failover and failback settings, including preferred owners

You can adjust the failover settings, including preferred owners and failback settings, to control how the cluster responds when the application or service fails. You can configure these settings on the property sheet for the clustered service or application (on the General tab or the Failover tab). The following table provides examples that illustrate how these settings work.

Settings Effect

Example 1:

General tab, Preferred owner: Node1

Failover tab, Failback setting: Allow failback (Immediately)

If the service or application fails over from Node1 to Node2, when Node1 is again available, the service or application will fail back to Node1.

Example 2:

Failover tab, Maximum failures in the specified period: 2

Failover tab, Period (hours): 6

In a six-hour period, if the application or service fails no more than twice, it will be restarted or failed over each time. If the application or service fails a third time in the six-hour period, it will be left in the failed state.

The default value for the maximum number of failures is n-1, where n is the number of nodes. You can change the value, but we recommend a relatively low value, so that if multiple node failures occur, the application or service will not be moved between nodes indefinitely.

List of topics about modifying settings

The following topics provide details about settings that you can modify for a clustered service or application:

Additional references