Skip to content

Commit c2c8f11

Browse files
committed
add note in Azure Premium Files
1 parent 95d239c commit c2c8f11

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/sap/workloads/planning-guide-storage.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,6 +349,7 @@ As preferences for allocating NFS volumes based on Azure NetApp Files for databa
349349
SAP scenarios supported on Azure Premium Files list like:
350350

351351
- Providing SMB or NFS shares for SAP's global transport directory
352+
- Usage as share for interfaces to SAP systems
352353
- The share sapmnt in high availability scenarios as documented in:
353354
- [High availability for SAP NetWeaver on Azure VMs on SUSE Linux Enterprise Server with NFS on Azure Files](./high-availability-guide-suse-nfs-azure-files.md)
354355
- [High availability for SAP NetWeaver on Azure VMs on Red Hat Enterprise Linux with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md)
@@ -357,6 +358,9 @@ SAP scenarios supported on Azure Premium Files list like:
357358

358359
Azure Premium Files is starting with larger amount of IOPS at the minimum share size of 100 GB compared to Azure NetApp Files. This higher bar of IOPS can avoid capacity overprovisioning to achieve certain IOPS and throughput values. For IOPS and storage throughput, read the section [Azure file share scale targets in Azure Files scalability and performance targets](../../storage/files/storage-files-scale-targets.md).
359360

361+
> [!NOTE]
362+
> Due to the tiered architecture of Azure Premium Files, the latency accessing metadata of the files stored in shares is significantly higher than with Azure NetApp Files. This higher latency can impact mass creation and deletion of files. But also can impact the time it takes to list content of shares. The main use case we see this higher metadata latency affecting is the usage as interface share where customers can encounter hundreds of thousands or even millions of file creations and mass deletions every day. Therefore, you should test the interface share scenarios diligently.
363+
360364
The capability matrix for SAP workload looks like:
361365

362366
| Capability| Comment| Notes/Links |
@@ -379,7 +383,7 @@ The capability matrix for SAP workload looks like:
379383
| Costs | low | - |
380384

381385

382-
**Summary**: Azure Premium Files is a low latency storage that allows to deploy NFS and SMB volumes or shares. Azure Premium Files provides excellent price/performance ratio for SAP application layer shares. It also provides synchronous zonal replication for these shares. So far, we don't support this storage type for SAP DBMS workload. Though it can be used for **/hana/shared** volumes.
386+
**Summary**: Azure Premium Files is a low latency storage that allows to deploy NFS and SMB volumes or shares. Azure Premium Files provides excellent price/performance ratio for SAP application layer shares. It also provides synchronous zonal replication for these shares. So far, we don't support this storage type for SAP DBMS workload. Though it can be used for **/hana/shared** volumes.
383387

384388

385389

0 commit comments

Comments
 (0)