Skip to content

Commit 9f258f9

Browse files
author
rdeltcheva
committed
Add hana shared considerations
1 parent 70df768 commit 9f258f9

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

articles/sap/workloads/hana-vm-operations-storage.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords: 'SAP, Azure HANA, Storage Ultra disk, Premium storage'
77
ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
10-
ms.date: 08/03/2023
10+
ms.date: 03/18/2024
1111
ms.author: juergent
1212
ms.custom: H1Hack27Feb2017
1313
---
@@ -97,6 +97,22 @@ Accumulating multiple Azure disks underneath a stripe set, is accumulative from
9797
> [!IMPORTANT]
9898
> In case you're using LVM or mdadm as volume manager to create stripe sets across multiple Azure premium disks, the three SAP HANA FileSystems /data, /log and /shared must not be put in a default or root volume group. It's highly recommended to follow the Linux Vendors guidance which is typically to create individual Volume Groups for /data, /log and /shared.
9999
100+
## Considerations for the HANA shared file system
101+
102+
When sizing the HANA file systems the spotlight is on the data and log file HANA systems. Yet, appropriately sizing **/hana/shared** also plays an important role in operating a stable HANA system, especially when deployed in HA configuration.
103+
If undersized, **/hana/shared** could become I/O saturated or latency can increase. For example: writing a large dump, or intensive tracing, HANA backup location left pointing to /hana/shared could exceed the available throughput / IOps.
104+
105+
If the HANA system is in HA configuration, a slow response from the shared file system, i.e. **/hana/shared** could result in cluster resources timeouts, which in turn may lead to unnecessary failovers, as the HANA resource agents erroneously assume the database is not available.
106+
107+
The SAP guidelines for **/hana/shared** for recommended recommended sizes would look like:
108+
109+
| Volume | Recommended Size |
110+
| --- | --- |
111+
| /hana/shared scale-up | Min(1 TB, 1 x RAM) |
112+
| /hana/shared scale-out | 1 x RAM of worker node<br /> per four worker nodes |
113+
114+
In addition to the documented guidelines, when sizing **/hana/shared** ensure that there is enough bandwidth to absorb the above described operations.
115+
100116

101117
## Azure Premium Storage v1 configurations for HANA
102118
For detailed HANA storage configuration recommendations using Azure premium storage v1, read the document [SAP HANA Azure virtual machine Premium SSD storage configurations](./hana-vm-premium-ssd-v1.md)

0 commit comments

Comments
 (0)