Overview of Serviceguard NFS
Supported Configurations
Simple Failover to an Idle NFS Server
Figure
Figure | Simple Failover to an Idle NFS Server |
|
|
| |||||
| Before Failover: |
|
|
| |||||
|
|
|
|
|
|
|
|
| |
|
| Node_A |
|
|
|
| Node_B | ||
|
|
|
|
|
| Pkg_1 |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
| disks |
|
|
|
|
|
|
|
|
| ||||
| After Failover: |
|
|
| |||||
|
|
|
|
|
| ||||
|
| Node_A |
|
|
| Node_B | |||
|
|
|
|
|
| Pkg_1 |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
| disks |
|
|
|
|
|
|
|
|
|
|
|
|
|
Node_A is the primary node for NFS server package Pkg_1. When Node_A fails, Node_B adopts Pkg_1. This means that Node_B locally mounts the file systems associated with Pkg_1 and exports them. Both Node_A and Node_B must have access to the disks that hold the file systems for Pkg_1.
Chapter 1 | 13 |