A virtual server is a resource group consisting of an IP Address resource and a Network Na me
resource. Ownership of these virtual servers should b e assigned to the different server nodes. In
addition to providing load balancing capabilities, the virtual server allows for the transition of
group resources in failover situations.
2. Create a virtua l server group for each node in the cluster.
Cluster resource groups a re used to balance the processing load on the ser vers. D istribute ownership
of the groups between the virtual servers.
3. For NFS environments, configure the NFS server.
NFS specific procedures include entering audit and file lock information as well as setting up client
groups and user name mappings. These procedures are not unique to a clustered deployment and
are d etailed in the Microsoft Services for NFS section within the “Other network file and print services”
chapter. Changes to NFS setup information are automatically replicated to all nodes in a cluster.
4. Create the file share resources.
In a clustered environment, file shares are created as a type of cluster resource. Creating cluster
resources and file shares is documented later in this chapter.
5. Assign ownership of the file share resources to the resource groups.
a. Divide ownership of the file share resource b etween the resourc e groups, which are in turn
distributed between 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 that the resources are dependent on the virtual ser vers a nd 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 m anaged 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 sugg estions are listed below:
• Back up user and group mappings.
To avoid 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 con sistently.
Groups that are mapped to each other should contain the sam e users and the mem bers of the
groups should be properly mapped to each other to ensure proper file access.
• Map properly.
• Valid UNIX users should be m apped to valid Windows 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 the 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 n ame mappings using d om 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 create
mappings using local user and group accounts.
• In a clustered deployment, administer user name mapping on a computer that b elongs to a
trusted domain.
134
Cluster adm inistration
To Next Page
Loading...
