Open topic with navigation
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 v4 root and any bind mounts must be exported by the primary server (the server where the NFS resource is being created). This implies NFS is running and the underlying file systems (root and bind mounts) are mounted. The root and bind mounts must be on shared devices that LifeKeeper can protect. If the underlying file systems are already protected by LifeKeeper, they must be in service on the primary server and have the highest priority. If the file systems are not already protected, then the recovery kit will place them under protection.
Note: If the NFS v4 root is /export with three subdirectories called bin, opt and other, local file systems /usr/local/bin and /usr/local/opt are bind mounted into the NFS v4 psuedo file system, then /export, /usr/local/bin and /usr/local/opt must be mounted on a shared device with /export mounted with write permission, /usr/local/bin and /usr/local/opt must be bind mounted into /export (mount --bind /usr/local/bin /export/bin and mount --bind /usr/local/opt /export/bin) and the /export, export/bin and /export/opt must all be exported. See the configuration example Active/Standby for NFS v4 for further information.
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.
When protecting NFS v4 root exports, /var/lib/nfs is moved to the NFS v4 root file system which must have write permissions set when mounted. To provide continued access, a symbolic link is created from /var/lib/nfs to the NFS v4 root. Because of this, Active/Active NFS v4 configurations are not supported nor are configuations with NFS v2/v3 and NFS v4. NFS v2/v3 exports should use the bind features of NFS v4 instead of attempting to make them standalone NFS v2/v3 exports.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation