Skip to content

Commit 411071e

Browse files
committed
fix broken link
1 parent 4e8e90c commit 411071e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 03/13/2025
8+
ms.date: 04/22/2025
99
ms.author: anfdocs
1010
---
1111
# Understand Azure NetApp Files application volume group for SAP HANA
@@ -42,7 +42,7 @@ Application volume group for SAP HANA helps you simplify the deployment process
4242

4343
* [Availability zone volume placement](use-availability-zones.md)
4444

45-
Designating the same availability zone for the volumes ensures that virtual machines and Azure NetApp Files volumes reside in the same availability zone and meet the latency requirements for SAP HANA. Availability zone volume placement simplifies the deployment process, avoiding the manual AvSet pinning process and eliminating the requirement for availability sets. To learn more about the differences between availability zone volume placement and proximity placement groups, see [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md#bes-practices-about-proximity-placement).
45+
Designating the same availability zone for the volumes ensures that virtual machines and Azure NetApp Files volumes reside in the same availability zone and meet the latency requirements for SAP HANA. Availability zone volume placement simplifies the deployment process, avoiding the manual AvSet pinning process and eliminating the requirement for availability sets. To learn more about the differences between availability zone volume placement and proximity placement groups, see [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md#best-practices-about-proximity-placement).
4646

4747
* Creation of separate storage endpoints (with different IP addresses) for data and log volumes.
4848
* This deployment method provides better performance and throughput for the SAP HANA database.

0 commit comments

Comments
 (0)