NFS Specific Configuration Considerations

The following should be considered before using the LifeKeeper NFS Server Recovery Kit:

• The NFS file system to be placed under LifeKeeper protection must be exported by the primary server (the server where the NFS resource is being created). This implies that NFS is running and the underlying file system is mounted.

*Note: If the /home directory is shared via NFS, then /home is the underlying file system.

• When you export a read/write file system, use the sync option. This option requests that all file system writes be committed to disk before the write request completes. If the sync option is not used with an NFS file system under LifeKeeper protection, data may be lost during a failover.

• The underlying file system must be on a shared device and mounted with write permission.

• If the underlying file system is already protected by LifeKeeper, it must be in service on the primary server and have the highest priority. If the underlying file system is not under LifeKeeper protection, then the Recovery Kit will place it under protection.

• The NFS Server Recovery Kit requires an IP resource that must be created and in service on the primary server. The IP resource must also have its highest priority on the primary server.

• Before creation of the NFS resource, clients must be able to mount the NFS file system using the LifeKeeper-protected IP address.

• When you extend an NFS file system resource, the file system must mount at the same mount point on each server.

*NFSv2 is not supported on RHEL 7/CentOS 7/OL 7 or later.

*NFS over UDP is not supported on RHEL 8 or later.