Specify which nodes can own a resource

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To specify which nodes can own a resource

  1. Open Cluster Administrator.

  2. In the console tree, click the Resources folder.

  3. In the details pane, click the appropriate resource.

  4. On the File menu, click Properties.

  5. On the General tab, next to Possible owners, click Modify.

  6. Specify which nodes you want to be possible owners.

    • To add a possible owner, under Available nodes, click a node, and then click the right arrow.

    • To remove a possible owner, under Possible owners, click a node, and then click the left arrow.

Notes

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

  • To open Cluster Administrator, click Start, click Control Panel, double-click Administrative Tools, and then double-click Cluster Administrator.

  • A possible owner is a node that is capable of running a resource.

  • If you want to make a group capable of failing over, it must have more than one possible owner.

  • If a resource has no possible owners, it will not come online. This can be useful if you want to keep a resource offline but you do not want to delete it and lose its configuration settings.

  • If the resource DLL for a particular resource type is not available on some nodes, these nodes are automatically removed from the possible owners list for all the resources of this type.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Server Cluster Resources
Failover and failback
Nodes