Skip to content

Commit 071918e

Browse files
committed
mount options faq
1 parent 41a7856 commit 071918e

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/azure-netapp-files/faq-application-volume-group.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.workload: storage
66
ms.topic: conceptual
77
author: b-hchen
88
ms.author: anfdocs
9-
ms.date: 03/08/2022
9+
ms.date: 03/09/2022
1010
---
1111
# Application volume group FAQs
1212

@@ -43,11 +43,13 @@ General recommendations for snapshots in an SAP HANA environment are as follows:
4343
* Closely monitor the data volume snapshots. HANA tends to have a high change rate. Keeping snapshots for a long period might increase your capacity needs. Be sure to monitor the used capacity vs. allocated capacity.
4444
* If you automatically create snapshots for your (log and file) backups, be sure to monitor their retention to avoid unpredicted volume growth.
4545

46-
## When looking at the mount instructions of a volume I see a list of IPs. Which IP should I use?
46+
## The mount instructions of a volume include a list of IP addresses. Which IP address should I use?
4747

48-
Application volume group ensures that SAP HANA data and log volumes for one HANA host will always have different IPs to achieve best performance. For a single Azure NetApp Files hardware that hosts your data, log and shared volume, up to six different IPs may be created, which is the reason it is recommended to size the delegated subnet accordingly. See [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md).
48+
Application volume group ensures that SAP HANA data and log volumes for one HANA host will always have separate storage endpoints with different IP addresses to achieve best performance. To host your data, log and shared volumes across the Azure NetApp Files storage resource(s) up to six storage endpoints can be created per used Azure NetApp Files storage resource. For this reason, it is recommended to size the delegated subnet accordingly. See [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md). Although all listed IP addresses can be used for mounting, the first listed IP address is the one that provides the lowest latency. It is recommended to always use the first IP address.
4949

50-
Although all listed IPs can be used for mounting, the first IP listed is the one that provides the lowest latency. It is recommended to always use the first IP.
50+
## What is the optimal mount option for SAP HANA?
51+
52+
To have an optimal SAP HANA experience, there is more to do on the Linux client than just mounting the volumes. A complete setup and configuration guide is available for SAP HANA on Azure NetApp Files. It includes many recommended Linux settings and recommended mount options. See the SAP HANA solutions overview on [SAP HANA on Azure NetApp Files](azure-netapp-files-solution-architectures.md#sap-hana) to select the guide for your system architecture.
5153

5254
## The deployment failed and not even a single volume was created. Why is that?
5355

0 commit comments

Comments
 (0)