HP ProLiant Storage Server User Guide (440584-003, September 2007)

as circumstances require. If the cluster node owning the group of file shares should be shut down or
fail, the other node in the cluster will begin sharing the directories until the original owner node is
brought back on line. At that time, ownership of the group and its resources can be brought back
to the original owner node.
Resource planning
1. Create a cluster group for each node in the cluster with an IP address resource and a network
name resourc
e.
Cluster resource groups are used to balance the pro cessing load on the servers. Distribute ownership
of the groups bet ween the virtual servers.
2. For NFS environments, configure the NFS server.
NFS specific procedures include entering audit and file lo ck information as well as setting up client
groups and user name mappings. These procedures are not unique to a clustered deployment and
are detailed in the Microsoft Services for NFS section within the “Other net work file and print services”
chapter. C
hanges to NFS setup information are automatically replicated to all nod es in a cluster.
3. Create the
file share resources.
4. Assign ownership of the file share resources to the resource groups.
a. Divide ownership of the file share resource between the resource groups, which are in turn
distributed bet ween the virtual servers, for effective load balancing.
b. Verify that the physical disk resource for this file share is also included in this group.
c. Verify t
hat the resources are dependent on the virtual ser vers and physical disk resources
from which the file share was created.
Permissions and access rights on share resources
File Share and NFS Share permissions must be managed using the Cluster Administrator tool versus the
individual shares on the file system themselves via Windows Explorer. Administering them through
the Cluster Administrator tool allows the permissions to migrate from one node to other. In addition,
permissions established using Explorer are lost after the share is failed or taken offline.
NFS cluster-specificissues
For convenience, all suggestions are listed below:
• Back
up user and group mappings.
To av
oid loss of complex advanced mappings in the case of a system failure, back up the
mappings whenever the mappings have been edited or new mappings have been added.
• Map consistently.
Grou
ps that are mapped to each other should contain the same users and the members of the
groups should be properly mapped to each other to ensure proper file access.
• Map properly.
•Val
id UNIX users should be mapped to valid Window s users.
• Valid UNIX groups should be mapped to valid Windows groups.
• Mapped Windows user must have the “Access this computer from the Network privilege”
or t
he mapping will be squashed.
• The mapped Windows user must have an active password, or the mapping will be squashed.
• In a clustered deployment, create user name mappings using dom a in user accounts.
Because the security identifiers of local accounts are recognized only by the local server, other
nodes in the cluster will not be able to resolve those accounts during a failover. Do not cre ate
ma
ppings using local user and group accounts.
• In a clustered deployment, administer user name mapping on a computer that belongs to a
trusted dom ain.
114
Cluster administration