Skip to content

Commit ecac063

Browse files
committed
SAP HANA standby with scale out on SLES - changes for NFS ID mapping
1 parent c1acc88 commit ecac063

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

articles/virtual-machines/workloads/sap/get-started.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.service: virtual-machines-linux
1515
ms.topic: article
1616
ms.tgt_pltfrm: vm-linux
1717
ms.workload: infrastructure-services
18-
ms.date: 11/12/2019
18+
ms.date: 11/21/2019
1919
ms.author: juergent
2020
ms.custom: H1Hack27Feb2017
2121

@@ -119,6 +119,7 @@ For information on integration of Azure services into SAP components, see:
119119

120120

121121
## Change Log
122+
- 11/21/2019: Changes in [SAP HANA scale-out with standby node on Azure VMs with Azure NetApp Files on SUSE Linux Enterprise Server](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse) to simplify the configuration for NFS ID mapping and change the recommended primary network interface to simplify routing.
122123
- 11/15/2019: Minor changes in [High availability for SAP NetWeaver on SUSE Linux Enterprise Server with Azure NetApp Files for SAP applications](high-availability-guide-suse-netapp-files.md) and [High availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](high-availability-guide-rhel-netapp-files.md) to clarify capacity pool size restrictions and remove statement that only NFSv3 version is supported.
123124
- 11/12/2019: Release of [High availability for SAP NetWeaver on Windows with Azure NetApp Files (SMB)](high-availability-guide-windows-netapp-files-smb.md)
124125
- 11/08/2019: Changes in [High availability of SAP HANA on Azure VMs on SUSE Linux Enterprise Server](sap-hana-high-availability.md), [Set up SAP HANA System Replication on Azure virtual machines (VMs)](sap-hana-high-availability-rhel.md), [Azure Virtual Machines high availability for SAP NetWeaver on SUSE Linux Enterprise Server for SAP applications](high-availability-guide-suse.md), [Azure Virtual Machines high availability for SAP NetWeaver on SUSE Linux Enterprise Server with Azure NetApp Files](high-availability-guide-suse-netapp-files.md), [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux](high-availability-guide-rhel.md), [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files](high-availability-guide-rhel-netapp-files.md), [High availability for NFS on Azure VMs on SUSE Linux Enterprise Server](high-availability-guide-suse-nfs.md), [GlusterFS on Azure VMs on Red Hat Enterprise Linux for SAP NetWeaver](high-availability-guide-rhel-glusterfs.md) to recommend Azure standard load balancer

articles/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.service: virtual-machines-windows
1515
ms.topic: article
1616
ms.tgt_pltfrm: vm-windows
1717
ms.workload: infrastructure-services
18-
ms.date: 11/20/2019
18+
ms.date: 11/21/2019
1919
ms.author: radeltch
2020

2121
---
@@ -403,7 +403,7 @@ Configure and prepare your OS by doing the following steps:
403403
3. **[A]** Verify the NFS domain setting. Make sure that the domain is configured as the default Azure NetApp Files domain, i.e. **`defaultv4iddomain.com`** and the mapping is set to **nobody**.
404404

405405
> [!IMPORTANT]
406-
> Make sure to set the NFS domain in `/etc/idmapd.conf' on the VM to match the default domain configuration on Azure NetApp Files: **`defaultv4iddomain.com`**. If there's a mismatch between the domain configuration on the NFS client (i.e. the VM) and the NFS server, i.e. the Azure NetApp configuration, then the permissions for files on Azure NetApp volumes that are mounted on the VMs will be displayed as `nobody`.
406+
> Make sure to set the NFS domain in `/etc/idmapd.conf` on the VM to match the default domain configuration on Azure NetApp Files: **`defaultv4iddomain.com`**. If there's a mismatch between the domain configuration on the NFS client (i.e. the VM) and the NFS server, i.e. the Azure NetApp configuration, then the permissions for files on Azure NetApp volumes that are mounted on the VMs will be displayed as `nobody`.
407407
408408
<pre><code>
409409
sudo cat /etc/idmapd.conf

0 commit comments

Comments
 (0)