Modifying Settings for a Clustered Service or Application
Applies To: Windows Server 2008
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: 10 Failover tab, Period (hours): 6 |
In a six-hour period, if the application or service fails ten times (or less), it will be restarted or failed over each time. If the application or service fails an eleventh time in the six-hour period, it will be left in the failed state. |
The following topics provide details about settings that you can modify for a clustered service or application:
Add Storage for a Clustered Service or Application
For information about adding a disk to the cluster itself, so that the disk is available for adding to a clustered service or application, see Add Storage to a Failover Cluster.
Modify Failover Settings for a Clustered Service or Application
Additional references
For design and deployment information for failover clusters, see https://go.microsoft.com/fwlink/?LinkId=86168.