Skip to content

Commit 3dcec89

Browse files
ShannonLeavittShannonLeavitt
authored
Merge pull request #96738 from saghorpa/HLInewscenariosNov2019
HLI new scenarios added Nov 2019
2 parents 879bb46 + 33905e2 commit 3dcec89

File tree

6 files changed

+241
-8
lines changed

6 files changed

+241
-8
lines changed

‎articles/virtual-machines/workloads/sap/hana-supported-scenario.md

Lines changed: 241 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: virtual-machines-linux
1212
ms.topic: article
1313
ms.tgt_pltfrm: vm-linux
1414
ms.workload: infrastructure
15-
ms.date: 07/06/2018
15+
ms.date: 11/26/2019
1616
ms.author: saghorpa
1717
ms.custom: H1Hack27Feb2017
1818

@@ -34,7 +34,7 @@ Let's understand the terms and definitions used in the document.
3434
- Multipurpose DR: A system at DR site configured to use non-production environment along with production instance configured to use to DR event.
3535
- Single SID: A system with one instance installed.
3636
- Multi SID: A system with multiple instances configured. Also called an MCOS environment.
37-
37+
- HSR: SAP HANA System Replication.
3838

3939
## Overview
4040
The HANA Large Instances support the variety of architectures to accomplish your business requirements. The following list covers the scenarios and their configuration details.
@@ -105,7 +105,7 @@ Storage is preconfigured based on the topology requested. The volume sizes and m
105105

106106
In the architecture diagrams, following notations are used for the graphics:
107107

