What's changed: Created AZ-120 Chapter 2 (Domain 2: compute (SAP-certified VMs, VM extension for SAP solutions, Marketplace/custom images, Bicep/ARM IaC, SDAF, Azure Center for SAP solutions); networking (VNet, Accelerated Networking, proximity placement group PPG, SAP latency requirements, ExpressRoute, private/service endpoints, Azure DNS); storage (disk types, striping vs simple, Write Accelerator for HANA log, Azure NetApp Files, Azure Files, Azure Disk Encryption)).
2.3Storage
Understand choosing storage types, disk striping, disk caching, Write Accelerator, encryption, and SAP storage design with Azure NetApp Files and Azure Files.
SAP (especially HANA) is sensitive to storage IOPS, throughput, and low latency. Meet requirements with disk types/configuration and SAP-specific optimizations.
2.3.1Disk types, striping, and Write Accelerator
Choose managed disks from Premium SSD / Ultra Disk (high IOPS, low latency) by SAP requirements. When one disk is insufficient, use disk striping (combine disks to sum IOPS/throughput); if one suffices, a simple volume. Disk caching helps read-heavy patterns, while Write Accelerator is an M-series VM feature that lowers write latency for HANA log disks for low-latency transaction-log writes (for log, not data, disks).
2.3.2Shared storage and encryption
For SAP shared file systems (/sapmnt, etc.) and HANA shared volumes, choose Azure NetApp Files (high-performance, low-latency, NFS/SMB, HANA-certified) or Azure Files (general SMB/NFS) by purpose (high-performance/large scale = NetApp Files; general/cost-conscious = Azure Files). Protect data with encryption (at-rest Storage Service Encryption; disk Azure Disk Encryption / key management).
Cues: "IOPS/capacity beyond a single disk" = disk striping (combine disks). "lower HANA log write latency (M-series)" = Write Accelerator (for log). "high-performance, low-latency shared storage/HANA-certified" = Azure NetApp Files. "general shared files" = Azure Files. Encrypt disks (Azure Disk Encryption).
Watch the mix-ups: (1) Write Accelerator is for HANA log disks (M-series)—distinct from data disks or read cache. (2) Disk striping (sum performance/capacity) vs simple volume (single). (3) NetApp Files (high-performance/HANA-certified) vs Azure Files (general) by purpose. (4) Disk-cache settings differ between HANA data and log.
2.3.3Section summary
- Choose disk types by SAP requirements; add performance/capacity via disk striping
- Write Accelerator lowers HANA log write latency on M-series (for log)
- Shared storage = Azure NetApp Files (high-perf/HANA-certified) or Azure Files (general); encrypt disks
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. On an M-series VM running SAP HANA, you want to lower write latency for the transaction-log disk. Best?
Q2. A single disk lacks IOPS/throughput; you want to sum performance across disks. Best?
Q3. For SAP shared file systems and HANA, you want high-performance, low-latency, HANA-certified shared storage. Best?
Q4. Which is the correct use of Write Accelerator?
Q5. You want to encrypt data at rest on SAP VM disks. Best?