While a Samba configuration file can contain many different directives, this description focuses on those aspects of the configuration file that affect your LifeKeeper configuration. Here are some key points about the configuration file:
- The configuration file is comprised of sections which correspond to the share (or service) they provide. Each section of the configuration file contains individual configuration options (or directives) unique to that share.
- The directives that are specified are sanity checked by the Samba Recovery Kit. Failure to set the directives properly will cause Samba resource creation to fail.
- The default configuration file for Samba is typically named smb.conf and resides in /etc or /etc/samba depending on the Linux distribution.
- Configuration file names must be unique within the cluster, or must reside in a different directory on each server for Active/Active configurations. The unique naming or location is required as the Samba Recovery Kit replicates a copy of the configuration file during extension to the same location on the backup server.
- Default set up can be used (and recommended) in the case to execute only one Samba daemon instance with active/standby set up. In this case, Samba daemon automatic startup must be disabled.
- If more than one version of Samba will be running in an Active/Standby configuration or if you use an Active/Active configuration, unique Samba configuration file names are required. See Running Multiple Instances of Samba for more requirements and information on running multiple versions of Samba.
The following sections of this document describe the sections of the configuration file, including the options required for LifeKeeper to protect a Samba share.