Skip to content

Commit 90c8315

Browse files
authored
Merge pull request #106255 from rdeltcheva/anf-sles-vol
update SAP ASCS with ANF on SUSE HA documentation with more efficient…
2 parents 71d6c09 + 67e083c commit 90c8315

File tree

3 files changed

+51
-27
lines changed

3 files changed

+51
-27
lines changed

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

Lines changed: 51 additions & 27 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: 02/27/2020
18+
ms.date: 03/02/2020
1919
ms.author: radeltch
2020

2121
---
@@ -93,7 +93,7 @@ To achieve that on SUSE Linux so far it was necessary to build separate highly a
9393
Now it is possible to achieve SAP Netweaver HA by using shared storage, deployed on Azure NetApp Files. Using Azure NetApp Files for the shared storage eliminates the need for additional [NFS cluster](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-nfs). Pacemaker is still needed for HA of the SAP Netweaver central services(ASCS/SCS).
9494

9595

96-
![SAP NetWeaver High Availability overview](./media/high-availability-guide-suse-anf/high-availability-guide-suse-anf.PNG)
96+
![SAP NetWeaver High Availability overview](./media/high-availability-guide-suse-anf/high-availability-guide-suse-anf.png)
9797

9898
SAP NetWeaver ASCS, SAP NetWeaver SCS, SAP NetWeaver ERS, and the SAP HANA database use virtual hostname and virtual IP addresses. On Azure, a [load balancer](https://docs.microsoft.com/azure/load-balancer/load-balancer-overview) is required to use a virtual IP address. We recommend using [Standard load balancer](https://docs.microsoft.com/azure/load-balancer/quickstart-load-balancer-standard-public-portal). The following list shows the configuration of the (A)SCS and ERS load balancer.
9999

@@ -138,7 +138,7 @@ SAP NetWeaver ASCS, SAP NetWeaver SCS, SAP NetWeaver ERS, and the SAP HANA datab
138138
SAP NetWeaver requires shared storage for the transport and profile directory. Before proceeding with the setup for Azure NetApp files infrastructure, familiarize yourself with the [Azure NetApp Files documentation][anf-azure-doc].
139139
Check if your selected Azure region offers Azure NetApp Files. The following link shows the availability of Azure NetApp Files by Azure region: [Azure NetApp Files Availability by Azure Region][anf-avail-matrix].
140140

141-
Azure NetApp files is available in several [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=netapp). Before deploying Azure NetApp Files, request onboarding to Azure NetApp Files , following the [Register for Azure NetApp files instructions][anf-register].
141+
Azure NetApp files is available in several [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=netapp). Before deploying Azure NetApp Files, request onboarding to Azure NetApp Files, following the [Register for Azure NetApp files instructions][anf-register].
142142

143143
### Deploy Azure NetApp Files resources
144144

@@ -152,15 +152,16 @@ The SAP Netweaver architecture presented in this article uses single Azure NetAp
152152

153153
4. Delegate a subnet to Azure NetApp files as described in the [instructions Delegate a subnet to Azure NetApp Files](https://docs.microsoft.com/azure/azure-netapp-files/azure-netapp-files-delegate-subnet).
154154

155-
5. Deploy Azure NetApp Files volumes, following the [instructions to create a volume for Azure NetApp Files](https://docs.microsoft.com/azure/azure-netapp-files/azure-netapp-files-create-volumes). Deploy the volumes in the designated Azure NetApp Files [subnet](https://docs.microsoft.com/rest/api/virtualnetwork/subnets). Keep in mind that the Azure NetApp Files resources and the Azure VMs must be in the same Azure Virtual Network or in peered Azure Virtual Networks. For example sapmnt<b>QAS</b>, usrsap<b>QAS</b>, etc. are the volume names and sapmnt<b>qas</b>, usrsap<b>qas</b>, etc. are the filepaths for the Azure NetApp Files volumes.
155+
5. Deploy Azure NetApp Files volumes, following the [instructions to create a volume for Azure NetApp Files](https://docs.microsoft.com/azure/azure-netapp-files/azure-netapp-files-create-volumes). Deploy the volumes in the designated Azure NetApp Files [subnet](https://docs.microsoft.com/rest/api/virtualnetwork/subnets). Keep in mind that the Azure NetApp Files resources and the Azure VMs must be in the same Azure Virtual Network or in peered Azure Virtual Networks. In this example we use two Azure NetApp Files volumes: sap<b>QAS</b> and trans. The file paths that are mounted to the corresponding mount points are /usrsap<b>qas</b>/sapmnt<b>QAS</b>, /usrsap<b>qas</b>/usrsap<b>QAS</b>sys, etc.
156156

157-
1. volume sapmnt<b>QAS</b> (nfs://10.1.0.4/sapmnt<b>qas</b>)
158-
2. volume usrsap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>)
159-
3. volume usrsap<b>QAS</b>sys (nfs://10.1.0.5/usrsap<b>qas</b>sys)
160-
4. volume usrsap<b>QAS</b>ers (nfs://10.1.0.4/usrsap<b>qas</b>ers)
157+
1. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/sapmnt<b>QAS</b>)
158+
2. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>ascs)
159+
3. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>sys)
160+
4. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>ers)
161161
5. volume trans (nfs://10.1.0.4/trans)
162-
6. volume usrsap<b>QAS</b>pas (nfs://10.1.0.5/usrsap<b>qas</b>pas)
163-
7. volume usrsap<b>QAS</b>aas (nfs://10.1.0.4/usrsap<b>qas</b>aas)
162+
6. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>pas)
163+
7. volume sap<b>QAS</b> (nfs://10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>aas)
164+
164165

165166
In this example, we used Azure NetApp Files for all SAP Netweaver file systems to demonstrate how Azure NetApp Files can be used. The SAP file systems that don't need to be mounted via NFS can also be deployed as [Azure disk storage](https://docs.microsoft.com/azure/virtual-machines/windows/disks-types#premium-ssd) . In this example <b>a-e</b> must be on Azure NetApp Files and <b>f-g</b> (that is, /usr/sap/<b>QAS</b>/D<b>02</b>, /usr/sap/<b>QAS</b>/D<b>03</b>) could be deployed as Azure disk storage.
166167

@@ -399,6 +400,30 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
399400
<b>10.1.1.21 anftstsapers</b>
400401
</code></pre>
401402

403+
4. **[1]** Create SAP directories in the Azure NetApp Files volume.
404+
Mount temporarily the Azure NetApp Files volume on one of the VMs and create the SAP directories(file paths).
405+
406+
```
407+
# mount temporarily the volume
408+
sudo mkdir -p /saptmp
409+
# If using NFSv3
410+
sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=3,tcp 10.1.0.4:/sapQAS /saptmp
411+
# If using NFSv4.1
412+
sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,sec=sys,tcp 10.1.0.4:/sapQAS /saptmp
413+
# create the SAP directories
414+
sudo cd /saptmp
415+
sudo mkdir -p sapmntQAS
416+
sudo mkdir -p usrsapQASascs
417+
sudo mkdir -p usrsapQASers
418+
sudo mkdir -p usrsapQASsys
419+
sudo mkdir -p usrsapQASpas
420+
sudo mkdir -p usrsapQASaas
421+
# unmount the volume and delete the temporary directory
422+
sudo cd ..
423+
sudo umount /saptmp
424+
sudo rmdir /saptmp
425+
```
426+
402427
## Prepare for SAP NetWeaver installation
403428
404429
1. **[A]** Create the shared directories
@@ -429,19 +454,19 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
429454
<pre><code>
430455
sudo vi /etc/auto.direct
431456
# Add the following lines to the file, save and exit
432-
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync 10.1.0.4:/sapmnt<b>qas</b>
457+
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync 10.1.0.4/usrsap<b>qas</b>/sapmnt<b>QAS</b>
433458
/usr/sap/trans -nfsvers=3,nobind,sync 10.1.0.4:/trans
434-
/usr/sap/<b>QAS</b>/SYS -nfsvers=3,nobind,sync 10.1.0.5:/usrsap<b>qas</b>sys
459+
/usr/sap/<b>QAS</b>/SYS -nfsvers=3,nobind,sync 10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>sys
435460
</code></pre>
436461
437462
If using NFSv4.1, create a file with:
438463
439464
<pre><code>
440465
sudo vi /etc/auto.direct
441466
# Add the following lines to the file, save and exit
442-
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys 10.1.0.4:/sapmnt<b>qas</b>
467+
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys 10.1.0.4/usrsap<b>qas</b>/sapmnt<b>QAS</b>
443468
/usr/sap/trans -nfsvers=4.1,nobind,sync,sec=sys 10.1.0.4:/trans
444-
/usr/sap/<b>QAS</b>/SYS -nfsvers=4.1,nobind,sync,sec=sys 10.1.0.5:/usrsap<b>qas</b>sys
469+
/usr/sap/<b>QAS</b>/SYS -nfsvers=4.1,nobind,sync,sec=sys 10.1.0.4/usrsap<b>qas</b>/usrsap<b>QAS</b>sys
445470
</code></pre>
446471
447472
> [!NOTE]
@@ -482,13 +507,13 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
482507
483508
<pre><code>sudo crm node standby <b>anftstsapcl2</b>
484509
# If using NFSv3
485-
sudo crm configure primitive fs_<b>QAS</b>_ASCS Filesystem device='<b>10.1.0.4</b>:/usrsap<b>qas</b>' directory='/usr/sap/<b>QAS</b>/ASCS<b>00</b>' fstype='nfs' \
510+
sudo crm configure primitive fs_<b>QAS</b>_ASCS Filesystem device='<b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>ascs' directory='/usr/sap/<b>QAS</b>/ASCS<b>00</b>' fstype='nfs' \
486511
op start timeout=60s interval=0 \
487512
op stop timeout=60s interval=0 \
488513
op monitor interval=20s timeout=40s
489514
490515
# If using NFSv4.1
491-
sudo crm configure primitive fs_<b>QAS</b>_ASCS Filesystem device='<b>10.1.0.4</b>:/usrsap<b>qas</b>' directory='/usr/sap/<b>QAS</b>/ASCS<b>00</b>' fstype='nfs' options='sec=sys,vers=4.1' \
516+
sudo crm configure primitive fs_<b>QAS</b>_ASCS Filesystem device='<b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>ascs' directory='/usr/sap/<b>QAS</b>/ASCS<b>00</b>' fstype='nfs' options='sec=sys,vers=4.1' \
492517
op start timeout=60s interval=0 \
493518
op stop timeout=60s interval=0 \
494519
op monitor interval=20s timeout=40s
@@ -543,13 +568,13 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
543568
sudo crm node online <b>anftstsapcl2</b>
544569
sudo crm node standby <b>anftstsapcl1</b>
545570
# If using NFSv3
546-
sudo crm configure primitive fs_<b>QAS</b>_ERS Filesystem device='<b>10.1.0.4</b>:/usrsap<b>qas</b>ers' directory='/usr/sap/<b>QAS</b>/ERS<b>01</b>' fstype='nfs' \
571+
sudo crm configure primitive fs_<b>QAS</b>_ERS Filesystem device='<b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>ers' directory='/usr/sap/<b>QAS</b>/ERS<b>01</b>' fstype='nfs' \
547572
op start timeout=60s interval=0 \
548573
op stop timeout=60s interval=0 \
549574
op monitor interval=20s timeout=40s
550575
551576
# If using NFSv4.1
552-
sudo crm configure primitive fs_<b>QAS</b>_ERS Filesystem device='<b>10.1.0.4</b>:/usrsap<b>qas</b>ers' directory='/usr/sap/<b>QAS</b>/ERS<b>01</b>' fstype='nfs' options='sec=sys,vers=4.1'\
577+
sudo crm configure primitive fs_<b>QAS</b>_ERS Filesystem device='<b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>ers' directory='/usr/sap/<b>QAS</b>/ERS<b>01</b>' fstype='nfs' options='sec=sys,vers=4.1'\
553578
op start timeout=60s interval=0 \
554579
op stop timeout=60s interval=0 \
555580
op monitor interval=20s timeout=40s
@@ -826,19 +851,19 @@ The following items are prefixed with either **[A]** - applicable to both PAS an
826851
<pre><code>
827852
sudo vi /etc/auto.direct
828853
# Add the following lines to the file, save and exit
829-
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>:/sapmnt<b>qas</b>
854+
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>/usrsap<b>qas</b>/sapmnt<b>QAS</b>
830855
/usr/sap/trans -nfsvers=3,nobind,sync <b>10.1.0.4</b>:/trans
831-
/usr/sap/<b>QAS</b>/D<b>02</b> -nfsvers=3,nobind,sync <b>10.1.0.5</b>:/usrsap<b>qas</b>pas
856+
/usr/sap/<b>QAS</b>/D<b>02</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>pas
832857
</code></pre>
833858

834859
If using NFSv4.1, create a new file with:
835860

836861
<pre><code>
837862
sudo vi /etc/auto.direct
838863
# Add the following lines to the file, save and exit
839-
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>:/sapmnt<b>qas</b>
864+
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>/usrsap<b>qas</b>/sapmnt<b>QAS</b>
840865
/usr/sap/trans -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>:/trans
841-
/usr/sap/<b>QAS</b>/D<b>02</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.5</b>:/usrsap<b>qas</b>pas
866+
/usr/sap/<b>QAS</b>/D<b>02</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>pas
842867
</code></pre>
843868

844869
Restart `autofs` to mount the new shares
@@ -861,19 +886,19 @@ The following items are prefixed with either **[A]** - applicable to both PAS an
861886
<pre><code>
862887
sudo vi /etc/auto.direct
863888
# Add the following lines to the file, save and exit
864-
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>:/sapmnt<b>qas</b>
889+
/sapmnt/<b>QAS</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>/usrsap<b>qas</b>/sapmnt<b>QAS</b>
865890
/usr/sap/trans -nfsvers=3,nobind,sync <b>10.1.0.4</b>:/trans
866-
/usr/sap/<b>QAS</b>/D<b>03</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>:/usrsap<b>qas</b>aas
891+
/usr/sap/<b>QAS</b>/D<b>03</b> -nfsvers=3,nobind,sync <b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>aas
867892
</code></pre>
868893

869894
If using NFSv4.1, create a new file with:
870895

871896
<pre><code>
872897
sudo vi /etc/auto.direct
873898
# Add the following lines to the file, save and exit
874-
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>:/sapmnt<b>qas</b>
899+
/sapmnt/<b>QAS</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>/usrsap<b>qas</b>/sapmnt<b>QAS</b>
875900
/usr/sap/trans -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>:/trans
876-
/usr/sap/<b>QAS</b>/D<b>03</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>:/usrsap<b>qas</b>aas
901+
/usr/sap/<b>QAS</b>/D<b>03</b> -nfsvers=4.1,nobind,sync,sec=sys <b>10.1.0.4</b>/usrsap<b>qas</b>/usrsap<b>QAS</b>aas
877902
</code></pre>
878903

879904
Restart `autofs` to mount the new shares
@@ -1423,5 +1448,4 @@ The following tests are a copy of the test cases in the [best practices guides o
14231448
* [Azure Virtual Machines deployment for SAP][deployment-guide]
14241449
* [Azure Virtual Machines DBMS deployment for SAP][dbms-guide]
14251450
* To learn how to establish high availability and plan for disaster recovery of SAP
1426-
* HANA on Azure (large instances), see [SAP HANA (large instances) high availability and disaster recovery on Azure](hana-overview-high-availability-disaster-recovery.md).
14271451
* 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]
Loading

0 commit comments

Comments
 (0)