Skip to content

Commit 0f8cb5e

Browse files
Merge pull request #286538 from b-ahibbard/sap-hana
update faqs for extension 1
2 parents 87a2cc1 + 451bfab commit 0f8cb5e

File tree

2 files changed

+14
-12
lines changed

2 files changed

+14
-12
lines changed

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

Lines changed: 2 additions & 3 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: 06/18/2024
8+
ms.date: 09/11/2024
99
ms.author: anfdocs
1010
---
1111
# Understand Azure NetApp Files application volume group for SAP HANA
@@ -56,8 +56,7 @@ Application volume group for SAP HANA extension one offers support for:
5656

5757
* [Standard network features](azure-netapp-files-network-topologies.md)
5858

59-
Application volume group for SAP HANA now supports selecting Standard network features for all volumes in the volume group. The availability of Standard network features simplifies deployment, avoiding the manual process for AvSet pinning and eliminating the need for availability sets.
60-
59+
Application volume group for SAP HANA now supports selecting Standard network features for all volumes in the volume group. Standard network features support enhanced security including [network security groups (NSGs)](../virtual-network/network-security-group-how-it-works.md)
6160

6261
## Next steps
6362

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

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
title: FAQs About Azure NetApp Files application volume groups | Microsoft Docs
3-
description: answers frequently asked questions (FAQs) about Azure NetApp Files application volume groups.
3+
description: Learn answers to frequently asked questions (FAQs) about Azure NetApp Files application volume groups.
44
ms.service: azure-netapp-files
55
ms.topic: conceptual
66
author: b-hchen
77
ms.author: anfdocs
8-
ms.date: 05/19/2022
8+
ms.date: 09/11/2024
99
---
1010
# Azure NetApp Files application volume group FAQs
1111

12-
This article answers frequently asked questions (FAQs) about Azure NetApp Files application volume group.
12+
Find answers to frequently asked questions (FAQs) about Azure NetApp Files application volume group.
1313

1414
## Generic FAQs
1515

@@ -81,7 +81,7 @@ NFSv4.1 is the supported protocol for SAP HANA and Oracle. As such, one TCP/IP s
8181

8282
### How do I size Azure NetApp Files volumes for use with SAP HANA for optimal performance and cost-effectiveness?
8383

84-
For optimal sizing, it's important to size for the complete landscape including snapshots and backup. Decide your volume layout for production, HA, and data protection, and perform your sizing using the [Azure NetApp Files sizing calculator for SAP HANA deployments](https://aka.ms/anfsapcalc).
84+
For optimal sizing, it's important to size for the complete landscape including snapshots and backups. Decide your volume layout for production, HA, and data protection, and perform your sizing using the [Azure NetApp Files sizing calculator for SAP HANA deployments](https://aka.ms/anfsapcalc).
8585

8686
### I received a warning message `"Not enough pool capacity"`. What can I do?
8787

@@ -131,15 +131,19 @@ Database volume throughput mostly affects the time it takes to read data into me
131131

132132
Azure NetApp Files performance of each volume can be adjusted at runtime. As such, at any time, you can adjust the performance of your database by adjusting the data and log volume throughput to your specific requirements. For instance, you can fine-tune performance and reduce costs by allowing higher throughput at startup while reducing to KPIs during normal operation.
133133

134-
### Will all the volumes be provisioned in close proximity to my SAP HANA servers?
134+
### Are all the volumes provisioned in close proximity to my SAP HANA servers?
135135

136-
Using the proximity placement group (PPG) that you created for your SAP HANA servers ensures that the data, log, and shared volumes are created close to the SAP HANA servers to achieve the best latency and throughput. However, log-backup and data-backup volumes don’t require low latency. From a protection perspective, it makes sense to store these backup volumes in a different location from the data, log, and shared volumes. Therefore, application volume group places the backup volumes on a different storage location inside the region that has sufficient capacity and throughput available.
136+
With an application volume group, you have the option to deploy volumes with an availability zone or proximity placement group volume placement. Both methods ensure that the data volumes are placed in close proximity to the HANA VMs, but using different principles.
137+
138+
Using availability zone volume placement (available with extension 1) places the volumes in the same availability zone as the application VMs. Using availability zones also supports Standard network features, which support enhanced security via network security group support. This method doesn't require manual pinning. It'ss therefore easier and faster to use.
139+
140+
Using proximity placement group requires the creation of a proximity placement group (PPG) for your SAP HANA servers. This placement ensures the data, log, and shared volumes are created close to the SAP HANA servers to achieve the best latency and throughput. This method requires manual pinning of the proximity placement group, which application volume group uses to find the optimal location for deploying the volumes. This method only supports Basic network features. Note that log-backup and data-backup volumes don’t require low latency. From a protection perspective, it makes sense to store these backup volumes in a different location from the data, log, and shared volumes. Therefore, the application volume group places the backup volumes on a different storage location inside the region that has sufficient capacity and throughput availability.
137141

