Implementing HA SAP NetWeaver with AnyDB on Azure VMs (part 1)

By Ashwin Venugopal -

 


To read part 2 please click here


Single SID 3-tier SAP NetWeaver HA AnyDB Deployment

The three-tier SAP Azure Resource Manager templates supports high-availability scenarios and if you want to prepare a highly available infrastructure, for deploying the templates, then you have to set the SYSTEMAVAILABILITY parameter to HA. The templates can easily create:
  • Azure VMs (and, if applicable, their managed disks):
  • Network cards for all VMs, along with the associated IP addresses
  • Availability groups for SAP Application Server VMs, SAP ASCS /SCS cluster VMs, and DBMS cluster VMs.
  • Azure internal load balancer:
  1. With all ports for the ASCS/SCS instance and IP address
  2. With all ports for the SQL Server DBMS and IP address

  • Network security group with an open external Remote Desktop Protocol (RDP) port to the first SAP Application Server VM.

By default, all the IP addresses of the network cards as well as Azure internal load balancers are dynamic but you have to convert them to static IP addresses. 

Multi-SID 3-tier SAP NetWeaver HA AnyDB Deployment

You can easily create a new multi-SID cluster by simply using the multi-SID quickstart templates on GitHub, but you have to deploy the following templates to achieve this goal:

  • ASCS/SCS Template- It can deploy two VMs that can be used to create a Windows Server failover cluster that can readily host multiple ASCS/SCS instances. It  deploys one Azure Load Balancer instance, which supports multiple SAP systems:

  1. The ASCS instances are configured for instance number 00, 10,20....
  2. The SCS instances are configured for instance number 01, 11, 21....
  3. The ASCS Enque Replication Server (ERS) (Linux only) instances are configured for instance number 02, 12, 22....
  4. The SCS ERS (Linux only) instances are configured for instance number 03, 13, 23....

The load balancer consists of 1 VIP(s) (2 for Linux), 1 VIP for ASCS/SCS, and 1 for ERS (Linux only).

  • Database Template- It deploys one or two VMs that can be used to install the Relational Database Management System (RDBMS) for single SAP system. For example, if you deploy an ASCS/SCS template for five SAP systems, you have to deploy the template five times. It also supports SQL Server and SAP HANA.

  • Application Server Template- It deploys two or more VMs that can be used as SAP Application Server instances for one SAP system. For example, if you deploy an ASCS/SCS template for five SAP systems for five SAP systems, then you have to deploy it five times.

Networking Configuration

You should perform the following steps, if you want to set the required DNS IP addresses:
  1. In the Azure portal, in DNS servers pane, the virtual network DNS servers option should be set to Custom DNS and according to the type of your network, you can easily choose your settings.

  • Corporate network connectivity (cross-premises)- it adds the IP addresses of the on-premises DNS servers. It is recommended to extend your on-premises DNS environment by installing additional DNS servers in Azure VMs while also including the IP addresses of these Azure VMs.
  • For VM deployments which are isolated in Azure- it deploys an additional Azure VM in the same virtual network while configuring them as DNS servers. You can add the IP addresses of the Azure VMs that are set to run the DNS service.

     2. You will require the following reserved host names and IP addresses:

  • SAP ASCS/SCS first cluster virtual host name (for cluster management)
  • SAP ASCS/SCS instance virtual host name
  • SAP DBMS second cluster virtual host name (cluster management)

     3. Whenever you create the cluster, you should also create the virtual host names and the associated           IP addresses. These resources are used by the clustered SAP ASCS/SCS instance as well as the               clustered DBMS instance.

      4. After deploying the Azure VMs to use in your cluster, you have to configure them with static IP             addresses. You should perform this task in the Azure VM networking configuration, instead of the           guest operating system.

Note: The IP address of the virtual host name of the SAP ASCS/SCS is the same as that of the SAP ASCS/SCS  internal load balancer while the IP address of the virtual name of the DBMS is the same as that of the DBMS internal load balancer.

Active Directory Domain Configuration

After you assign static IP addresses to the Azure VMs, you can easily add the VMs to the domain.



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