Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00, June 2003

Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00
Chapter 14
Control Script created for each SAMBA sever package. This README
file assumes that the users have properly installed the SG/LX and
SAMBA Toolkit to all cluster nodes using RPM files.
SAMBA Server application has to be installed on all nodes that will run
the SAMBA packages in the SG/LX cluster. A typical configuration for an
SAMBA server application is configuring one node as a primary node
and the other nodes as standby nodes. The SAMBA Server application
runs on the primary node and it can accept SMB/CIFS requests from and
send responses to the clients. In the event of a failure on the primary
node, a standby node will take over control of SAMBA server functions.
This means that all necessary configuration information on each node
must be identical and the resources must be available to all supporting
nodes. The file systems exposing access to clients must be stored on
shared disks and these disks must be accessible by the same pathnames
on each node.
SAMBA server is a single daemon instance system when it runs on a
single node. (i.e. Only one smbd and nmbd is allowed to run on a server
machine.) This single daemon (smbd or nmbd) provides all services that
are defined in its configuration file.
Table 1-1 The Samba Toolkit Contains:
File Name Description
README This file
hasmb.conf User defined variables
for use to run high
availability Samba
package.
hasmb.sh The main shell script
hasmb.mon Monitoring the health
of the running Samba
Web Server.
toolkit.sh Interface between the
package control script
and the Samba.