SAP HANA on Azure (Large Instances) Compute, Network, & Storage (part 3)

By Ashwin Venugopal -

 



To read part 1 please click here
To read part 2 please click here


Express Route Global Reach

With the help of ExpressRoute Global Reach, customers are able to link the ExpressRoute circuits together to make a private network between on-premises networks. Global reach helps in the following two scenarios of HANA Large Instances:
  1. Enable direct access from on-premises to HANA Large Instance units deployed in different regions.
  2. Enable direct communication between your HANA Large Instance units deployed in different regions.   

Direct Access from on-premises

Wherever the global reach is provided within the Azure regions, the global reach functionality can be enabled for your ExpressRoute circuits that can connect your on-premises network to your Azure virtual network that in turn also connect to your HANA Large Instance units. There is no additional cost for you related to the circuit that connects the HANA Large Instance unit(s) to Azure, but, there are certain cost implications for the on-[remises side of your ExpressRoute circuit.

You can't use Azure NSGs to apply connectivity restrictions between your two HANA Large Instances tenants as the network traffic's data flow and control flow between different HANA Large instance tenants will not be routed through Azure virtual networks. 

Internet Connectivity of HANA Large Instance

HANA Large Instance don't have a direct internet connectivity which prevents you from registering the operating system instances directly with the OS vendor. As another option, you can also use SUSE Linux Enterprise Server Subscription Management Tool or Red Hat Enterprise Linux Subscription Manager.

Supported Scenarios

The HANA Large Instances are known for supporting a variety of architectural patterns to account for a wide range of business requirements. These supported scenarios includes:

  • Single node with one SID- This topology supports one node in a scale up configuration with one SID.

  • Single node MCOS- This topology supports one node in a scale up configuration with multiple SIDs. 

  • Single node with DR (Normal)- This topology supports one node in a scale up configuration with one or multiple SIDs along with the storage-based replication to the DR site for a primary SID. 

  • Single node with DR (Multipurpose)- This topology supports one node in a scale up configuration with one or multiple SIDs along with the storage-based replication to the DR site for a primary SID. 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. 

  • HSR with STONITH- This topology supports two nodes for the HANA System Replication (HSR) configuration which is only supported for single HANA instances on a node, i.e. MCOS scenarios are not supported. 

  • HSR with DR (Normal/Multipurpose)- This topology supports two nodes for the HANA System Replication (HSR) configuration. Both the DR and multipurpose configurations are only supported for single HANA instances on a node, i.e. MCOS scenarios are not supported. 

  • Host auto failover (1+1)- This topology supports two nodes in a host auto failover configuration and SAP supports this scenario only for S/4 HANA.

  • Scale-out with standby- This topology supports multiple nodes in a scale-out configuration. There is one node with master role, one or more nodes with worker role, and one or more nodes as standby.

  • Scale-out without standby-  This topology supports multiple nodes in a scale-out configuration. There is one node with master role, and one or more nodes with worker role.

  • Scale-out with DR- This topology supports multiple nodes in a scale-out with a DR. Both normal and multipurpose DR is supported. This topology can be requested with or without standby node.  



To read part 1 please click here
To read part 2 please click here






Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more