Samba Configuration Examples

This section contains definitions and examples of typical Samba configurations. Each example includes the configuration file entries that apply to LifeKeeper.

Configuration 1：Active/Standby Configuration

In the Active/Standby configuration, ServerA is the primary LifeKeeper server. It exports the file and print shares that reside on a shared storage device. While ServerB may be handling other applications/services, it acts only as a backup for the Samba resources in LifeKeeper’s context.

Configuration Notes:

• The clients connect to the Samba servers using the NetBIOS name LKServerA over the protected IP address (172.17.101.141), which is defined by the interfaces directive of the configuration file.

• The configuration file smb.conf has been copied to ServerB upon extension of the Samba resource hierarchy. It contains the following directives:

[global] netbios name = LKServerA bind interfaces only = yes

lock directory = /var/lock/samba interfaces = 172.17.101.141 127.0.0.1

log file = /var/log/sambaServA/log

[FShare-A]

path = /FShare-A

read only = no

public = yes

valid users =

printable = no

create mode = 0664

directory mode = 0775

[PRShare-A]

path = /PRShare-A

printer = publicprinter

printable = yes

browseable = no

• The Samba resource hierarchy would look like the following:

Configuration 2：Active/Active Configuration

In the Active/Active configuration below, both ServerA and ServerB are primary LifeKeeper servers for Samba resources. Each server is also the backup server for the other.

Configuration Notes:

• The clients connect to the Samba servers using the NetBIOS name LKServerA and LKServerB over the protected IP addresses (172.17.101.141 and 172.17.101.142 respectively), which are defined by the interfaces directive of the configuration files.

• The configuration file smb.conf was copied to ServerB upon extension of the Samba resource hierarchy. Likewise, the configuration file smb.conf-B was copied to ServerA upon extension of the Samba resource hierarchy.

• ServerA protects the file share /Fshare-A; ServerB protects the file share /Fshare-B.

• ServerA protects the print share /publicprinter; ServerB does not protect a print share.

• The two configuration files contain the following directives:

• The Samba resource hierarchies would look like the following: