SAP HANA on Azure (Large Instances)

By Ashwin Venugopal -

 



High-Level Architecture

The overall architecture of SAP HANA on Azure (Large Instances) readily offers ability and flexibility of Azure to scale resources for the SAP application layer to meet your needs.




The Azure Large Instance stamp composed of the following resources:

  • Compute- Servers that are based on one of the several generations of  Intel Xeon processors that provide the necessary compute capability and are SAP HANA certified.
  • Network- A unified high-speed network fabric that interconnects the compute and storage.
  • Storage- It can be easily accessed through a unified network fabric and its storage capacity depends upon the specific SAP HANA on Azure (Large Instances) configuration specified by each customer but more storage capacity can be added at an additional monthly.

SAP HANA on Azure (Large Instance) are offered in multiple Azure regions which facilitates the disaster recovery capabilities that customers can easily choose to implement as different Large Instance stamps within one geo-political region are connected to each other, for example, HANA Large Instance Stamps in US West and US East are connected through a dedicated network link for disaster recovery replication. 

Architectural Components

  • Virtual network- This service can securely connect various Azure resources to each other and is also subdivided into separate subnets for each layer which can readily deployed on Azure VMs to connect to the HANA database layer residing on large instances.

  • Virtual machines- They are extensively used in the SAP application layer as well as shared services layer which includes a jumpbox used by administrators to set up HANA Large Instances also to offer access to other VMs.

  • HANA Large Instances- It is a physical server certified to meet SAP HANA Tailored Datacenter Integration (TDI) standards runs SAP HANA which uses two HANA Large Instances i.e. a primary and a secondary compute unit. High availability at the data layer is provided through HANA System Replication (HSR).

  • High availability pair- It is a group of HANA Large Instances blades that are managed together to provide application redundancy and reliability.

  • MSEE (Microsoft Enterprise Edge)- It is a connection point from a connectivity provider or your network edge through an ExpressRoute circuit.

  • Network Interface Cards (NICs)- HANA Large Instance server offers four virtual NICs by default in which one NIC is required for client communication, second for the node-to-node connectivity needed by HSR, third for HANA Large Instance storage, and fourth for iSCSI used in high availability clustering.

  • Network File System (NFS) storage- This server supports the network file share that provides the secure data persistence for HANA Large Instance.

  • ExpressRoute- It is widely recommended for creating the private connections between an on-premises as well as Azure virtual networks that do not go over the public internet. This connection is setup as a part of Microsoft offering.

  • Gateway- The ExpressRoute Gateway is generally used to connect the Azure virtual network used for the SAP application layer to the HANA large Instance network and use the High Performance or Ultra Performance SKU.

  • Disaster Recovery (DR)- Storage replication is supported and will be configured from the primary to the DR site located in another region, upon request.








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