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
Setting Up SAMBA Server Application for a SG/LX Cluster
Chapter 1 11
To configure a shared file systems, you need to create volume group(s)
and logical volume(s) on the shared disks and construct a new file system
for each logical volume for the SMB/CIFS file system (and SAMBA
configuration files).
The following is an example of configuring a shared storage for a SAMBA
package. The procedures below assume that you are configuring shared
file system /shared/smb_1 directory, which resides on a logical volume
"lvol1" from a shared volume group /dev/vg01.
1.Create a Volume Group vg01 for a shared storage.
2.Create a Logic Volume lvol1 for the vg01.
3.Make a directory /shared/smb1_1 on a local disk.
4.Mount device /dev/vg01/lovl1 to the "/shared/smb_1"
You can configure more shared storage for additional SAMBA instances
in the SG/LX cluster using the same method.
NOTE You need to create the volume groups on one node, and will require the
other node to reboot in order to for the other node to see the disk
partition. (Refer to document on Creating the Logical Volume
Infrastructure in the manual.)
Setting Up SAMBA Server Packages on a SG/LX
Cluster
The following procedures will show you the steps to configure a SG/LX
package running the SAMBA instance, which includes customizing the
SG/LX package configuration file, package control script. (Please refer to
the Getting Started with ServiceGuard for Linux manual for more
detailed instructions on setting up the SG/LX with packages, and for
instructions on how to start, halt, and move packages and their services
between nodes in a cluster.)
The procedures below assume that you are configuring a SG/LX SAMBA
package smb_pkg1, consisting of one service smb1_monitor. The
SAMBA instance is listening to a relocatable IP address 15.13.174.201
and its shared SMB/CIFS file systems are on the /shared/smb_1
directory, which resides on a logical volume "lvol1" from a shared volume
group /dev/vg01. Here, it is assumed that you have already determined