108-
![Legends.PNG](media/hana-supported-scenario/Legends.PNG)
108+
[ ![Legends.PNG](media/hana-supported-scenario/Legends.png)](media/hana-supported-scenario/Legends.png#lightbox)
109109

110110
The following list shows the supported scenarios:
111111

@@ -197,7 +197,7 @@ The following mountpoints are preconfigured:
197197
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
198198
- Volume size distribution is based off the database size in memory. Refer the [Overview and architecture](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-overview-architecture) section to learn what database sizes in memory are supported with multisid environment.
199199

200-
## 3. Single node with DR (Normal)
200+
## 3. Single node with DR using storage replication
201201

202202
This topology supports one node in a scale up configuration with one or multiple SIDs with the storage-based replication to the DR site for a primary SID. In the diagram, only single SID is depicted at the primary site, but multisid (MCOS) is supported as well.
203203

@@ -238,7 +238,7 @@ The following mountpoints are preconfigured:
238238
- Boot volume for **SKU Type I class** is replicated to DR node.
239239

240240

241-
## 4. Single node with DR (Multipurpose)
241+
## 4. Single node with DR (Multipurpose) using storage replication
242242

243243
This topology supports one node in a scale up configuration with one or multiple SIDs with the storage-based replication to the DR site for a primary SID. In the diagram, only single SID is depicted at the primary site, but multisid (MCOS) is supported as well. At the DR site, HLI unit is used for QA instance while production operations are running from the primary site. At the time of DR failover (or failover test), QA instance at DR site is taken down.
244244

@@ -287,7 +287,7 @@ The following mountpoints are preconfigured:
287287
- At the DR: The data, logbackups, log, shared volumes for QA (marked as “QA Instance installation”) are configured for the QA instance installation.
288288
- Boot volume for **SKU Type I class** is replicated to DR node.
289289

290-
## 5. HSR with STONITH
290+
## 5. HSR with STONITH for high availability
291291

292292
This topology support two nodes for the HANA System Replication (HSR) configuration. This configuration is only supported for single HANA instances on a node. Means, MCOS scenarios are NOT supported.
293293

@@ -336,7 +336,7 @@ The following mountpoints are preconfigured:
336336
- STONITH: An SBD is configured for the STONITH setup. However, a use of STONITH is optional.
337337

338338

339-
## 6. HSR with DR
339+
## 6. High availability with HSR and DR with storage replication
340340

341341
This topology support two nodes for the HANA System Replication (HSR) configuration. Both the normal and multipurpose DR is supported. These configurations are only supported for single HANA instances on a node. Means, MCOS scenarios are NOT supported with these configurations.
342342

@@ -513,7 +513,7 @@ The following mountpoints are preconfigured:
513513
### Key considerations
514514
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
515515

516-
## 10. Scale-out with DR
516+
## 10. Scale-out with DR using storage replication
517517

518518
This topology supports multiple nodes in a scale-out with a DR. Both normal and multipurpose DR is supported. In the diagram, only the single purpose DR is depicted. You can request this topology with or without the standby node.
519519

@@ -560,6 +560,239 @@ The following mountpoints are preconfigured:
560560
- Boot volume for **SKU Type I class** is replicated to DR node.
561561

562562

563+
## 11. Single node with DR using HSR
564+
565+
This topology supports one node in a scale up configuration with one SID with the HANA system replication to the DR site for a primary SID. In the diagram, only single SID is depicted at the primary site, but multisid (MCOS) is supported as well.
566+
567+
### Architecture diagram
568+
569+
![single-node-hsr-dr-111.png](media/hana-supported-scenario/single-node-hsr-dr-111.png)
570+
571+
### Ethernet
572+
The following network interfaces are preconfigured:
573+
574+
| NIC LOGICAL INTERFACES | SKU TYPE | Name with SUSE OS | Name with RHEL OS | Use case|
575+
| --- | --- | --- | --- | --- |
576+
| A | TYPE I | eth0.tenant | eno1.tenant | Client to HLI/HSR |
577+
| B | TYPE I | eth2.tenant | eno3.tenant | Configured but not in use |
578+
| C | TYPE I | eth1.tenant | eno2.tenant | Node to storage |
579+
| D | TYPE I | eth4.tenant | eno4.tenant | Configured but not in use |
580+
| A | TYPE II | vlan\<tenantNo> | team0.tenant | Client to HLI/HSR |
581+
| B | TYPE II | vlan\<tenantNo+2> | team0.tenant+2 | Configured but not in use |
582+
| C | TYPE II | vlan\<tenantNo+1> | team0.tenant+1 | Node to storage |
583+
| D | TYPE II | vlan\<tenantNo+3> | team0.tenant+3 | Configured but not in use |
584+
585+
### Storage
586+
The following mountpoints are preconfigured on both the HLI units (Primary and DR):
587+
588+
| Mountpoint | Use case |
589+
| --- | --- |
590+
|/hana/shared/SID | HANA Install for SID |
591+
|/hana/data/SID/mnt00001 | Data files install for SID |
592+
|/hana/log/SID/mnt00001 | Log files install for SID |
593+
|/hana/logbackups/SID | Redo logs for SID |
594+
595+
596+
### Key considerations
597+
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
598+
- For MCOS: Volume size distribution is based off the database size in memory. Refer the [Overview and architecture](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-overview-architecture) section to learn what database sizes in memory are supported with multisid environment.
599+
- Primary node get sync to DR node using HANA system replication.
600+
- [Global Reach](https://docs.microsoft.com/azure/expressroute/expressroute-global-reach) is used to link the ExpressRoute circuits together to make a private network between your regions network.
601+
602+
603+
604+
## 12. Single node HSR to DR (cost optimized)
605+
606+
This topology supports one node in a scale up configuration with one SID with the HANA system replication to the DR site for a primary SID. In the diagram, only single SID is depicted at the primary site, but multisid (MCOS) is supported as well. At the DR site, HLI unit is used for QA instance while production operations are running from the primary site. At the time of DR failover (or failover test), QA instance at DR site is taken down.
607+
608+
### Architecture diagram
609+
610+
![single-node-hsr-dr-cost-optimized-121.png](media/hana-supported-scenario/single-node-hsr-dr-cost-optimized-121.png)
611+
612+
### Ethernet
613+
The following network interfaces are preconfigured:
614+
615+
| NIC LOGICAL INTERFACES | SKU TYPE | Name with SUSE OS | Name with RHEL OS | Use case|
616+
| --- | --- | --- | --- | --- |
617+
| A | TYPE I | eth0.tenant | eno1.tenant | Client to HLI/HSR |
618+
| B | TYPE I | eth2.tenant | eno3.tenant | Configured but not in use |
619+
| C | TYPE I | eth1.tenant | eno2.tenant | Node to storage |
620+
| D | TYPE I | eth4.tenant | eno4.tenant | Configured but not in use |
621+
| A | TYPE II | vlan\<tenantNo> | team0.tenant | Client to HLI/HSR |
622+
| B | TYPE II | vlan\<tenantNo+2> | team0.tenant+2 | Configured but not in use |
623+
| C | TYPE II | vlan\<tenantNo+1> | team0.tenant+1 | Node to storage |
624+
| D | TYPE II | vlan\<tenantNo+3> | team0.tenant+3 | Configured but not in use |
625+
626+
### Storage
627+
The following mountpoints are preconfigured:
628+
629+
| Mountpoint | Use case |
630+
| --- | --- |
631+
|**At the primary site**|
632+
|/hana/shared/SID | HANA Install for production SID |
633+
|/hana/data/SID/mnt00001 | Data files install for production SID |
634+
|/hana/log/SID/mnt00001 | Log files install for production SID |
635+
|/hana/logbackups/SID | Redo logs for production SID |
636+
|**At the DR site**|
637+
|/hana/shared/SID | HANA Install for production SID |
638+
|/hana/data/SID/mnt00001 | Data files install for production SID |
639+
|/hana/log/SID/mnt00001 | Log files install for production SID |
640+
|/hana/logbackups/SID | Redo logs for production SID |
641+
|/hana/shared/QA-SID | HANA Install for QA SID |
642+
|/hana/data/QA-SID/mnt00001 | Data files install for QA SID |
643+
|/hana/log/QA-SID/mnt00001 | Log files install for QA SID |
644+
|/hana/logbackups/QA-SID | Redo logs for QA SID |
645+
646+
### Key considerations
647+
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
648+
- For MCOS: Volume size distribution is based off the database size in memory. Refer the [Overview and architecture](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-overview-architecture) section to learn what database sizes in memory are supported with multisid environment.
649+
- At the DR: The volumes and mountpoints are configured (marked as “PROD Instance at DR site”) for the production HANA Instance installation at the DR HLI unit.
650+
- At the DR: The data, logbackups, log, shared volumes for QA (marked as “QA Instance installation”) are configured for the QA instance installation.
651+
- Primary node get sync to DR node using HANA system replication.
652+
- [Global Reach](https://docs.microsoft.com/azure/expressroute/expressroute-global-reach) is used to link the ExpressRoute circuits together to make a private network between your regions network.
653+
654+
## 13. High availability and disaster recovery with HSR
655+
656+
This topology support two nodes for the HANA System Replication (HSR) configuration for the local regions high availability. For the DR, the third node at the DR region gets sync from primary site using HSR (async mode).
657+
658+
### Architecture diagram
659+
660+
![hana-system-replication-dr-131.png](media/hana-supported-scenario/hana-system-replication-dr-131.png)
661+
662+
### Ethernet
663+
The following network interfaces are preconfigured:
664+
665+
| NIC LOGICAL INTERFACES | SKU TYPE | Name with SUSE OS | Name with RHEL OS | Use case|
666+
| --- | --- | --- | --- | --- |
667+
| A | TYPE I | eth0.tenant | eno1.tenant | Client to HLI/HSR |
668+
| B | TYPE I | eth2.tenant | eno3.tenant | Configured but not in use |
669+
| C | TYPE I | eth1.tenant | eno2.tenant | Node to storage |
670+
| D | TYPE I | eth4.tenant | eno4.tenant | Configured but not in use |
671+
| A | TYPE II | vlan\<tenantNo> | team0.tenant | Client to HLI/HSR |
672+
| B | TYPE II | vlan\<tenantNo+2> | team0.tenant+2 | Configured but not in use |
673+
| C | TYPE II | vlan\<tenantNo+1> | team0.tenant+1 | Node to storage |
674+
| D | TYPE II | vlan\<tenantNo+3> | team0.tenant+3 | Configured but not in use |
675+
676+
### Storage
677+
The following mountpoints are preconfigured:
678+
679+
| Mountpoint | Use case |
680+
| --- | --- |
681+
|**At the primary site**|
682+
|/hana/shared/SID | HANA Install for production SID |
683+
|/hana/data/SID/mnt00001 | Data files install for production SID |
684+
|/hana/log/SID/mnt00001 | Log files install for production SID |
685+
|/hana/logbackups/SID | Redo logs for production SID |
686+
|**At the DR site**|
687+
|/hana/shared/SID | HANA Install for production SID |
688+
|/hana/data/SID/mnt00001 | Data files install for production SID |
689+
|/hana/log/SID/mnt00001 | Log files install for production SID |
690+
|/hana/logbackups/SID | Redo logs for production SID |
691+
692+
693+
### Key considerations
694+
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
695+
- At the DR: The volumes and mountpoints are configured (marked as “PROD DR instance”) for the production HANA Instance installation at the DR HLI unit.
696+
- Primary site node get sync to DR node using HANA system replication.
697+
- [Global Reach](https://docs.microsoft.com/azure/expressroute/expressroute-global-reach) is used to link the ExpressRoute circuits together to make a private network between your regions network.
698+
699+
## 14. High availability and disaster recovery with HSR (cost optimized)
700+
701+
This topology support two nodes for the HANA System Replication (HSR) configuration for the local regions high availability. For the DR, the third node at the DR region gets sync from primary site using HSR (async mode), while an another instance (eg. QA) already running out from the DR node.
702+
703+
### Architecture diagram
704+
705+
![hana-system-replication-dr-cost-optimized-141.png](media/hana-supported-scenario/hana-system-replication-dr-cost-optimized-141.png)
706+
707+
### Ethernet
708+
The following network interfaces are preconfigured:
709+
710+
| NIC LOGICAL INTERFACES | SKU TYPE | Name with SUSE OS | Name with RHEL OS | Use case|
711+
| --- | --- | --- | --- | --- |
712+
| A | TYPE I | eth0.tenant | eno1.tenant | Client to HLI/HSR |
713+
| B | TYPE I | eth2.tenant | eno3.tenant | Configured but not in use |
714+
| C | TYPE I | eth1.tenant | eno2.tenant | Node to storage |
715+
| D | TYPE I | eth4.tenant | eno4.tenant | Configured but not in use |
716+
| A | TYPE II | vlan\<tenantNo> | team0.tenant | Client to HLI/HSR |
717+
| B | TYPE II | vlan\<tenantNo+2> | team0.tenant+2 | Configured but not in use |
718+
| C | TYPE II | vlan\<tenantNo+1> | team0.tenant+1 | Node to storage |
719+
| D | TYPE II | vlan\<tenantNo+3> | team0.tenant+3 | Configured but not in use |
720+
721+
### Storage
722+
The following mountpoints are preconfigured:
723+
724+
| Mountpoint | Use case |
725+
| --- | --- |
726+
|**At the primary site**|
727+
|/hana/shared/SID | HANA Install for production SID |
728+
|/hana/data/SID/mnt00001 | Data files install for production SID |
729+
|/hana/log/SID/mnt00001 | Log files install for production SID |
730+
|/hana/logbackups/SID | Redo logs for production SID |
731+
|**At the DR site**|
732+
|/hana/shared/SID | HANA Install for production SID |
733+
|/hana/data/SID/mnt00001 | Data files install for production SID |
734+
|/hana/log/SID/mnt00001 | Log files install for production SID |
735+
|/hana/logbackups/SID | Redo logs for production SID |
736+
|/hana/shared/QA-SID | HANA Install for QA SID |
737+
|/hana/data/QA-SID/mnt00001 | Data files install for QA SID |
738+
|/hana/log/QA-SID/mnt00001 | Log files install for QA SID |
739+
|/hana/logbackups/QA-SID | Redo logs for QA SID |
740+
741+
### Key considerations
742+
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
743+
- At the DR: The volumes and mountpoints are configured (marked as “PROD DR instance”) for the production HANA Instance installation at the DR HLI unit.
744+
- At the DR: The data, logbackups, log, shared volumes for QA (marked as “QA Instance installation”) are configured for the QA instance installation.
745+
- Primary site node get sync to DR node using HANA system replication.
746+
- [Global Reach](https://docs.microsoft.com/azure/expressroute/expressroute-global-reach) is used to link the ExpressRoute circuits together to make a private network between your regions network.
747+
748+
## 15. Scale-out with DR using HSR
749+
750+
This topology supports multiple nodes in a scale-out with a DR. You can request this topology with or without the standby node. Primary site nodes get sync to the DR site nodes with HANA system replication (async mode).
751+
752+
753+
### Architecture diagram
754+
755+
[ ![scale-out-dr-hsr-151.png](media/hana-supported-scenario/scale-out-dr-hsr-151.png)](media/hana-supported-scenario/scale-out-dr-hsr-151.png#lightbox)
756+
757+
758+
### Ethernet
759+
The following network interfaces are preconfigured:
760+
761+
| NIC LOGICAL INTERFACES | SKU TYPE | Name with SUSE OS | Name with RHEL OS | Use case|
762+
| --- | --- | --- | --- | --- |
763+
| A | TYPE I | eth0.tenant | eno1.tenant | Client to HLI/HSR |
764+
| B | TYPE I | eth2.tenant | eno3.tenant | Node to node communication |
765+
| C | TYPE I | eth1.tenant | eno2.tenant | Node to storage |
766+
| D | TYPE I | eth4.tenant | eno4.tenant | Configured but not in use |
767+
| A | TYPE II | vlan\<tenantNo> | team0.tenant | Client to HLI/HSR |
768+
| B | TYPE II | vlan\<tenantNo+2> | team0.tenant+2 | Node to node communication |
769+
| C | TYPE II | vlan\<tenantNo+1> | team0.tenant+1 | Node to storage |
770+
| D | TYPE II | vlan\<tenantNo+3> | team0.tenant+3 | Configured but not in use |
771+
772+
### Storage
773+
The following mountpoints are preconfigured:
774+
775+
| Mountpoint | Use case |
776+
| --- | --- |
777+
|**On the primary node**|
778+
|/hana/shared | HANA Install for production SID |
779+
|/hana/data/SID/mnt00001 | Data files install for production SID |
780+
|/hana/log/SID/mnt00001 | Log files install for production SID |
781+
|/hana/logbackups/SID | Redo logs for production SID |
782+
|**On the DR node**|
783+
|/hana/shared | HANA Install for production SID |
784+
|/hana/data/SID/mnt00001 | Data files install for production SID |
785+
|/hana/log/SID/mnt00001 | Log files install for production SID |
786+
|/hana/logbackups/SID | Redo logs for production SID |
787+
788+
789+
### Key considerations
790+
- /usr/sap/SID is a symbolic link to /hana/shared/SID.
791+
- At the DR: The volumes and mountpoints are configured for the production HANA Instance installation at the DR HLI unit.
792+
- Primary site nodes get sync to DR nodes using HANA system replication.
793+
- [Global Reach](https://docs.microsoft.com/azure/expressroute/expressroute-global-reach) is used to link the ExpressRoute circuits together to make a private network between your regions network.
794+
795+
563796
## Next steps
564797
- Refer [Infrastructure and connectivity](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-overview-infrastructure-connectivity) for HLI
565798
- Refer [High availability and disaster recovery](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-overview-high-availability-disaster-recovery) for HLI

‎articles/virtual-machines/workloads/sap/media/hana-supported-scenario/hana-system-replication-dr-131.png

134 KB
Loading

‎articles/virtual-machines/workloads/sap/media/hana-supported-scenario/hana-system-replication-dr-cost-optimized-141.png

159 KB
Loading

‎articles/virtual-machines/workloads/sap/media/hana-supported-scenario/scale-out-dr-hsr-151.png

124 KB
Loading

‎articles/virtual-machines/workloads/sap/media/hana-supported-scenario/single-node-hsr-dr-111.png

107 KB
Loading

‎articles/virtual-machines/workloads/sap/media/hana-supported-scenario/single-node-hsr-dr-cost-optimized-121.png

137 KB
Loading

0 commit comments

Comments
 (0)