This section provides an example of Active/Standby for NFS v4. In this configuration, Server 1 is considered active because it is running NFS and exporting the file systems. Server 2 does other processing. If Server 1 fails, Server 2 gains access to the file systems and uses the LifeKeeper secondary hierarchy to make it available to clients.
*Note: In an active/standby configuration, Server 2 might be running NFS but does not have any other NFS resources under LifeKeeper protection.
Active/Standby Configuration Example for NFS v4
![]()
Configuration Notes:
- The NFS software must be installed on both servers.
- The underlying file systems (File Systems A, B and C) must be mounted and be on shared (or replicated) disks.
- Bind mounts must be completed prior to creation (bind /usr/local/bin to /export/bin and bind /usr/local/opt to /export/opt).
- The NFS export points are /export, /export/bin and /export/opt.
- The exported file systems must have the same mount point on both the primary and backup servers.
- Server 2 cannot access files and directories on the shared disk while Server 1 is active.
Creating a Resource Hierarchy to Server 1:
Server: |
Server1 |
Export Point: |
/export |
IP Tag: |
ip-172.17.100.202 |
NFS Tag: |
nfs-/export |
*Note: With the selection of the export points, bind information is picked up automatically; therefore, no input is required to create and extend the hierarchy.
Extending a Resource Hierarchy to Server 2:
Template Server: |
Server1 |
Tag to Extend: |
nfs-/export |
Target Server: |
Server2 |
Target Priority: |
10 |
Post your comment on this topic.