Clustering setup and installation guide

System Setup and Configuration
Compaq Smart Array Cluster Storage Clustering Setup and Installation Guide 3-17
COMPAQ CONFIDENTIAL
Writer: John Turner File Name: d-ch3 system setup and configuration.doc
Codename: Voyager CL+ Part Number: 272402-001 Last Saved On: 1/3/02 10:59 AM
IMPORTANT: If you have a volume that is not being managed by Novell Cluster
Services, the volume must be mounted manually before you can access it. The MOUNT
ALL command in autoexec.ncf no longer mounts all NSS volumes by default. In the
autoexec.nfc file of the server where the volume is to be mounted, add separate MOUNT
commands followed by the volume name for each of the noncluster volumes that you want
to mount.
Cluster-Enabling Pools and Volumes
If you have a shared disk system that is part of your cluster and want the pools and
volumes on the shared disk system to be highly available to NetWare clients, you
must cluster-enable those pools and volumes. Cluster-enabling a pool or volume
allows it to be moved or mounted on different servers in the cluster in a manner that
supports transparent client reconnect.
With this release of Cluster Services, cluster-enabled volumes no longer appear as
cluster resources. NSS Pools are resources, and load and unload scripts apply to pools
and are automatically generated for them. Each cluster-enabled NSS pool requires its
own IP address. This means that each cluster-enabled volume does not have an
associated load and unload script or an assigned IP address.
The first volume you cluster-enable in the pool automatically cluster-enables the pool
where the volume resides. After a pool has been cluster-enabled, you must
cluster-enable the other volumes in the pool if you want them to be mounted on
another server during a failover.
When a server fails, any cluster-enabled pools being accessed by that server will fail
over to other servers in the cluster. Since the cluster-enabled pool fails over, all
volumes in the pool will also fail over, but only the volumes that have been cluster-
enabled will be mounted. Any volumes in the pool that have not been cluster-enabled
will have to be mounted manually. For this reason, volumes that are not
cluster-enabled should be in separate pools that are not cluster-enabled.
If you want each cluster-enabled volume to be its own cluster resource, each volume
must have its own pool.
Some server applications do not require NetWare client access to volumes, so cluster-
enabling pools and volumes might not be necessary. Pools must be deactivated and
volumes must be dismounted before being cluster-enabled.