Using SAMBA Toolkit in a Serviceguard Cluster README Revision: B.06.00

$ cd /etc/cmcluster/pkg/SMB_1/
$ $PWD/toolkit.sh stop
- Perform maintenance actions (Example: changing the configuration
parameters. If files are changed, please remember to distribute the
new file to all cluster nodes as needed).
- Start the CIFS Server instance again if you stopped it as below:
$ cd /etc/cmcluster/pkg/SMB_1/
$ $PWD/toolkit.sh start
- Allow monitoring scripts to continue normally as shown below:
$ rm -f /etc/cmcluster/pkg/SMB_1/samba.debug
A message "Starting Samba toolkit monitoring again after
maintenance" appears in the Serviceguard Package Control script
log.
- Enable the package failover
$ cmmodpkg -e SMB_1
Note: If the package fails during maintenance (example, the node
crashes), the package will not automatically fail over to an
adoptive node. It is the responsibility of the user to start
the package up on an adoptive node. Please refer to the
manual "Managing Serviceguard" for more details.
Note: This feature is enabled only when the configuration variable
MAINTENANCE_FLAG is set to "yes" in the Samba toolkit
configuration file.
F. Special Notes
Please consider the following areas when implementing HP CIFS Server in
the Serviceguard HA framework.
* Client Applications
HA CIFS Server server cannot guarantee that client applications with
open files on a CIFS Server share, or, applications launched from 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 CIFS Server.
* File Locks
File locks are not preserved during failover, and applications are not
advised about any lost file locks.