Skip to content

Commit dd00ef8

Browse files
committed
restriction for powershell & CLI with avg. flex service level command
1 parent 8d470a1 commit dd00ef8

11 files changed

+46
-15
lines changed

articles/azure-netapp-files/application-volume-group-add-hosts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Add hosts to a multiple-host SAP HANA system using Azure NetApp Files application volume group for SAP HANA | Microsoft Docs
2+
title: Add hosts to a multiple-host SAP HANA system using Azure NetApp Files application volume group for SAP HANA
33
description: Describes how to add more HANA hosts after you've created the first host in an SAP HANA multiple-host setup.
44
services: azure-netapp-files
55
author: b-hchen
@@ -12,6 +12,8 @@ ms.author: anfdocs
1212

1313
Building a multiple-host SAP HANA database always starts with creating a volume group for the first host. To begin, you must create the first host in an SAP HANA multiple-host setup (see [Deploy the first SAP HANA host](application-volume-group-deploy-first-host.md)). After that, you can add additional HANA hosts by following steps in this article.
1414

15+
[!INCLUDE [PowerShell & CLI call-out](includes/application-volume-group-powershell.md)]
16+
1517
> [!IMPORTANT]
1618
> SAP recommends that you size the HANA shared volume to 1 x RAM of a HANA host for every four SAP HANA hosts of a multiple-host SAP HANA database. You might need to adjust the size for the shared volume you created with the initial host to adapt for the required capacity.
1719

articles/azure-netapp-files/application-volume-group-add-volume-secondary.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Add volumes for an SAP HANA system as a secondary database in HSR using Azure NetApp Files | Microsoft Docs
2+
title: Add volumes for an SAP HANA system as a secondary database in HSR using Azure NetApp Files
33
description: Describes using application volume group to add volumes for an SAP HANA system as a secondary database in HANA System Replication (HSR).
44
services: azure-netapp-files
55
author: b-hchen
@@ -12,6 +12,8 @@ ms.author: anfdocs
1212

1313
This article describes using application volume group to add volumes for an SAP HANA system as a secondary database in HANA System Replication (HSR).
1414

15+
[!INCLUDE [Application volume group CLI & PowerShell limitation](includes/application-volume-group-powershell.md)]
16+
1517
## HANA System Replication
1618

1719
The HANA System Replication (HSR) functionality enables SAP HANA databases to synchronously or asynchronously replicate from a primary SAP HANA system to a secondary SAP HANA system. The HSR uses application-level synchronization. The primary and the secondary SAP HANA systems have the same storage requirements, except for the following differences:

articles/azure-netapp-files/application-volume-group-deploy-first-host.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.author: anfdocs
1212

1313
All deployments start with the volumes for a single SAP HANA host. This is the case even for large, multiple-host installations. The shared, log-backup, and data-backup volumes are created only for the first host. All other hosts in a multiple-host environment share these volumes, and they add only data and log volumes for each additional host.
1414

15+
[!INCLUDE [Application volume group CLI & PowerShell limitation](includes/application-volume-group-powershell.md)]
16+
1517
This article describes how to deploy the first SAP HANA host using Azure NetApp Files application volume group for SAP HANA.
1618

1719
## Before you begin

articles/azure-netapp-files/application-volume-group-disaster-recovery.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ ms.author: anfdocs
1212

1313
This article describes using an application volume group to add volumes for an SAP HANA system as a disaster recovery (DR) system. This configuration uses Azure NetApp Files cross-region replication (CRR) functionality.
1414

15+
[!INCLUDE [Application volume group CLI & PowerShell limitation](includes/applicaiton-volume-group-powershell.md)]
16+
1517
## CRR between source and destination HANA servers
1618

