Azure AZ-120 key terms

SAP support note listing supported Azure virtual machine types, SAP software versions, and maximum database sizes for running SAP NetWeaver and SAP HANA on Azure. It is the primary compatibility reference for sizing decisions.

Azure virtual machine families that SAP has tested and approved for particular SAP workloads, such as E-series for application servers and M-series for HANA databases. Certification depends on CPU, memory, and storage throughput.

Memory-optimized Azure virtual machine family offering large RAM sizes, used for SAP HANA production databases. Specific sizes support scale-up configurations up to multiple terabytes of memory.

Deployment pattern where a single large Azure virtual machine hosts the entire HANA database. It simplifies operations but limits capacity to the largest certified VM size.

Deployment pattern that distributes a HANA database across multiple Azure virtual machines in a cluster. It increases total memory and CPU capacity but requires careful network and storage design.

Fully managed Azure file storage service providing high-performance NFS and SMB shares. It is commonly used for SAP HANA data and log volumes and for shared SAP transport directories.

A logical storage container within Azure NetApp Files created in a capacity pool with a defined quota and service level. SAP deployments often use separate volumes for HANA data, log, and backup.

Azure disk feature that reduces write latency for the log volume of SAP HANA databases on M-series virtual machines. It is enabled per disk and requires specific disk and VM support.

Azure managed disk tier offering high IOPS and low latency for production SAP workloads. Disk size determines performance tier, so larger disks can deliver more throughput.

Azure managed disk option with configurable IOPS and throughput and sub-millisecond latency, used for demanding SAP database workloads. It requires specific VM families and availability zone support.

Azure feature that uses SR-IOV to bypass the virtual switch for network traffic, reducing latency and CPU overhead. It is recommended for SAP application and database servers with chatty communication.

Azure construct that constrains resources to the same datacenter to minimize network latency between them. SAP tiers benefit when application and database VMs must communicate with very low latency.

Logical grouping of virtual machines across fault domains and update domains within a single datacenter. It protects SAP tiers from hardware failure and planned maintenance but does not span zones.

Physically separate datacenter location within an Azure region, each with independent power and cooling. Distributing SAP VMs across zones improves resilience but adds cross-zone latency.

Group of hardware sharing a common power source and network switch within an Azure datacenter. VMs placed in different fault domains avoid a single point of hardware failure.

Grouping used by Azure to perform planned maintenance on virtual machines one set at a time. Spreading SAP VMs across update domains prevents simultaneous reboots.

Open-source high-availability cluster resource manager used on Linux to control SAP and HANA failover. On Azure it requires a fencing mechanism and a cluster configuration aligned with SAP and Microsoft guidance.

Shoot-the-other-node-in-the-head fencing mechanism that isolates a failed cluster node to prevent split-brain conditions. Azure deployments typically implement it with the Azure fence agent.

Cluster fencing component that uses Azure resource management APIs to stop or deallocate a failing virtual machine. It replaces traditional power fencing in Azure Pacemaker clusters.

Layer 4 load balancing service used to direct traffic to SAP application servers and to support cluster virtual IP addresses. Standard SKU is required for zone-aware and HA port configurations.

Azure Load Balancer feature that balances all ports on a backend pool simultaneously, simplifying rules for clustered SAP and database nodes. It is commonly enabled for Pacemaker-managed virtual IPs.

Load balancer setting that allows a cluster virtual IP to move between nodes without changing the destination address in packets. It is required for SAP ASCS/ERS and HANA cluster failover.

High-availability configuration that clusters the SAP ABAP Central Services and Enqueue Replication Server instances. Failover keeps the message and lock services available during node outages.

Azure service that replicates virtual machines to a secondary region or target for disaster recovery. It can orchestrate failover of SAP application servers and supporting infrastructure.

SAP HANA native replication that continuously ships redo logs from a primary to a secondary system. It enables database failover with minimal data loss across zones or regions.

Maximum acceptable duration for restoring an SAP service after a disruption. It drives decisions about clustering, replication, and automation in the disaster recovery design.

Maximum acceptable amount of data loss measured in time before a disruption. It determines replication frequency and backup schedules for SAP databases and file shares.

Managed backup service that protects Azure virtual machines and file shares with policy-driven snapshots and vault storage. It is used for SAP application servers and operating system recovery.

SAP backup interface that lets third-party tools stream database backups directly. Azure Backup for SAP HANA uses a Backint-compatible plug-in to protect HANA databases.

Database backup process that writes a consistent copy of HANA data to file or Backint destinations. Regular full and log backups are essential for point-in-time recovery.

SAP component running on each host that provides monitoring, start/stop control, and interface integration with SAP management tools. Correct installation and registration are needed for operations.

Command-line utility used to start, stop, and query SAP instances and to trigger local monitoring. Administrators use it for scripted operations and health checks on Azure VMs.

SAP Landscape Management tool that automates start, stop, and relocation of SAP systems across hosts. It supports planned maintenance and failover orchestration in Azure environments.

Azure service that collects SAP telemetry such as HANA and NetWeaver metrics into a central workspace. It provides dashboards and alerts for proactive operations.

Azure data store for log and metric queries using Kusto Query Language. It backs Azure Monitor for SAP Solutions and supports alerting and reporting on SAP workload health.

Azure service that discovers, assesses, and migrates on-premises servers and workloads. It helps size SAP systems and plan the move to Azure virtual machines.

Container for Azure blobs, files, and disks that provides durable storage. SAP migrations commonly use it to stage backups and transport files during cutover.

Managed SMB or NFS file share hosted in a storage account. It can host SAP transport directories and shared files when performance requirements are modest.