Modifying the Samba Configuration File

When changes are required to a Samba configuration file that is used in a LifeKeeper Samba instance, perform these procedures on the server that is In Service, Protected (ISP). There are three types of configuration file changes:

• Those that do not directly impact the Samba hierarchy

• Those that directly impact the hierarchy but do not require a delete and recreation of hierarchy

• Those that directly impact the hierarchy and require a delete and recreation of the hierarchy

Modifications that do not directly impact the Samba Hierarchy

Any changes to configuration file directives not used by LifeKeeper fall into this category. (See Configuring the LifeKeeper for Linux Samba Recovery Kit for a list the directives used by the kit.) Example directives not used by LifeKeeper would include security, hosts allow, hosts deny and valid users to name a few. The procedures are as follows:

1. Take the Samba resource for the configuration file out of service. This step is required to stop the Samba daemons.

2. Make the necessary updates to the Samba configuration file.

3. Synchronize the configuration within the cluster. Use the utility synccfg to perform this task:

LKROOT/lkadm/subsys/gen/samba/bin/synccfg –t TargetSys –c ConfigFile

where LKROOT is the install location of LifeKeeper (/opt/LifeKeeper), TargetSy is the node to update and ConfigFile is the full path to the configuration file to copy.

4. Repeat the previous step for all servers in the hierarchy.

5. Bring the hierarchy back in service to restart the Samba daemons.

Modifications that directly impact the Samba Hierarchy

Any changes to configuration file directives used by LifeKeeper (see Configuring the LifeKeeper for Linux Samba Recovery Kit for a list), with the exception of the netbios name or the physical movement of the configuration file, fall into this category. Depending on the extent of the changes, it may be quicker and easier to proceed to the third category and just recreate the hierarchy. The typical types of changes expected in this category include the addition of new file and print shares, removal of file and print shares or the addition or removal of IP interfaces.

1. Take the Samba resource for the configuration file out of service. This step is required to stop the Samba daemons.

2. Make the necessary updates to the Samba configuration file.

3. Make the necessary updates to the Samba hierarchy. This varies depending on the type of change made to the configuration file. For example:

º If an additional IP address has been added to the interfaces directive, then a new IP resource needs to be created, extended and then added as a dependent child to the Samba resource hierarchy. See Creating a Resource Dependency in the LifeKeeper for Linux Technical Documentation for information on how to create dependencies.

º If a new file share has been added to the configuration file, then a File System resource may need to be created, extended and added as a dependent child to the Samba resource hierarchy. If the File System resource already exists as a child in the hierarchy (e.g. the path directive defined for the new share has the same file system mount point as another file or print share) then it does not need to be created and added as a dependent child.

º If a new print share is added, then File System and Print Services resources need to be created, extended and added as dependent children in the Samba hierarchy. If a print services resource does not exist that protects the printer as defined by the print share name or printer/printer name directive, then one must be created. See file share above to determine if a file system resource needs to be added.

º If a file or print share is removed, or if an IP address is removed from the interfaces directives, delete the dependency in the Samba hierarchy and then delete the individual resource.

º If a print share name is changed, follow the delete of print share followed by the addition of new print share.

4. Synchronize the configuration within the cluster. Use the utility synccfg to perform this task:

LKROOT/lkadm/subsys/gen/samba/bin/synccfg –t TargetSys –c ConfigFile

where LKROOT is the install location of LifeKeeper (/opt/LifeKeeper), TargetSys is the server to update and ConfigFile is the full path to the configuration file to copy.

5. Repeat the previous step for all servers in the hierarchy.

6. Bring the hierarchy back in service to restart the Samba daemons.

Note: If you are making a number of changes that require numerous resource creations and dependency additions or deletions, you may wish to create all the new resources before you take the Samba hierarchy out of service so that downtime is minimized.

Modifications that directly impact the Samba Hierarchy, requiring a deletion and recreation of the Hierarchy

If the netbios name directive is changed or the physical location of the configuration file is changed, then you must:

1. Delete the hierarchy. (See Deleting a Resource Hierarchy for details.)

2. Change the NetBIOS name or move the configuration file.

3. Create a new Samba hierarchy and extend to all backup servers.