Merge pull request #312498 from Xelu86/hagluster

JamesJBarnett · web-flow · commit eda4b98d45d3 · 2026-03-02T15:34:06.000-07:00
[Update] GlusterFS on Azure VMs on Red Hat Enterprise Linux for SAP NetWeaver
diff --git a/articles/sap/workloads/high-availability-guide-rhel-glusterfs.md b/articles/sap/workloads/high-availability-guide-rhel-glusterfs.md
@@ -1,14 +1,14 @@
 ---
-title: GlusterFS on Azure VMs on RHEL for SAP NetWeaver | Microsoft Docs
-description: GlusterFS on Azure VMs on Red Hat Enterprise Linux for SAP NetWeaver
+title: GlusterFS on Azure VMs on RHEL for SAP NetWeaver
+description: Learn about deploying GlusterFS on Azure VMs on Red Hat Enterprise Linux for SAP NetWeaver.
 services: virtual-machines-windows,virtual-network,storage
-author: rdeltcheva
-manager: juergent
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
-ms.topic: article
-ms.date: 07/03/2023
+ms.topic: how-to
+manager: juergent
+author: rdeltcheva
 ms.author: radeltch
+ms.date: 03/02/2026
 ms.custom:
   - linux-related-content
   - sfi-image-nochange
@@ -17,43 +17,25 @@ ms.custom:
 
 # GlusterFS on Azure VMs on Red Hat Enterprise Linux for SAP NetWeaver
 
-[dbms-guide]:dbms-guide-general.md
-[deployment-guide]:deployment-guide.md
-[planning-guide]:planning-guide.md
+This article describes how to deploy the virtual machines (VMs), configure the VMs, and install a GlusterFS cluster. The GlusterFS cluster is used to store the shared data of a highly available SAP system. This guide describes how to set up GlusterFS that is used by two SAP systems, NW1 and NW2. The names of the resources (for example VMs, virtual networks) in the example, assumes that you used the [SAP file server template][template-file-server] with resource prefix `glust`.
 
