HP CIFS Server Administrator's Guide Version A.03.01.02 (5900-1766, September 2011)

3. Use the cmcheckconf command to verify the contents of your cluster and package
configuration. At this point it is assumed that you have created your MCServiceGuard cluster
configuration file (clucifs.conf) through MCServiceGuard procedures.
cmcheckconf -C /etc/cmcluster/clucifs.conf \
-P /etc/cmcluster/samba/pkg1/samba.conf \
-P /etc/cmcluster/samba/pkg2/samba.conf
4. Activate the shared volume for cluster locks.
vgchange —a y /dev/vglock
5. Use the cmapplyconf command to copy the binary configuration file to all the nodes in the
cluster.
cmapplyconf -v -C /etc/cmcluster/clucifs.conf \
-P /etc/cmcluster/samba/pkg1/samba.conf \
-P /etc/cmcluster/samba/pkg2/samba.conf
This command will distribute the updated cluster binary configuration file to all of the nodes
of the cluster.
You are ready to start the HA HP CIFS Server packages.
The configuration of the HA HP CIFS Server is now complete.
Special Notes for HA HP CIFS Server
There are several areas of concern when implementing Samba in the MC/ServiceGuard HA
framework. These areas are described below:
• Client Applications
HA HP CIFS Server cannot guarantee that client applications with open files on a HP CIFS
Server share, or, applications launched from HP CIFS Server shares, will transparently recover
from a switchover. In these instances there may be cases where the application will need to
be restarted and the files reopened as a switchover is a logical shutdown and restart of the
HP CIFS Server.
• File Locks
File locks are not preserved during failover. File locks are lost and applications are not advised
about any lost file locks.
• Print Jobs
If a failover occurs when a print job is in process, the job may be printed twice or not at all,
depending on the job state at the time of the failover.
• Symbolic Links
If you have your Samba server configured with follow symlinks set to yes and wide links set
to yes, the defaults for these parameters, you should be cautious.
Symbolic links in the shared directory trees may point to files outside any shared directory. If
the symbolic links point to files that are not in logical shared volumes, then, after a failover
occurs, the symbolic link may point to a different file or no file. Keeping the targets of all
shared symbolic links synchronized with all MC/ServiceGuard nodes at all times could be
difficult in this situation.
Easier options would be to set wide links to no or to be sure that every file or directory that
you point to is on a logical shared volume.
Special Notes for HA HP CIFS Server 145