Skip to content

Commit 9c8f02a

Browse files
authored
Merge pull request #205725 from atikmapari/Broken-link-juergent
Broken link fixed
2 parents 01c5494 + 3f4cc4e commit 9c8f02a

File tree

5 files changed

+10
-17
lines changed

5 files changed

+10
-17
lines changed

articles/virtual-machines/workloads/sap/hana-vm-operations-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -271,7 +271,7 @@ Other advantages of Ultra disk can be the better read latency in comparison to p
271271
> Ultra disk is not yet present in all the Azure regions and is also not yet supporting all VM types listed below. For detailed information where Ultra disk is available and which VM families are supported, check the article [What disk types are available in Azure?](../../disks-types.md#ultra-disks).
272272
273273
### Production recommended storage solution with pure Ultra disk configuration
274-
In this configuration, you keep the **/hana/data** and **/hana/log** volumes separately. The suggested values are derived out of the KPIs that SAP has to certify VM types for SAP HANA and storage configurations as recommended in the [SAP TDI Storage Whitepaper](https://archive.sap.com/kmuuid2/70c8e423-c8aa-3210-3fae-e043f5c1ca92/SAP%20HANA%20TDI%20-%20Storage%20Requirements.pdf).
274+
In this configuration, you keep the **/hana/data** and **/hana/log** volumes separately. The suggested values are derived out of the KPIs that SAP has to certify VM types for SAP HANA and storage configurations as recommended in the [SAP TDI Storage Whitepaper](https://www.sap.com/documents/2017/09/e6519450-d47c-0010-82c7-eda71af511fa.html).
275275

276276
The recommendations are often exceeding the SAP minimum requirements as stated earlier in this article. The listed recommendations are a compromise between the size recommendations by SAP and the maximum storage throughput the different VM types provide.
277277

articles/virtual-machines/workloads/sap/hana-vm-operations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ The basic configuration of a VM node for SAP HANA scale-out looks like:
136136
- All other disk volumes aren't shared among the different nodes and aren't based on NFS. Installation configurations and steps for scale-out HANA installations with non-shared **/hana/data** and **/hana/log** is provided further later in this document. For HANA certified storage that can be used, check the article [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md).
137137

138138

139-
Sizing the volumes or disks, you need to check the document [SAP HANA TDI Storage Requirements](https://archive.sap.com/kmuuid2/70c8e423-c8aa-3210-3fae-e043f5c1ca92/SAP%20HANA%20TDI%20-%20Storage%20Requirements.pdf), for the size required dependent on the number of worker nodes. The document releases a formula you need to apply to get the required capacity of the volume
139+
Sizing the volumes or disks, you need to check the document [SAP HANA TDI Storage Requirements](https://www.sap.com/documents/2017/09/e6519450-d47c-0010-82c7-eda71af511fa.html), for the size required dependent on the number of worker nodes. The document releases a formula you need to apply to get the required capacity of the volume
140140

141141
The other design criteria that is displayed in the graphics of the single node configuration for a scale-out SAP HANA VM is the VNet, or better the subnet configuration. SAP highly recommends a separation of the client/application facing traffic from the communications between the HANA nodes. As shown in the graphics, this goal is achieved by having two different vNICs attached to the VM. Both vNICs are in different subnets, have two different IP addresses. You then control the flow of traffic with routing rules using NSGs or user-defined routes.
142142

@@ -335,4 +335,4 @@ Get familiar with the articles as listed
335335
- [Deploy a SAP HANA scale-out system with standby node on Azure VMs by using Azure NetApp Files on SUSE Linux Enterprise Server](./sap-hana-scale-out-standby-netapp-files-suse.md)
336336
- [Deploy a SAP HANA scale-out system with standby node on Azure VMs by using Azure NetApp Files on Red Hat Enterprise Linux](./sap-hana-scale-out-standby-netapp-files-rhel.md)
337337
- [High availability of SAP HANA on Azure VMs on SUSE Linux Enterprise Server](./sap-hana-high-availability.md)
338-
- [High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux](./sap-hana-high-availability-rhel.md)
338+
- [High availability of SAP HANA on Azure VMs on Red Hat Enterprise Linux](./sap-hana-high-availability-rhel.md)

articles/virtual-machines/workloads/sap/planning-guide.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1589,7 +1589,7 @@ In the table below typical SAP communication ports are listed. Basically it is s
15891589
**) sid = SAP-System-ID
15901590

15911591
For more information, see [TCP/IP Ports Used by SAP Applications]
1592-
(https://scn.sap.com/docs/DOC-17124). Using this document, you can open dedicated ports in the VPN device necessary for specific SAP products and scenarios.
1592+
(https://help.sap.com/docs/Security/575a9f0e56f34c6e8138439eefc32b16/616a3c0b1cc748238de9c0341b15c63c.html). Using this document, you can open dedicated ports in the VPN device necessary for specific SAP products and scenarios.
15931593

15941594
Other security measures when deploying VMs in such a scenario could be to create a [Network Security Group][virtual-networks-nsg] to define access rules.
15951595

@@ -1796,7 +1796,7 @@ We can separate the discussion about SAP high availability in Azure into two par
17961796

17971797
and how it can be combined with Azure infrastructure HA.
17981798

1799-
SAP High Availability in Azure has some differences compared to SAP High Availability in an on-premises physical or virtual environment. The following paper from SAP describes [standard SAP High Availability configurations in virtualized environments on Windows](https://scn.sap.com/docs/DOC-44415). There is no sapinst-integrated SAP-HA configuration for Linux. For more information about SAP HA on-premises for Linux, see [SAP High Availability Partner Information](https://scn.sap.com/docs/DOC-8541).
1799+
SAP High Availability in Azure has some differences compared to SAP High Availability in an on-premises physical or virtual environment. The following paper from SAP describes [standard SAP High Availability configurations in virtualized environments on Windows](https://help.sap.com/docs/SAP_NETWEAVER_703/a2cf03bc73a44b2a87d535cdb35e529e/45237d7e9f9b4002e10000000a155369.html). There is no sapinst-integrated SAP-HA configuration for Linux. For more information about SAP HA on-premises for Linux, see [SAP High Availability Partner Information](https://scn.sap.com/docs/DOC-8541).
18001800

18011801
### Azure Infrastructure High Availability
18021802

@@ -2018,4 +2018,4 @@ Read the articles:
20182018

20192019
- [Azure Virtual Machines deployment for SAP NetWeaver](./deployment-guide.md)
20202020
- [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](./dbms_guide_general.md)
2021-
- [SAP HANA infrastructure configurations and operations on Azure](./hana-vm-operations.md)
2021+
- [SAP HANA infrastructure configurations and operations on Azure](./hana-vm-operations.md)

articles/virtual-machines/workloads/sap/sap-hana-availability-across-regions.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ If you are using the scenario of sharing the DR target with a QA system in one V
4040

4141
- There are two [operation modes](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/627bd11e86c84ec2b9fcdf585d24011c.html) with delta_datashipping and logreplay, which are available for such a scenario
4242
- Both operation modes have different memory requirements without preloading data
43-
- Delta_datashipping might require drastically less memory without the preload option than logreplay could require. See chapter 4.3 of the SAP document [How To Perform System Replication for SAP HANA](https://archive.sap.com/kmuuid2/9049e009-b717-3110-ccbd-e14c277d84a3/How%20to%20Perform%20System%20Replication%20for%20SAP%20HANA.pdf)
43+
- Delta_datashipping might require drastically less memory without the preload option than logreplay could require. See chapter 4.3 of the SAP document [How To Perform System Replication for SAP HANA](https://www.sap.com/documents/2017/07/606a676e-c97c-0010-82c7-eda71af511fa.html)
4444
- The memory requirement of logreplay operation mode without preload is not deterministic and depends on the columnstore structures loaded. In extreme cases, you might require 50% of the memory of the primary instance. The memory for logreplay operation mode is independent on whether you chose to have the data preloaded set or not.
4545

4646

@@ -85,10 +85,3 @@ For step-by-step guidance on setting up these configurations in Azure, see:
8585

8686
- [Set up SAP HANA system replication in Azure VMs](sap-hana-high-availability.md)
8787
- [High availability for SAP HANA by using system replication](https://blogs.sap.com/2018/01/08/your-sap-on-azure-part-4-high-availability-for-sap-hana-using-system-replication/)
88-
89-
90-
91-
92-
93-
94-

articles/virtual-machines/workloads/sap/sap-hana-availability-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,8 @@ These articles provide a good overview of using SAP HANA in Azure:
4040
It's also a good idea to be familiar with these articles about SAP HANA:
4141

4242
- [High availability for SAP HANA](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/6d252db7cdd044d19ad85b46e6c294a4.html)
43-
- [FAQ: High availability for SAP HANA](https://archive.sap.com/documents/docs/DOC-66702)
44-
- [Perform system replication for SAP HANA](https://archive.sap.com/documents/docs/DOC-47702)
43+
- [FAQ: High availability for SAP HANA](https://www.sap.com/documents/2016/05/c6f37cb5-737c-0010-82c7-eda71af511fa.html)
44+
- [Perform system replication for SAP HANA](https://www.sap.com/documents/2017/07/606a676e-c97c-0010-82c7-eda71af511fa.html)
4545
- [SAP HANA 2.0 SPS 01 What’s new: High availability](https://blogs.sap.com/2017/05/15/sap-hana-2.0-sps-01-whats-new-high-availability-by-the-sap-hana-academy/)
4646
- [Network recommendations for SAP HANA system replication](https://www.sap.com/documents/2016/06/18079a1c-767c-0010-82c7-eda71af511fa.html)
4747
- [SAP HANA system replication](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.01/en-US/b74e16a9e09541749a745f41246a065e.html)
@@ -65,4 +65,4 @@ Measure your availability requirement against the SLAs that Azure components can
6565
## Next steps
6666

6767
- Learn about [SAP HANA availability within one Azure region](./sap-hana-availability-one-region.md).
68-
- Learn about [SAP HANA availability across Azure regions](./sap-hana-availability-across-regions.md).
68+
- Learn about [SAP HANA availability across Azure regions](./sap-hana-availability-across-regions.md).

0 commit comments

Comments
 (0)