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

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more