-[2002167]:https://launchpad.support.sap.com/#/notes/2002167
-[2009879]:https://launchpad.support.sap.com/#/notes/2009879
-[1928533]:https://launchpad.support.sap.com/#/notes/1928533
-[2015553]:https://launchpad.support.sap.com/#/notes/2015553
-[2178632]:https://launchpad.support.sap.com/#/notes/2178632
-[2191498]:https://launchpad.support.sap.com/#/notes/2191498
-[2243692]:https://launchpad.support.sap.com/#/notes/2243692
-[1999351]:https://launchpad.support.sap.com/#/notes/1999351
+As documented in [Red Hat Gluster Storage Life Cycle](https://access.redhat.com/support/policy/updates/rhs), Red Hat Gluster Storage reaches end of life at the end of 2024. The configuration is supported for SAP on Azure until it reaches end of life stage. GlusterFS shouldn't be used for new deployments. We recommend deploying the SAP shared directories on an NFS on Azure Files, or Azure NetApp Files volumes as documented in [HA for SAP NW on RHEL with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md). See also [HA for SAP NW on RHEL with Azure NetApp Files](./high-availability-guide-rhel-netapp-files.md).
 
-[template-file-server]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fapplication-workloads%2Fsap%2Fsap-file-server-md%2Fazuredeploy.json
-
-[sap-hana-ha]:sap-hana-high-availability-rhel.md
-
-This article describes how to deploy the virtual machines, configure the virtual machines, and install a GlusterFS cluster that can be used to store the shared data of a highly available SAP system.
-This guide describes how to set up GlusterFS that is used by two SAP systems, NW1 and NW2. The names of the resources (for example virtual machines, virtual networks) in the example assume that you have used the [SAP file server template][template-file-server] with resource prefix **glust**.
-
-Be aware that as documented in [Red Hat Gluster Storage Life Cycle](https://access.redhat.com/support/policy/updates/rhs) Red Hat Gluster Storage will reach end of life at the end of 2024. The configuration will be supported for SAP on Azure until it reaches end of life stage. GlusterFS should not be used for new deployments. We recommend to deploy the SAP shared directories on NFS on Azure Files or Azure NetApp Files volumes as documented in [HA for SAP NW on RHEL with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md) or [HA for SAP NW on RHEL with Azure NetApp Files](./high-availability-guide-rhel-netapp-files.md).  
-
-Read the following SAP Notes and papers first
+Read the following SAP Notes and papers first:
 
 * SAP Note [1928533], which has:
   * List of Azure VM sizes that are supported for the deployment of SAP software
   * Important capacity information for Azure VM sizes
   * Supported SAP software, and operating system (OS) and database combinations
   * Required SAP kernel version for Windows and Linux on Microsoft Azure
 
-* SAP Note [2015553] lists prerequisites for SAP-supported SAP software deployments in Azure.
-* SAP Note [2002167] has recommended OS settings for Red Hat Enterprise Linux
+* SAP Note [2015553] has prerequisites for SAP-supported SAP software deployments in Azure.
+* SAP Note [2002167] has the recommended OS settings for Red Hat Enterprise Linux
 * SAP Note [2009879] has SAP HANA Guidelines for Red Hat Enterprise Linux
 * SAP Note [2178632] has detailed information about all monitoring metrics reported for SAP in Azure.
 * SAP Note [2191498] has the required SAP Host Agent version for Linux in Azure.
 * SAP Note [2243692] has information about SAP licensing on Linux in Azure.
-* SAP Note [1999351] has additional troubleshooting information for the Azure Enhanced Monitoring Extension for SAP.
+* SAP Note [1999351] has extra troubleshooting information for the Azure Enhanced Monitoring Extension for SAP.
 * [SAP Community WIKI](https://wiki.scn.sap.com/wiki/display/HOME/SAPonLinuxNotes) has all required SAP Notes for Linux.
 * [Azure Virtual Machines planning and implementation for SAP on Linux][planning-guide]
 * [Azure Virtual Machines deployment for SAP on Linux (this article)][deployment-guide]
@@ -70,36 +52,36 @@ Read the following SAP Notes and papers first
 
 ## Overview
 
-To achieve high availability, SAP NetWeaver requires shared storage. GlusterFS is configured in a separate cluster and can be used by multiple SAP systems.  
+To achieve high availability, SAP NetWeaver requires shared storage. GlusterFS runs in a separate cluster and supports access by multiple SAP systems.
 
-![SAP NetWeaver High Availability overview](./media/high-availability-guide-rhel-glusterfs/rhel-glusterfs.png)
+![A diagram of a GlusterFS shared storage with 3 nodes configured for high availability for SAP NetWeaver.](./media/high-availability-guide-rhel-glusterfs/rhel-glusterfs.png)
 
-## Set up GlusterFS
+## Prerequisites
 
 In this example, the resources were deployed manually via the [Azure portal](https://portal.azure.com/#home).
 
-### Deploy Linux manually via Azure portal
+This document assumes that you deployed:
 
-This document assumes that you've already deployed a resource group, [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md), and subnet.
+* A resource group previously.
+* An [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md) and subnet.
 
-Deploy virtual machines for GlusterFS. Choose a suitable RHEL image that is supported for Gluster storage. You can deploy VM in any one of the availability options - scale set, availability zone or availability set.
+When you deploy VMs for GlusterFS, choose a suitable RHEL image that supports Gluster storage. You can deploy VM in any one of the availability options - scale set, availability zone, or availability set.
 
 ### Configure GlusterFS
 
 The following items are prefixed with either **[A]** - applicable to all nodes, **[1]** - only applicable to node 1, **[2]** - only applicable to node 2, **[3]** - only applicable to node 3.
 
 1. **[A]** Setup host name resolution
 
-   You can either use a DNS server or modify the /etc/hosts on all nodes. This example shows how to use the /etc/hosts file.
-   Replace the IP address and the hostname in the following commands
+   You can either use a DNS server or modify the `/etc/hosts` on all nodes. This example shows how to use the `/etc/hosts` file. Replace the IP address and the hostname in the following commands:
 
    ```bash
    sudo vi /etc/hosts
    ```
 
-   Insert the following lines to /etc/hosts. Change the IP address and hostname to match your environment
+   Insert the following lines to `/etc/hosts`. Change the IP address and hostname to match your environment:
 
-   ```text
+   ```
    # IP addresses of the Gluster nodes
    10.0.0.40 glust-0
    10.0.0.41 glust-1
@@ -108,7 +90,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Register
 
-   Register your virtual machines and attach it to a pool that contains repositories for RHEL 7 and GlusterFS
+   Register your VMs and attach it to a pool that contains repositories for RHEL 7 and GlusterFS:
 
    ```bash
    sudo subscription-manager register
@@ -117,39 +99,39 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Enable GlusterFS repos
 
-   In order to install the required packages, enable the following repositories.
+   In order to install the required packages, enable the following repositories:
 
    ```bash
    sudo subscription-manager repos --disable "*"
    sudo subscription-manager repos --enable=rhel-7-server-rpms
    sudo subscription-manager repos --enable=rh-gluster-3-for-rhel-7-server-rpms
    ```
-  
+
 1. **[A]** Install GlusterFS packages
 
-   Install these packages on all GlusterFS nodes
+   Install these packages on all GlusterFS nodes:
 
    ```bash
    sudo yum -y install redhat-storage-server
    ```
 
    Reboot the nodes after the installation.
 
-1. **[A]** Modify Firewall
+1. **[A]** Modify firewall
 
-   Add firewall rules to allow client traffic to the GlusterFS nodes.
+   Add firewall rules to allow client traffic to the GlusterFS nodes:
 
    ```bash
    # list the available zones
    firewall-cmd --get-active-zones
-   
+
    sudo firewall-cmd --zone=public --add-service=glusterfs --permanent
    sudo firewall-cmd --zone=public --add-service=glusterfs
    ```
 
 1. **[A]** Enable and start GlusterFS service
 
-   Start the GlusterFS service on all nodes.
+   Start the GlusterFS service on all nodes:
 
    ```bash
    sudo systemctl start glusterd
@@ -158,32 +140,40 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[1]** Create GluserFS
 
-   Run the following commands to create the GlusterFS cluster
+   Create the GlusterFS cluster by running the following commands:
 
    ```bash
    sudo gluster peer probe glust-1
    sudo gluster peer probe glust-2
-   
-   # Check gluster peer status
+   ```
+
+   Check the GlusterFS peer status:
+
+   ```bash
    sudo gluster peer status
-   
+   ```
+
+   ```output
    # Number of Peers: 2
-   # 
+   #
    # Hostname: glust-1
    # Uuid: 10d43840-fee4-4120-bf5a-de9c393964cd
    # State: Accepted peer request (Connected)
-   # 
+   #
    # Hostname: glust-2
    # Uuid: 9e340385-12fe-495e-ab0f-4f851b588cba
    # State: Accepted peer request (Connected)
    ```
 
 1. **[2]** Test peer status
 
-   Test the peer status on the second node
+   Test the peer status on the second node:
 
    ```bash
    sudo gluster peer status
+   ```
+
+   ```output
    # Number of Peers: 2
    #
    # Hostname: glust-0
@@ -197,10 +187,13 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[3]** Test peer status
 
-   Test the peer status on the third node
+   Test the peer status on the third node:
 
    ```bash
    sudo gluster peer status
+   ```
+
+   ```output
    # Number of Peers: 2
    #
    # Hostname: glust-0
@@ -214,9 +207,9 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Create LVM
 
-   In this example, the GlusterFS is used for two SAP systems, NW1 and NW2. Use the following commands to create LVM configurations for these SAP systems.
+   In this example, the GlusterFS is used for two SAP systems, **NW1** and **NW2**. Use the following commands to create LVM configurations for these SAP systems.
 
-   Use these commands for NW1
+   Use these commands for **NW1**:
 
    ```bash
    sudo pvcreate --dataalignment 1024K /dev/disk/azure/scsi1/lun0
@@ -229,35 +222,35 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo lvcreate -l 50%FREE -n rhgs-NW1/ascs
    sudo lvcreate -l 100%FREE -n rhgs-NW1/aers
    sudo lvscan
-   
+
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW1/sapmnt
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW1/trans
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW1/sys
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW1/ascs
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW1/aers
-   
+
    sudo mkdir -p /rhs/NW1/sapmnt
    sudo mkdir -p /rhs/NW1/trans
    sudo mkdir -p /rhs/NW1/sys
    sudo mkdir -p /rhs/NW1/ascs
    sudo mkdir -p /rhs/NW1/aers
-   
+
    sudo chattr +i /rhs/NW1/sapmnt
    sudo chattr +i /rhs/NW1/trans
    sudo chattr +i /rhs/NW1/sys
    sudo chattr +i /rhs/NW1/ascs
    sudo chattr +i /rhs/NW1/aers
-   
+
    echo -e "/dev/rhgs-NW1/sapmnt\t/rhs/NW1/sapmnt\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW1/trans\t/rhs/NW1/trans\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW1/sys\t/rhs/NW1/sys\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW1/ascs\t/rhs/NW1/ascs\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW1/aers\t/rhs/NW1/aers\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
-   
+
    sudo mount -a
    ```
 
-   Use these commands for NW2
+   Use these commands for **NW2**:
 
    ```bash
    sudo pvcreate --dataalignment 1024K /dev/disk/azure/scsi1/lun1
@@ -269,62 +262,62 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    sudo lvcreate -l 10%FREE -n rhgs-NW2/sys
    sudo lvcreate -l 50%FREE -n rhgs-NW2/ascs
    sudo lvcreate -l 100%FREE -n rhgs-NW2/aers
-   
+
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW2/sapmnt
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW2/trans
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW2/sys
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW2/ascs
    sudo mkfs.xfs -f -K -i size=512 -n size=8192 /dev/rhgs-NW2/aers
-   
+
    sudo mkdir -p /rhs/NW2/sapmnt
    sudo mkdir -p /rhs/NW2/trans
    sudo mkdir -p /rhs/NW2/sys
    sudo mkdir -p /rhs/NW2/ascs
    sudo mkdir -p /rhs/NW2/aers
-   
+
    sudo chattr +i /rhs/NW2/sapmnt
    sudo chattr +i /rhs/NW2/trans
    sudo chattr +i /rhs/NW2/sys
    sudo chattr +i /rhs/NW2/ascs
    sudo chattr +i /rhs/NW2/aers
    sudo lvscan
-   
+
    echo -e "/dev/rhgs-NW2/sapmnt\t/rhs/NW2/sapmnt\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW2/trans\t/rhs/NW2/trans\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW2/sys\t/rhs/NW2/sys\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW2/ascs\t/rhs/NW2/ascs\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
    echo -e "/dev/rhgs-NW2/aers\t/rhs/NW2/aers\txfs\tdefaults,inode64,nobarrier,noatime,nouuid 0 2" | sudo tee -a /etc/fstab
-   
+
    sudo mount -a
    ```
 
 1. **[1]** Create the distributed volume
 
-   Use the following commands to create the GlusterFS volume for NW1 and start it.
+   Use the following commands to create the GlusterFS volume for **NW1** and start it:
 
    ```bash
    sudo gluster vol create NW1-sapmnt replica 3 glust-0:/rhs/NW1/sapmnt glust-1:/rhs/NW1/sapmnt glust-2:/rhs/NW1/sapmnt force
    sudo gluster vol create NW1-trans replica 3 glust-0:/rhs/NW1/trans glust-1:/rhs/NW1/trans glust-2:/rhs/NW1/trans force
    sudo gluster vol create NW1-sys replica 3 glust-0:/rhs/NW1/sys glust-1:/rhs/NW1/sys glust-2:/rhs/NW1/sys force
    sudo gluster vol create NW1-ascs replica 3 glust-0:/rhs/NW1/ascs glust-1:/rhs/NW1/ascs glust-2:/rhs/NW1/ascs force
    sudo gluster vol create NW1-aers replica 3 glust-0:/rhs/NW1/aers glust-1:/rhs/NW1/aers glust-2:/rhs/NW1/aers force
-   
+
    sudo gluster volume start NW1-sapmnt
    sudo gluster volume start NW1-trans
    sudo gluster volume start NW1-sys
    sudo gluster volume start NW1-ascs
    sudo gluster volume start NW1-aers
    ```
 
-   Use the following commands to create the GlusterFS volume for NW2 and start it.
+   Use the following commands to create the GlusterFS volume for **NW2** and start it:
 
    ```bash
    sudo gluster vol create NW2-sapmnt replica 3 glust-0:/rhs/NW2/sapmnt glust-1:/rhs/NW2/sapmnt glust-2:/rhs/NW2/sapmnt force
    sudo gluster vol create NW2-trans replica 3 glust-0:/rhs/NW2/trans glust-1:/rhs/NW2/trans glust-2:/rhs/NW2/trans force
    sudo gluster vol create NW2-sys replica 3 glust-0:/rhs/NW2/sys glust-1:/rhs/NW2/sys glust-2:/rhs/NW2/sys force
    sudo gluster vol create NW2-ascs replica 3 glust-0:/rhs/NW2/ascs glust-1:/rhs/NW2/ascs glust-2:/rhs/NW2/ascs force
    sudo gluster vol create NW2-aers replica 3 glust-0:/rhs/NW2/aers glust-1:/rhs/NW2/aers glust-2:/rhs/NW2/aers force
-   
+
    sudo gluster volume start NW2-sapmnt
    sudo gluster volume start NW2-trans
    sudo gluster volume start NW2-sys
@@ -340,3 +333,20 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 * [Azure Virtual Machines DBMS deployment for SAP][dbms-guide]
 * To learn how to establish high availability and plan for disaster recovery of SAP HANA on Azure (large instances), see [SAP HANA (large instances) high availability and disaster recovery on Azure](/azure/virtual-machines/workloads/sap/hana-overview-high-availability-disaster-recovery).
 * To learn how to establish high availability and plan for disaster recovery of SAP HANA on Azure VMs, see [High Availability of SAP HANA on Azure Virtual Machines (VMs)][sap-hana-ha]
+
+[dbms-guide]:dbms-guide-general.md
+[deployment-guide]:deployment-guide.md
+[planning-guide]:planning-guide.md
+
+[2002167]:https://launchpad.support.sap.com/#/notes/2002167
+[2009879]:https://launchpad.support.sap.com/#/notes/2009879
+[1928533]:https://launchpad.support.sap.com/#/notes/1928533
+[2015553]:https://launchpad.support.sap.com/#/notes/2015553
+[2178632]:https://launchpad.support.sap.com/#/notes/2178632
+[2191498]:https://launchpad.support.sap.com/#/notes/2191498
+[2243692]:https://launchpad.support.sap.com/#/notes/2243692
+[1999351]:https://launchpad.support.sap.com/#/notes/1999351
+
+[template-file-server]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fapplication-workloads%2Fsap%2Fsap-file-server-md%2Fazuredeploy.json
+
+[sap-hana-ha]:sap-hana-high-availability-rhel.md
