Skip to content

Commit a1d6309

Browse files
committed
minor changes
1 parent 2f6a90e commit a1d6309

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/sap/workloads/high-availability-guide-suse-netapp-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ During VM configuration, you have an option to create or select exiting load bal
169169

170170
The instructions in this section are only applicable, if using Azure NetApp Files volumes with NFSv4.1 protocol. Perform the configuration on all VMs, where Azure NetApp Files NFSv4.1 volumes will be mounted.
171171

172-
1. Verify the NFS domain setting. Make sure that the domain is configured as the default Azure NetApp Files domain, that is, **`defaultv4iddomain.com`** and the mapping is set to **nobody**.
172+
1. Verify the NFS domain setting. Make sure that the domain is configured as the default Azure NetApp Files domain that is, **`defaultv4iddomain.com`** and the mapping is set to **nobody**.
173173

174174
> [!IMPORTANT]
175175
> 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`.
@@ -246,7 +246,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
246246

247247
2. **[A]** Update SAP resource agents
248248

249-
A patch for the resource-agents package is required to use the new configuration, that is described in this article. You can check, if the patch is already installed with the following command
249+
A patch for the resource-agents package is required to use the new configuration that is described in this article. You can check, if the patch is already installed with the following command
250250

251251
```bash
252252
sudo grep 'parameter name="IS_ERS"' /usr/lib/ocf/resource.d/heartbeat/SAPInstance

articles/sap/workloads/high-availability-guide-suse-nfs-azure-files.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
225225

226226
2. **[A]** Update SAP resource agents
227227

228-
A patch for the resource-agents package is required to use the new configuration, that is described in this article. You can check, if the patch is already installed with the following command
228+
A patch for the resource-agents package is required to use the new configuration that is described in this article. You can check, if the patch is already installed with the following command
229229

230230
```bash
231231
sudo grep 'parameter name="IS_ERS"' /usr/lib/ocf/resource.d/heartbeat/SAPInstance
@@ -298,7 +298,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
298298
sudo chattr +i /usr/sap/NW1/ERS01
299299
```
300300

301-
2. **[A]** Mount the file systems, that will not be controlled by the Pacemaker cluster.
301+
2. **[A]** Mount the file systems that will not be controlled by the Pacemaker cluster.
302302

303303
```bash
304304
vi /etc/fstab

articles/sap/workloads/high-availability-guide-suse.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ The NFS server, SAP NetWeaver ASCS, SAP NetWeaver SCS, SAP NetWeaver ERS, and th
7979
## Setting up a highly available NFS server
8080

8181
> [!NOTE]
82-
> We recommend deploying one of the Azure first-party NFS services: [NFS on Azure Files](../../storage/files/storage-files-quick-create-use-linux.md) or [NFS ANF volumes](../../azure-netapp-files/azure-netapp-files-create-volumes.md) for storing shared data in a highly available SAP system. Be aware, that we are de-emphasizing SAP reference architectures, utilizing NFS clusters.
82+
> We recommend deploying one of the Azure first-party NFS services: [NFS on Azure Files](../../storage/files/storage-files-quick-create-use-linux.md) or [NFS ANF volumes](../../azure-netapp-files/azure-netapp-files-create-volumes.md) for storing shared data in a highly available SAP system. Be aware that we are de-emphasizing SAP reference architectures, utilizing NFS clusters.
8383
> The SAP configuration guides for SAP NW highly available SAP system with native NFS services are:
8484
>
8585
> * [High availability SAP NW on Azure VMswith simple mount and NFS on SLES for SAP Applications](./high-availability-guide-suse-nfs-simple-mount.md)
@@ -170,7 +170,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
170170

171171
1. **[A]** Update SAP resource agents
172172

173-
A patch for the resource-agents package is required to use the new configuration, that is described in this article. You can check, if the patch is already installed with the following command
173+
A patch for the resource-agents package is required to use the new configuration that is described in this article. You can check, if the patch is already installed with the following command
174174

175175
```bash
176176
sudo grep 'parameter name="IS_ERS"' /usr/lib/ocf/resource.d/heartbeat/SAPInstance

0 commit comments

Comments
 (0)