How to Set Up HAStoragePlus Resource Type (5/02) (Sun Cluster 3.0 5/02 Supplement)

Sun Cluster 3.0 5/02 Supplement

How to Set Up HAStoragePlus Resource Type (5/02)

The following change was introduced in the Sun Cluster 3.0 5/02 update release and applies to this update and all subsequent updates to Sun Cluster 3.0 software.

The HAStoragePlus resource type was introduced in Sun Cluster 3.0 5/02. This new resource type performs the same functions as HAStorage, and synchronizes the startups between resource groups and disk device groups. The HAStoragePlus resource type has an additional feature to make a local file system highly available. (For background information on making a local file system highly available, see "Enabling Highly Available Local File Systems".) To use both of these features, set up the HAStoragePlus resource type.

To set up HAStoragePlus, the local file system partitions must reside on global disk groups with affinity switchovers enabled and the Sun Cluster environment must be configured for failover.

The following example uses a simple NFS service that shares out home directory data from a locally mounted directory /global/local-fs/nfs/export/home. The example assumes the following:

The mount point /global/local-fs/nfs will be used to mount a UFS local file system on a Sun Cluster global device partition.
The /etc/vfstab entry for the /global/local-fs/nfs file system should specify that it is a local file system and the mount boot flag is no.
The PathPrefix directory (the directory used by HA-NFS to maintain administrative and status information) is on the root directory of the same file system to be mounted (for example, /global/local-fs/nfs).

Become superuser on a cluster member.

Determine whether the resource type is registered.

The following command prints a list of registered resource types.
# scrgadm -p | egrep Type

If you need to, register the resource type.
# scrgadm -a -t SUNW.nfs

Create the failover resource group nfs-r

# scrgadm -a -g nfs-rg -y PathPrefix=/global/local-fs/nfs

Create a logical host resource of type SUNW.LogicalHostname.
# scrgadm -a -j nfs-lh-rs -g nfs-rg -L -l log-nfs

Create the resource nfs-hastp-rs of type SUNW.HAStoragePlus.

# scrgadm -a -j nfs-hastp-rs -g nfs-rg -t SUNW.HAStoragePlus \
-x FilesystemMountPoints=/global/local-fs/nfs \
-x AffinityOn=TRUE

Bring the resource group nfs-rg online on a cluster node.

This node will become the primary node for the /global/local-fs/nfs file system's underlying global device partition. The file system /global/local-fs/nfs will then be locally mounted on this node.
# scswitch -Z -g nfs-rg

Register the SUNW.NFS resource type with the cluster. Create the resource nfs-rs of type SUNW.nfs and specify its resource dependency on the resource nfs-hastp-rs.

dfstab.nfs-rs will be present in /global/local-fs/nfs/SUNW.nfs.
# scrgadm -a -t SUNW.nfs # scrgadm -a -g nfs-rg -j nfs-rs -t SUNW.nfs \ -y Resource_dependencies=nfs-hastp-rs
only -
The nfs-hastp-rs resource must be online before you can set the dependency in the nfs resource.

Bring the resource nfs-rs online.
# scswitch -Z -g nfs-rg

Now whenever the service is migrated to a new node, the primary I/O path for /global/local-fs/nfs will always be online and collocated with the NFS servers. The file system /global/local-fs/nfs will be locally mounted before starting the NFS server.