HP Serviceguard Toolkit for NFS manual SG NFS Servers over VxFS High Availability

Page 5

The files and filesystems can be shared and accessed concurrently within the cluster. However, file sharing and access from outside the cluster will still require NFS - client systems which are not members of the CFS cluster will use NFS to access the shared filesystems.

Cross mounting (with the nfs_xmnt script) is not needed since you can use CFS to share files and filesystems within the cluster.

Figures 2 and 3 also show how files and filesystems are accessed differently in a CFS environment versus a non-CFS environment. In a non-CFS environment, clients must access the server which exports a specific filesystem. In a CFS environment, clients can access the cluster via a load balancer or another mechanism such as a DNS round-robin scheme (represented by the cloud in Figure 3). Each NFS client can be directed to the server which currently has the most capacity available. This approach has a limitation that clients are bound to a particular NFS server when they issue the mount command.

Note: The implementation of a load balancer or DNS round-robin scheme is optional and is beyond the scope of this white paper. For more information about DNS round- robin addressing refer to the BIND Name Service Overview section in the HP-UX IP Address and Client Administrator’s Guide.

NFS

Client1

NFS

Client2

NFS

Client3

 

Serviceguard NFS servers

 

 

 

 

 

 

NFS Server1

 

NFS Server2

NFS Server3

/VxFS1

 

/VxFS2

/VxFS3

Shared Storage

/VxFS1/VxFS2/VxFS3

Figure 2. SG NFS Servers over VxFS – High Availability

5

Image 5
Contents Serviceguard NFS Toolkit Support for Cluster File System Starting a Serviceguard NFS failover package Non-CFS Implementation with Package Failover Integrating Support for CFS into Serviceguard NFS ToolkitCFS vs. Non-CFS Implementation Current SG-NFS over VxFS SupportSG NFS Servers over VxFS High Availability Issues and Limitations with the Current CFS Implementation Prerequisites Node Status State Cluster StatusMultinodepackages Package Status State Autorun SG-CFS-DG-1SG NFS over CFS without file locking Configuring a Serviceguard NFS export packageRunscripttimeout Notimeout # Failoverpolicy Configurednode # Failbackpolicy ManualPackagename SG-NFS-XP-1 Packagetype MultinodeHaltscripttimeout Notimeout Starting a Serviceguard NFS export packageSG-NFS-XP-1 Packagename SG-NFS1 Configuring a Serviceguard NFS failover packageDEPENDENCYCONDITIONSG-NFS-XP-1=UP Dependencylocationsamenode Starting a Serviceguard NFS failover packagePackage Status State Autorun Node SG-NFS2 Package Status State Autorun Node SG-NFS1SG NFS over CFS with file locking NFSFILELOCKMIGRATION=1 Nfs2.conf file set these variables to Starting a Serviceguard NFS failover package Cluster1 up XFS Starting a Serviceguard NFS export package Configuring a Serviceguard NFS failover package Starting a Serviceguard NFS failover package Package Status State Autorun Node SG-NFS1 FILELOCKMIGRATION1 Starting a Serviceguard NFS failover package Thyme Running
Related manuals
Manual 93 pages 19.37 Kb Manual 93 pages 21.07 Kb