Basic Cluster Administration Procedures; Failing Over And Failing Back; Network Name Parameters - HP ProLiant 300 Series Administration Manual

Figure 105 Network Name Parameters
8. Select whether or not DNS registration must succeed and whether to enable kerberos authentication
and click Next to continue.
9. Review the configuration, and then click Finish to create the resource.
10. After the resource is created it is necessary to bring it online. On the Cluster Resources page,
select the resource and click Bring Online.
11. Click OK on the Bring a Resource Online page to bring the new resource online.

Basic cluster administration procedures

Failing over and failing back

As previously mentioned, when a node goes offline, all resources dependent on that node are
automatically failed over to another node. Processing continues, but in a reduced manner because all
operations must be processed on the remaining node(s). In clusters containing more than two nodes,
additional fail over rules can be applied. For instance, groups can be configured to fail over different
nodes to balance the additional work load imposed by the failed node. Nodes can be excluded from the
possible owners list to prevent a resource from coming online on a particular node. Lastly the preferred
owners list can be ordered, to provide an ordered list of failover nodes. Using these tools, the failover
of resources can be controlled with in a multinode cluster to provide a controlled balanced failover
methodology that balances the increased work load.
Because operating environments differ, the administrator must indicate whether the system will
automatically fail the resources (organized by resource groups) back to their original node or will leave
the resources failed over, waiting for the resources to be moved back manually.
NOTE:
If the storage server is not set to automatically fail back the resources to their designated owner, the
resources must be moved back manually each time a failover occurs.
200
Cluster Administration