| Installing and Configuring MC/ServiceGuard NFS |
| Configuring an MC/ServiceGuard NFS Package |
| See “Example Two - One Adoptive Node for Two Packages with File Lock |
| Migration” on page 64 for a sample configuration using the package |
| control option. |
|
|
NOTE | The NFS specific variables have been moved to NFS specific control |
| script in MC/ServiceGuard NFS Toolkit with the A.11.11.02 and |
| A.11.00.05 releases. See section “Editing the NFS Control Script |
| (hanfs.sh)” on page 41 for the details. |
| Editing nfs.cntl for NFS Toolkit A.11.00.04 and A.11.11.01 (or |
| |
| lower) |
| For MC/ServiceGuard NFS Toolkit A.11.00.04 or lower for |
| or MC/ServiceGuard NFS Toolkit A.11.11.01 or lower for |
| using MC/ServiceGuard A.11.09 (or below) framework. |
| Example steps: |
1.Create a separate VG[n] variable for each volume group.
VG[0]=/dev/vg01
VG[1]=/dev/vg02
...
2.Create a separate LV[n] and FS[n] variable for each volume group and file system that will be mounted on the server:.
LV[0]=/dev/vg01/lvol1;FS[0]=/ha_root LV[1]=/dev/vg01/lvol2;FS[1]=/users/scaf LV[2]=/dev/vg02/lvol1;FS[2]=/ha_data
3.Create a separate XFS[n] variable for each NFS directory to be exported. Specify the directory name and any export options.
XFS[0]=”/ha_root” XFS[1]=”/users/scaf”
Do not configure these exported directories in the /etc/exports file. When an NFS server boots up, it attempts to export all file systems in its /etc/exports file. If those file systems are not currently present on the NFS server node, the node cannot boot properly. This
Chapter 2 | 37 |