Cluster Enable Pools And Volumes - Novell NETWARE 6-DOCUMENTATION Manual

Cluster Enable Pools and Volumes

Novell Cluster Services Overview and Installation
2 6
by default. In the AUTOEXEC.NCF 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 you want to mount.
Using NetWare Remote Manager
The same procedure for creating shared disk partitions using NetWare Remote
Manager is used to create cluster volumes. To create a cluster volume on
shared storage using NetWare Remote Manager go to
If you have a shared disk system that is part of your cluster and you want the
pools and volumes on the shared disk system to be highly available to
NetWare clients, you will need to 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. Once a pool has been cluster enabled, you
will need to 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. Because 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 aren't 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 don't require NetWare client access to volumes, so
cluster enabling pools and volumes might not be necessary. Pools should be
deactivated and volumes should be dismounted before being cluster enabled.
Step 1 on page 23.