In addition to the installation requirements described in Section 3.1, Installation Requirements for Dynamic Storage Technology, consider the requirements in this section when setting up DST shadow volumes in a Novell Cluster Services cluster environment.
Ensure that each node in the cluster is running the same release version of OES 2 SP3 with the latest patches applied.
Ensure that each node is running the latest version of Novell Cluster Services with the latest patches applied.
When you use clustered DST volumes, special steps are needed when you upgrade the cluster from OES 2 SP3 to OES 11 SP1. For information, see OES 11 SP1: Dynamic Storage Technology Administration Guide.
The NCP (NetWare Core Protocol) Server and the Dynamic Storage Technology software are not cluster aware. They must be installed on every node in the cluster where you plan to migrate or fail over the cluster resource that contains shadow volumes. You do not cluster NCP Server or DST services. You can cluster the DST shadow volume pair as a cluster resource that manages the primary and secondary disks, pools, and volumes.
Dynamic Storage Technology supports shadow volumes created with pairs of shared Novell Storage Services (NSS) volumes. Install NSS on each node in the cluster. For information, see the OES 2 SP3: NSS File System Administration Guide for Linux.
You must create the two NSS pools and volumes on separate shared disks before you create the shadow volume relationship for the two volumes. The primary pool must be cluster-enabled. The secondary pool must be shared. You can cluster-enable the secondary pool, but its Cluster objects and IP address are not used while the two NSS volumes are in the shadow relationship.
When you use Novell Remote Manager for Linux to manage policies for the shadow volume, you typically connect to the IP address of the DST pair cluster resource. You can also connect to the IP address of the server node where the cluster resource is currently mounted.
NCP Server allows NCP users to access a merged view of the clustered shadow volume when the cluster resource is online. As with any clustered volume, the files are not available when the cluster resource is offline.
Novell CIFS supports Dynamic Storage Technology merged view of DST volume pairs comprised of two NSS volumes. CIFS users can access a merged view of the clustered DST volume pair when the cluster resource is online. As with any clustered volume, the files are not available when the cluster resource is offline
You must install and configure Novell CIFS on every node in the cluster where you plan to give users CIFS access to the shared cluster resource. For information, see OES 2 SP3: Novell CIFS for Linux Administration Guide.
You want Novell CIFS to be available on the node where the DST shadow volumes is active. To do this, you add Novell CIFS as an advertising protocol for the primary NSS pool resource as you cluster-enable it.
In the primary NSS pool cluster resource load script, the following command binds Novell CIFS to provide access to the shared resource through the virtual server IP address when the resource is mounted on a node.
novcifs --add --vserver=virtualserverFDN --ip-addr=virtualserverip
In the primary NSS pool cluster resource unload script, the following command unbinds Novell CIFS from the DST shadow volume cluster resource when the resource is failed over or cluster migrated to another node in the cluster.
novcifs --remove --vserver=virtualserverFDN --ip-addr=virtualserverip
In the primary NSS pool cluster resource monitor script, the following command checks the status and immediately invokes the resource’s failover settings if the cifsd daemon is not running.
exit_on_error rcnovell-cifs status
You can modify this line to use “monitor” instead of “status”. The CIFS monitor command helps to keep CIFS up and running. If the cifsd daemon is running, the monitor command returns its status. If the cifsd daemon is dead or not running, it starts the cifsd daemon and returns its status. If the restart fails, the resource’s failover settings are invoked, such as failing over the resource to its preferred node, or going comatose.
In addition, the following CIFS attributes are automatically added to the NCS:NCP Server object for the virtual server:
nfapCIFSServerName (read access)
nfapCIFSAttach (read access)
nfapCIFSComment (read access)
nfapCIFSShares (write access)
ShadowFS and FUSE (File System in Userspace) can be used with Novell Samba to allow SMB/CIFS users to access a merged view of the clustered DST shadow volume pair. Novell Samba is an alternative to Novell CIFS; they cannot be used together on the same server. You must install and configure Novell Samba and ShadowFS for each node in the cluster. For information about setting up SMB/CIFS access on each node, see Section 12.0, Using ShadowFS to Provide a Merged View for Novell Samba Users.
Additional commands for managing FUSE for the resource must be added manually in the cluster load/unload scripts of the primary pool cluster resource. You must also add the following lines in the load script of the primary NSS pool cluster resource to allow time for ShadowFS to start:
# If shadowfs is used, wait for shadowfs to start for (( c=1; c<=10; c++ )) do if [ ! -d /media/shadowfs/VOLUME/._NETWARE ]; then sleep 5; fi done
You must add the following line to the unload script of the primary NSS pool cluster resource to unload the volume in FUSE:
#unload the volume in FUSE ignore_error fusermount -u /media/shadowfs/VOLUME
Novell AFP does not support a merged view of files on the DST volume pair. AFP users see only the files on the primary volume. Do not give AFP users direct access to the secondary volume.