SAP HANA on Azure (Large Instances) compute, network, & storage (part 2)

By Ashwin Venugopal -

 


To read part 1 please click here
To read part 3 please click here


ExpressRoute Fast Path

Microsoft is offering ExpressRoute Fast Path since May 2019 to optimize connectivity of HANA Large Instances to Azure virtual networks that host the SAP application VMs which helps in not routing the data to flow between VMs and HANA Large Instances through the ExpressRoute Gateway anymore. 

The ExpressRoute Fast Path functionality needs that the subnets running the SAP application VMs are in the same Azure virtual network that connects to the HANA Large Instances while the VMs located in Azure virtual networks connected directly to the HANA Large Instance units are not profitable through ExpressRoute Fast Path. Additionally, ExpressRoute Fast Path does not support User Defined Routing (UDR) rules and requires an UltraPerformance ExpressRoute gateway. 

Single & Multiple SAP Systems

Single SAP system

The ExpressRoute gateway for the VMs hosting the SAP application instances is connected to one ExpressRoute circuit which in turn connects to an on-premises network and then connects to a separate enterprise edge router dedicated to connecting to Large Instance stamps.

This system is simple an example of a single SAP system where the SAP application layer is hosted in Azure and it is assumed that the ExpressRoute gateway bandwidth of 2-Gbps or 10-Gbps throughput doesn't represent a bottleneck.

Multiple SAP system

If you deploy multiple SAP systems or large SAP systems to connect with SAP HANA on Azure (Large Instances), then the throughput of the ExpressRoute gateway may become a bottleneck. You may also want to create a special virtual network that can connect to HANA Large Instance for following cases:

  • Performing backups directly from the HANA Instances in HANA Large Instance to a VM in Azure that can host NFS shares.

  • Copying large backups or other files from HANA Large Instance units to disk space managed in Azure.  

For more scalable network architecture:

  • Leverage multiple virtual networks for a single, larger SAP application layer.

  • Deploy one separate virtual network for each SAP system deployed, as compared to combining these SAP systems in separate subnets under the same virtual network.

Depending on the rules and restrictions, you can easily apply between the different virtual networks hosting VMs of different SAP systems, and peer from those virtual networks. 

Routing in Azure

The following dictates the routing behavior of SAP HANA on Azure (Large Instances):

  • By default, SAP HANA on Azure (Large Instances) can be accessed only through Azure VMs and the dedicated ExpressRoute connection, not directly through on-premises.

  • If you deploy HANA Large Instance units in two different Azure regions for disaster recovery, the same transient routing restrictions are applied in the past i.e. IP addresses of a HANA Large Instance unit in one region were not routed to HANA large Instance unit deployed in another region.

  • SAP HANA on Azure (Large Instances) units always have an assigned IP address from the server IP pool address range that you submitted while requesting the HANA Large Instance deployment.

You should be also aware that the implementation and support for custom solutions involving third-party network appliances and IPTables isn't offered by Microsoft and the support must be provided by the vendor of the component used or the integrator. 



To read part 1 please click here
To read part 3 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