MSNFS administration on a server cluster
The Microsoft Services for Network File System (NFS) online help provides server cluster information
for the following topics:
•
Configuring shared folders on a server cluster
Configuring an NFS share as a cluster resource
◦
◦
Modifying an NFS shared cluster resource
◦
Deleting an NFS shared cluster resource
•
Using Microsoft Services for NFS with server clusters
Understanding how Server for NFS works with server clusters
◦
◦
Using Server for NFS on a server cluster
•
Configuring User Name Mapping on a server cluster
For further details, see the online help for Microsoft Services for Network File System.
Best practices for running Server for NFS in a server cluster
•
Stop Server for NFS before stopping the server cluster.
•
Ensure share availability when a node fails.
•
Use the appropriate tool to manage Network File System (NFS) share cluster resources.
•
Avoid conflicting share names.
•
Ensure the availability of audit logs.
•
Move file shares or take them offline before stopping Server for NFS.
•
Take resources offline before modifying.
•
Administer Server for NFS only from computers in a trusted domain.
•
Restart the Server for NFS service after the cluster service restarts.
•
Choose the appropriate sharing mode.
•
Use the command line properly when creating or modifying NFS share cluster resources.
•
Use hard mounts.
•
Use the correct virtual server name.
Print services in a cluster
The Windows Storage Server 2012 or 2012 R2 Cluster service implementation increases availability
of critical print servers. A print spooler service on a clustered print server may be hosted on any
of the nodes in the cluster. As with all cluster resources, clients should access the print server by
its virtual network name or virtual IP address.
Creating a cluster printer spooler
Printer spoolers should be created in a separate group dedicated to this purpose for ease of
management. For each printer spooler, a physical resource is required to instantiate the print
spooler resource. In some cases, dedicated physical resources are not available and hence sharing
of the physical resource among other members of the group is acceptable, remembering that all
members of a group are managed as a unit. Hence, the group will failover and failback as a
group.
To create a printer spooler:
72
Cluster administration
