Managing Serviceguard NFS for Linux, July 2007

Installing and Configuring Serviceguard NFS for Linux
Before Creating an Serviceguard NFS Package
Chapter 228
3. Configure the disk hardware for high availability. Data disks
associated with Serviceguard NFS must be external disks. All the
nodes that support the Serviceguard NFS package must have access
to the external disks. For most disks this means they must be
attached to a shared bus that is connected to all nodes which support
the package. The disk on which NFS volume is configured can be
either a single lun or a split site raid1 array, which provides a level
of disaster tolerance to the NFS volume. This can be achieved by
setting up a Serviceguard Extended Distance Cluster which uses the
linux software RAID as the basic building block. For information on
setting up the Extended Distance Cluster, see the HP Serviceguard
Extended Distance Cluster for Linux Deployment Guide.
4. Use LVM commands to set up volume groups, logical volumes, and
file systems as needed for the data that will be exported to clients.
Refer to the Managing Serviceguard manual.
a. Create a directory for each NFS package. For example:
/usr/local/cmcluster/nfs1
b. The names of the volume groups must be unique within the
cluster, and the major and minor numbers associated with the
volume groups must be the same on all nodes. In addition, the
mounting points and exported file system names must be the
same on all nodes.
The preceding requirements exist because NFS uses the major
number, minor number, inode number, and exported directory as
part of a file handle to uniquely identify each NFS file. If
differences exist 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.
5. Make sure the user IDs and group IDs of those who access the
Serviceguard NFS file system are the same on all nodes that can run
the package.
Make sure the user IDs and group IDs in 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.
6. 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.