HP Serviceguard Toolkit for NFS manual Overview of the NFS File Lock Migration Feature

Page 11

Overview of MC/ServiceGuard NFS

Overview of the NFS File Lock Migration Feature

• Any client that holds NFS file locks against files residing in the HA/NFS package (transitioned between servers) sends reclaim requests to the adoptive node (where the exported filesystems currently reside) and reclaims its locks.

• After rpc.statd sends the crash recovery notification messages, the

 

SM entries in the package holding directory are removed, and the

 

nfs.flm script is started on the adoptive node. The script once again

 

copies each /var/statmon/sm file on the HA/NFS server into the

 

holding directory, every five seconds. Each file residing in the

 

/var/statmon/sm directory on the adoptive node following the

 

package migration represents a client that either reclaimed its locks

 

after failover or has established new locks after failover.

 

 

NOTE

To enable the File Lock Migration feature, you need MC/ServiceGuard

 

version A.11.15.

 

To ensure that the File Lock Migration feature functions properly, install

 

HP-UX 11i v1 NFS General Release and Performance Patch,

 

PHNE_26388 (or a superseding patch). For HP-UX 11i v2, the feature

 

functions properly without a patch.

 

 

Chapter 1

11

Image 11
Contents Edition Managing MC/ServiceGuard NFS A.11.23.02Legal Notices Contents Index Figures Figures NFS Overview of MC/ServiceGuard NFS Limitations of MC/ServiceGuard NFS Overview of the NFS File Lock Migration Feature Overview of the NFS File Lock Migration Feature Supported Configurations Pkg1 disks Simple Failover to an Idle NFS ServerPkg2 Disks Failover from One Active NFS Server to AnotherPackages Host Configured as Adoptive Node for MultipleCascading Failover with Three Adoptive Nodes NFS NFS Server-to-Server Cross MountingSupported Configurations Starting File Lock Migration Starting the NFS ServicesHow the Control and Monitor Scripts Work Halting the NFS Services Monitoring the NFS Services On the Client Side Installing and Configuring Installing and Configuring MC/ServiceGuard NFS Readme Installing MC/ServiceGuard NFSCmmakepkg -p /opt/cmcluster/nfs/nfs.conf ServiceGuard NFS Toolkit Monitoring NFS/TCP Services with MCChapter Before Creating an MC/ServiceGuard NFS Package NUMNFSD=10 Before Creating an MC/ServiceGuard NFS Package Mount -o nointr relocatableip/usr/src /usr/src Configuring an MC/ServiceGuard NFS Package Copying the Template Files Editing the Control Script nfs.cntl IP0=15.13.114.243 SUBNET0=15.13.112.0 Lower Etc/hosts file Configuring an MC/ServiceGuard NFS Package Configuring an MC/ServiceGuard NFS Package Editing the NFS Control Script hanfs.sh Netswitchingenabled Editing the File Lock Migration Script nfs.flm Configuring an MC/ServiceGuard NFS Package Editing the NFS Monitor Script nfs.mon Editing the Package Configuration File nfs.conf Configuring an MC/ServiceGuard NFS Package Configuring Server-to-Server Cross-Mounts Optional SNFS0=nfs1/hanfs/nfsu011CNFS0=/nfs/nfsu011 Configuring an MC/ServiceGuard NFS Package Run the cluster using the following command cmruncl -v-f Configuring an MC/ServiceGuard NFS Package Chapter Sample Configurations Sample Configurations Basil Sage Example One Three-Server Mutual TakeoverThree-Server Mutual Takeover after One Server Fails Cluster Configuration File for Three-Server Mutual Takeover Package Configuration File for pkg01 Nfs.cntl Control Script NFS Control Scripts for pkg01Package Configuration File for pkg02 NFS Control Scripts for pkg02 Package Configuration File for pkg03 NFS Control Scripts for pkg03 Packages with File Lock Migration Example Two One Adoptive Node for TwoSage Basil Pkg02 VOLUMEGROUP/dev/nfsu01 VOLUMEGROUP/dev/nfsu02 Package Configuration File for pkg01 NFS Control Scripts for pkg01 Hanfs.sh Control Script Nfs.flm Script NFS File Lock Migration and Monitor Scripts for pkg01Package Configuration File for pkg02 NFS Control Scripts for pkg02 NFSFLMSCRIPT=$0%/*/nfs2.flm NFS File Lock Migration and Monitor Scripts for pkg02 Failover Example Three Three-Server CascadingCascading Failover with Three Servers after One Server Fails VOLUMEGROUP/dev/nfsu01 VOLUMEGROUP/dev/nfsu02 Package Configuration File for pkg01 NFS Control Scripts for pkg01 NODENAMEthyme NODENAMEsage NODENAMEbasil IP0=15.13.114.244 SUBNET0=15.13.112.0 Example Four Two Servers with NFS Cross-Mounts Thyme Basil Cluster Configuration File for Two-Server NFS Cross-Mount NODENAMEthyme NODENAMEbasil NFS Control Scripts for pkg01 SNFS0=nfs1/hanfs/nfsu011 CNFS0=/nfs/nfsu011 NODENAMEbasil NODENAMEthyme NFS Control Scripts for pkg02 SNFS0=nfs2/hanfs/nfsu021 CNFS0=/nfs/nfsu021 Index Index Package configuration file nfs.conf default values
Related manuals
Manual 28 pages 17.67 Kb Manual 93 pages 21.07 Kb