Managing MC/ServiceGuard NFS A.11.11.03 and A.11.23.02 (June 2004)

Installing and Configuring MC/ServiceGuard NFS
Before Creating an MC/ServiceGuard NFS Package
Chapter 2 31
between the primary and adoptive nodes, the client’s file handle
would no longer point to the correct file location after movement of
the package to a different node.
It is recommended that filesystems used for NFS be created as
journalled file systems (FStype vxfs). This ensures the fastest
recovery time in the event of a package switch to another node.
9. Make sure the user IDs and group IDs of those who access the
MC/ServiceGuard NFS file system are the same on all nodes that can
run the package. Make sure the /etc/passwd and /etc/group files
are the same on the primary node and all adoptive nodes, or use NIS
to manage the passwd and group databases. For information on
configuring NIS, see the Installing and Administering NFS Services
manual.
10. Create an entry for the name of the package in the DNS or NIS name
resolution files, or in /etc/hosts, so that users will mount the
exported file systems from the correct node. This entry maps the
package name to the package’s relocatable IP address.
11. Decide whether to place executables locally on each client or on the
NFS server. There are a number of trade-offs to be aware of
regarding the location of executables with MC/ServiceGuard NFS.
The advantages of keeping executables local to each client are as
follows:
• No failover time. If the executables are local to the client, there is
no delay if the NFS server fails.
• Faster access to the executables than accessing them through the
network.
The advantage of putting the executables on the NFS server is as
follows:
• Executable management. If the executables are located in one
centralized location, the administrator must update only one
copy when changes are made.
If executables are placed on the NFS server, you need to ensure that
interrupts are handled correctly in a MC/ServiceGuard environment.
The client must mount the filesystem using the nointr option. This
mount option will ensure that the executable continues running
correctly on the client after a failover of the server occurs. For
example, enter the following command on the NFS client:
B5140-90020.book Page 31 Thursday, June 3, 2004 5:04 PM