138142
### What is the relationship between AVset, VM, PPG, and Azure NetApp Files volumes?
139143

140144
A proximity placement group (PPG) needs to have at least one VM assigned to it, either directly or via an AVset. The purpose of the PPG is to extract the exact location of a VM and pass this information to application volume group to search for Azure NetApp Files resources in the very same data center. This setting only works when at least ONE VM in the PPG is started. Typically, you can add your database servers to the PPG.
141145

142-
PPGs have the side effect that if all VMs are shut down, a following restart of VMs DOES NOT guarantee that they will start in the same data center as before. To prevent this situation from happening, it's strongly recommended to use an AVset where all VMs and the PPG are associated to and use the [HANA pinning workflow](https://aka.ms/HANAPINNING). The workflow not only ensures that the VMs aren't moving when restarted, it also ensures that locations are selected where enough compute and Azure NetApp Files resources are available.
146+
PPGs have the side effect that if all VMs are shut down, a following restart of VMs DOES NOT guarantee that they'll start in the same data center as before. To prevent this situation from happening, it's strongly recommended to use an AVset where all VMs and the PPG are associated to and use the [HANA pinning workflow](https://aka.ms/HANAPINNING). The workflow not only ensures that the VMs aren't moving when restarted, it also ensures that locations are selected where enough compute and Azure NetApp Files resources are available.
143147

144148
### For a multi-host SAP HANA system, will the shared volume be resized when I add additional HANA hosts?
145149

@@ -152,7 +156,6 @@ No. This scenario is currently one of the very few cases where you need to manua
152156

153157
Log-back and data-backup volumes are optional, and they don't require close proximity. The best way to achieve the intended outcome is to remove the data-backup or log-backup volume when you create the first volume from the application volume group for SAP HANA. You can then create your own volume as a single, independent volume using standard volume provisioning and selecting the proper capacity and throughput to meet your needs. You should use a naming convention that indicates a data-backup volume and that it's used for multiple SIDs.
154158

155-
156159
## FAQs about application volume group for Oracle
157160

158161
This section answers questions about Azure NetApp Files application volume group for Oracle.
@@ -163,7 +166,7 @@ The deployment workflow ensures that all volumes are placed in the availability
163166

164167
### How do I size Azure NetApp Files volumes for use with Oracle for optimal performance and cost-effectiveness?
165168

166-
For optimal sizing, it's important to size for the complete database landscape including HA, snapshots, and backup. Decide your volume layout for production, HA and data protection, and perform your sizing according to [Run Your Most Demanding Oracle Workloads in Azure without Sacrificing Performance or Scalability](https://techcommunity.microsoft.com/t5/azure-architecture-blog/run-your-most-demanding-oracle-workloads-in-azure-without/ba-p/3264545) and [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183). You can also use the [SAP on Azure NetApp Files Sizing Estimator](https://aka.ms/anfsapcalc) by using the **Add Single Volume** input option.
169+
For optimal sizing, it's important to size for the complete database landscape including HA, snapshots, and backups. Decide your volume layout for production, HA and data protection, and perform your sizing according to [Run Your Most Demanding Oracle Workloads in Azure without Sacrificing Performance or Scalability](https://techcommunity.microsoft.com/t5/azure-architecture-blog/run-your-most-demanding-oracle-workloads-in-azure-without/ba-p/3264545) and [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183). You can also use the [SAP on Azure NetApp Files Sizing Estimator](https://aka.ms/anfsapcalc) by using the **Add Single Volume** input option.
167170

168171
Important information you need to provide for sizing each of the volumes includes: SID, role (production, Dev, pre-prod/QA), snapshot reserve in percentage, number of days for local snapshot retention, number of file-based backups, single-host/multiple-host with the number of hosts, and Data Guard requirements (primary, secondary). Contact an Oracle on Azure NetApp Files sizing expert to help you plan the overall Oracle system sizing.
169172

0 commit comments

Comments
 (0)