1719
The Azure NetApp Files [cross-region replication](cross-region-replication-introduction.md) functionality enables you to replicate volumes between [supported cross-region replication pairs](cross-region-replication-introduction.md#supported-region-pairs). This functionality allows you to [replicate a volume](cross-region-replication-create-peering.md) from a source region to a volume on the destination region for disaster recovery (DR).

articles/azure-netapp-files/application-volume-group-manage-volumes-oracle.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ ms.author: anfdocs
1313

1414
You can manage a volume from its volume group. You can resize, delete, or change throughput for the volume.
1515

16+
[!INCLUDE [CLI & PowerShell call-out](includes/application-volume-group-powershell-oracle.md)]
17+
1618
## Steps
1719

1820
1. From your NetApp account, select **Application volume groups**.

articles/azure-netapp-files/application-volume-group-manage-volumes.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,15 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 11/19/2024
8+
ms.date: 05/14/2025
99
ms.author: anfdocs
1010
---
1111
# Manage volumes in an application volume group for SAP HANA
1212

1313
You can manage a volume from its volume group. You can resize, delete, or change throughput for the volume.
1414

15+
[!INCLUDE [Application volume group CLI & PowerShell limitation](includes/application-volume-group-powershell.md)]
16+
1517
## Steps
1618

1719
1. From your NetApp account, select **Application volume groups**. Select a volume group to display the volumes in the group.

articles/azure-netapp-files/application-volume-group-oracle-deploy-volumes.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,7 @@
22
title: Deploy application volume group for Oracle using Azure NetApp Files
33
description: Describes how to deploy all required volumes for your Oracle database using Azure NetApp Files application volume group for Oracle.
44
services: azure-netapp-files
5-
documentationcenter: ''
65
author: b-hchen
7-
manager: ''
8-
editor: ''
9-
10-
ms.assetid:
116
ms.service: azure-netapp-files
127
ms.workload: storage
138
ms.tgt_pltfrm: na
@@ -19,6 +14,8 @@ ms.author: anfdocs
1914

2015
This article describes how to deploy all required volumes for your Oracle database using Azure NetApp Files application volume group for Oracle.
2116

17+
[!INCLUDE [CLI & PowerShell call-out](includes/application-volume-group-powershell-oracle.md)]
18+
2219
## Before you begin
2320

2421
You should understand the [requirements and considerations for application volume group for Oracle](application-volume-group-oracle-considerations.md).

articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md

Lines changed: 10 additions & 4 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: how-to
8-
ms.date: 04/22/2025
8+
ms.date: 05/14/2025
99
ms.author: anfdocs
1010
---
1111
# Create a capacity pool for Azure NetApp Files
@@ -22,9 +22,15 @@ Creating a capacity pool enables you to create volumes within it.
2222
>[!IMPORTANT]
2323
>To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from `2024-01-01`.
2424
* The Standard, Premium, and Ultra service levels are generally available (GA). No registration is required.
25-
* The **Flexible** service level is currently in preview and supported in all Azure NetApp Files regions. You must submit a waitlist request to access the Flexible service level by using [the request form](https://aka.ms/ANFFlexibleSLpreviewsignup). After you submit the waitlist request, it can take approximately one week to enable the feature.
26-
27-
Check the status of feature registration with the command:
25+
* The **Flexible** service level is currently in preview and supported in all Azure NetApp Files regions. You must register the feature before using it for the first time:
26+
27+
1. Register the feature:
28+
29+
```azpowershell-interactive
30+
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFlexibleServiceLevel
31+
```
32+
33+
2. Check the status of feature registration with the command:
2834
2935
```azurepowershell-interactive
3036
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFlexibleServiceLevel
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
author: b-ahibbard
3+
ms.service: azure-netapp-files
4+
ms.topic: include
5+
ms.date: 05/14/2025
6+
ms.author: anfdocs
7+
8+
# application-volume-group-oracle-deploy-volumes.md
9+
#application-volume-group-manage-volumes-oracle.md
10+
---
11+
12+
>[!IMPORTANT]
13+
>Currently, using the Azure CLI or PowerShell to create or modify Oracle application volume group volumes isn't supported.

articles/azure-netapp-files/includes/application-volume-group-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,4 @@ ms.author: anfdocs
1515
>[!IMPORTANT]
1616
>Currently, using the the Azure CLI or PowerShell to create or modify SAP HANA application volume groups with availability zones or Standard network features isn't supported.
1717
18-
[!INCLUDE [Application volume group CLI & PowerShell limitation](includes/application-volume-group-powershell.md)]
18+

0 commit comments

Comments
 (0)