Operating System Support of Azure for SAP Workloads

By Ashwin Venugopal -

 



Azure VMs

SAP certified operating systems supported for SAP products on Azure VMs includes:
  • Microsoft Windows Server 2008 R2, 2012 (R2), 2016 and 2019
  • SUSE Linux Enterprise Server 12 (SLES 12) and higher
  • SUSE SLES for SAP Applications (based on SLES 12) and higher
  • Red Hat Enterprise Linux 7 (RHEL 7) and higher
  • Red Hat RHEL for SAP (based on RHEL 7) and higher
  • Red Hat RHEL for SAP HANA (based on RHEL 7) and higher
  • Oracle Linux 7 (OL7)
While running SAP products on Linux, you should also review the following SAP notes:
  • 2243692- Linux on Microsoft Azure (Iaas) VM SAP license issues
  • 2513384- SUSE Linux Enterprise Server for SAP Applications for Azure
  • 2694118- Red Hat Enterprise Linux HA Add-On on Azure
Note- Multi-SID cluster configurations for SAP Central Services is supported with Windows Server as guest operating system on Azure VMs, but it is not supported with any of the Linux distributions.

SAP HANA on Azure (Large Instances)

SAP-certified operating systems supported for SAP products on SAP HANA on Azure (Large Instances) includes:

  • SUSE Linux Enterprise Server 12 for SAP Applications.
  • Red Hat Enterprise Linux 6.7 or 7.x for SAP HANA.

Storage Support for Azure for SAP Workloads

Azure VM Disks

Storage-specific provisions for Azure VM hosting SAP workloads can be described as:
  • "To increase the total number of IOPS per volume presented to a guest operating system in the VM multiple disks can be striped using functionality operating systems offer and each disk is protected from a physical drive failure by the means of mirroring. Hence, using a software RAID level higher than RAID-0 is not necessary."

  • "DB log files should be stored on different disks than the DB data files."

  • "Azure VMs automatically offers a D:\ drive within the VM instance, which is not persisted and should not be used at all by the DBMS or any SAP files/directories."

  • The use of managed disk is recommended for SAP workloads. 

Using Azure Premium Storage for all the SAP production systems is strongly recommended in Azure VMs instead of Azure Standard Storage. Most of the performance issues of the DBMS that are deployed in Azure VMs are related to:
  • IPOS limits of Standard Storage
  • High latency with Azure Standard Storage, which slows down business processing. 

SQL Server also offers to place SQL Server data files and transaction log files directly on Azure Storage Blobs without wrapping them in VHDs as it can overcome the VHD limits in smaller Azure VMs as well as increases the IOPS using Azure Standard Storage. However, it is not recommended to directly place SQL Server data and transaction log on Azure Storage Blobs as standard deployment method because:

  • The Premium Storage Cache, which is established on the local compute node is not used in such a scenario. 
  • The data volume throughput SLA of the VM is not honored.
  • I/O traffic goes through the network channel and not through the storage I/O channel. Especially when using the Premium Storage this can lead to some disadvantages with regards to the deterministic I/O latencies. 
  • A Premium Storage Account has a current size limitation of 35 TB.
  • An Azure Standard Storage Account cannot be transferred to a Premium Storage Account. If you want to move a VHD from one storage account to another, then, you have to copy the VHDs between them. 
  • For SAP application servers, often Premium Storage is not needed from a storage workload point-of-view,
  • For Azure Standard Storage, any caching is not recommended which is offered during the creation of VHDs which is different to Azure Premium Storage. 
  • With Azure Premium Storage, allowing of read only caching is recommended for the VHDs that supports DBMS files. VHDs supporting transaction log or redo files should not use any caching with Azure Premium Storage.
  • Azure Premium Storage read/write caching should not be used for the VHDs that supports database files.  

The choice of the storage has also backup implications and Premium Storage must also be used in combination with the Microsoft Data Protection Manager (DPM) in Azure.











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