You can configure the start, failover, and failback of cluster resources to happen manually or automatically.
IMPORTANT:Cluster Services works with NCP user connections so that the user data sessions are resumed after failover. However, non-NCP users might experience service interruption and need to reconnect to the server after the failover. Applications using server based storage must be restarted on the client even with NCP unless they are NCP reconnect aware.
With the resourcemode set to AUTO, the resource automatically starts on a server when the cluster is first brought up. If the resource mode is set to MANUAL, you can manually start the resource on a server when you want, instead of having it automatically start when servers in the cluster are brought up.
With the resourcemode set to AUTO, the resource automatically starts on the next server in the Preferred Nodes list if there is a hardware or software failure. If the resource mode is set to MANUAL, you can intervene after a failure occurs and before the resource is moved to another node.
With the resourcemode set to DISABLE, the resource does not fail back to its most preferred node when the most preferred node rejoins the cluster. If the resource mode is set to AUTO, the resource automatically fails back to its most preferred node when the most preferred node rejoins the cluster. Set the resource mode to MANUAL to prevent the resource from moving back to its preferred node when that node is brought back online, until you are ready to allow it to happen.
The preferred node is the first server in thelist for the resource.
IMPORTANT:Resources fail back only to the first node in theirlist. For example, if a resource has failed over to three servers since it originally ran on its preferred node, and the second server the resource was running on comes back up, the resource does not fail back to that second server.
Resources do not automatically move from node to node just because a node higher in thelist rejoins the cluster, unless the mode is set to AUTO and the first node in the list rejoins the cluster.
If you are creating a new cluster resource, the Resource Policies page should already be displayed. You can start with Step 6.
In iManager, select> .
Select the cluster that you want to manage.
If the cluster does not appear in your list, add the cluster to your list as described in Section 8.2, Setting Up a Personalized List of Clusters to Manage.
Select the cluster resource to open its Properties page.
You can also select the check box next to the cluster resource, then click.
On the Properties page, click thetab.
(Optional) Select thecheck box if you want to ensure that the resource runs only on the master node in the cluster.
If the master node in the cluster fails, the resource fails over to whichever node becomes the master.
(Optional) Select thecheck box if you don’t want the cluster-wide timeout period and node number limit enforced.
The quorum default values were set when you installed Cluster Services. You can change the quorum default values by accessing the properties page for the Cluster object.
Selecting this box ensures that the resource is launched immediately on any server in the Preferred Nodes list as soon as any server in the list is brought online.
Specify the, , and modes for this resource.
The default for bothand modes is AUTO, and the default for mode is DISABLE.
Do one of the following:
If you are configuring a new resource, click Section 10.10, Configuring Preferred Nodes and Node Failover Order for a Resource., then continue with
Clickto save your changes.
Changes for a resource’s properties are not applied while the resource is loaded or running on a server. You must offline, then online the resource to activate the changes for the resource.