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

By Ashwin Venugopal -

 

To read part 1 please click here



Add registry entries on both cluster nodes of the SAP ASCS-SCS instance

If you want to add registry entries on both cluster nodes of the SAP ASCS-SCS instance, then you have to add them on both Windows cluster nodes for SAP ASCS/SCS:

Path

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Variable name

KeepAliveTime

Variable type

REG_DWORD (Decimal)

Value

120000

Path

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Variable name

KeepAliveTime

Variable type

REG_DWORD (Decimal)

Value

120000

 You have to restart both the cluster nodes to apply the changes. 

Set up a Windows Server failover cluster for SAP ASCS-SCS instance

It involves the following tasks:

  • Add cluster nodes to the cluster.
  • Configure Cloud witness 

Add cluster nodes to the cluster

You have to set up the failover cluster by using the Failover Cluster Manager:

  • In the Failover Cluster Manager, select Create Cluster, and then add only the name of the first cluster.
  • Enter the network name (virtual host name) of the cluster.
  • After successfully creating the cluster, you have to run a validation test.
  • At this point you can ignore the warnings about disks and should not worry about having a quorum.
  • Bring the cluster virtual host name online.
  • Now you can add the second cluster node.

Configure cloud witness

If you want to configure the cloud witness, then you should have a valid Azure Storage Account through which you can store the blob file (used for arbitration). The same Microsoft Storage Account can be used to configure a Cloud Witness for multiple different clusters and will contain one-blob file per cluster. When creating a storage account, you should keep in mind that:
  • You can't use a Blob storage account for a Cloud Witness.
  • You can't use Azure Premium Storage for a Cloud Witness.
  • For replication, select Locally-redundant Storage (LRS) because the Failover Clustering uses the blob file as the arbitration point, which in turn also requires some consistency guarantees while reading the data. 

Note- No extra steps are required for the configuration necessary for the URL as the endpoint is generated automatically by Cloud Witness resource.

Configure failover parameters

After successfully installing the Windows Failover Clusters, you  should change some thresholds, so that they can adapt to the conditions in Azure for failover detection. If you assume that your two VMs consisting teh cluster configuration for ASCS/SCS are in the same subnet, then you can easily change the following parameters to these values:

  • SameSubNetDelay = 2000
  • SameSubNetThreshold = 15
  • RoutingHistoryLength = 30

Although all these settings are resilient enough, but they can also offer failover that is fast enough in real error conditions on a SAP atmosphere or in a node or VM failure. 



To read part 1 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