Show Table of Contents
Chapter 4. An active/active Samba Server in a Red Hat High Availability Cluster (Red Hat Enterprise Linux 7.4 and Later)
As of the Red Hat Enterprise Linux 7.4 release, the Red Hat High Availability Add-On provides support for running Samba in an active/active cluster configuration using Pacemaker. This chapter describes how to configure a highly available active/active Samba server on a two-node Red Hat Enterprise Linux High Availability Add-On cluster using shared storage. The procedure uses
pcs to configure Pacemaker cluster resources.
This use case requires that your system include the following components:
- Two nodes, which will be used to create the cluster running Clustered Samba. In this example, the nodes used are
z1.example.comandz2.example.comwhich have IP address of192.168.1.151and192.168.1.152. - A power fencing device for each node of the cluster. This example uses two ports of the APC power switch with a host name of
zapc.example.com. - Shared storage for the nodes in the cluster, using iSCSI or Fibre Channel.
Configuring a highly available active/active Samba server on a two-node Red Hat Enterprise Linux High Availability Add-On cluster requires that you perform the following steps.
- Create the cluster that will export the Samba shares and configure fencing for each node in the cluster, as described in Section 4.1, “Creating the Cluster”.
- Configure a
gfs2file system mounted on the clustered LVM logical volumemy_clvon the shared storage for the nodes in the cluster, as described in Section 4.2, “Configuring a Clustered LVM Volume with a GFS2 File System”. - Configure Samba on each node in the cluster, Section 4.3, “Configuring Samba”.
- Create the Samba cluster resources as described in Section 4.4, “Configuring the Samba Cluster Resources”.
- Test the Samba share you have configured, as described in Section 4.5, “Testing the Resource Configuration”.
4.1. Creating the Cluster
Use the following procedure to install and create the cluster to use for the Samba service:
- Install the cluster software on nodes
z1.example.comandz2.example.com, using the procedure provided in Section 1.1, “Cluster Software Installation”. - Create the two-node cluster that consists of
z1.example.comandz2.example.com, using the procedure provided in Section 1.2, “Cluster Creation”. As in that example procedure, this use case names the clustermy_cluster. - Configure fencing devices for each node of the cluster, using the procedure provided in Section 1.3, “Fencing Configuration”. This example configures fencing using two ports of the APC power switch with a host name of
zapc.example.com.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.