You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
36
36
| - | - | - |
37
37
| In-Azure bare-metal flash performance | Fast and reliable all-flash performance with submillisecond latency. | Run performance-intensive workloads in the cloud with on-premises infrastructure-level performance.
38
38
| Multi-protocol support | Supports multiple protocols, including NFSv3, NFSv4.1, SMB 3.0, SMB 3.1.1, and simultaneous dual-protocol. | Seamlessly integrate with existing infrastructure and workflows without compatibility issues or complex configurations. |
39
-
| Four flexible performance tiers (Standard, Premium, Ultra, Optimum) | Four performance tiers with dynamic service-level change capability based on workload needs, including cool access for cold data. | Choose the right performance level for workloads and dynamically adjust performance without overspending on resources.
39
+
| Four adaptable performance tiers (Standard, Premium, Ultra, Flexible) | Four performance tiers with dynamic service-level change capability based on workload needs, including cool access for cold data. | Choose the right performance level for workloads and dynamically adjust performance without overspending on resources.
40
40
| Small-to-large volumes | Easily resize file volumes from 100 GiB up to 100 TiB without downtime. | Scale storage as business needs grow without over-provisioning, avoiding upfront cost.
41
41
| 1-TiB minimum capacity pool size | 1-TiB capacity pool is a reduced-size storage pool compared to the initial 4-TiB minimum. | Save money by starting with a smaller storage footprint and lower entry point, without sacrificing performance or availability. Scale storage based on growth without high upfront costs.
42
42
| 1,000-TiB maximum capacity pool | 1000-TiB capacity pool is an increased storage pool compared to the initial 500-TiB maximum. | Reduce waste by creating larger, pooled capacity and performance budget, and share and distribute across volumes.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-service-levels.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Service levels are an attribute of a capacity pool. Service levels are defined a
13
13
14
14
## Supported service levels
15
15
16
-
Azure NetApp Files supports three service levels: *Ultra*, *Premium*, and *Standard*.
16
+
Azure NetApp Files supports four service levels: *Standard*, *Premium*, *Ultra*, and *Flexible*.
17
17
18
18
* <aname="Standard"></a>Standard storage:
19
19
The Standard service level provides up to 16 MiB/s of throughput per 1 TiB of capacity provisioned.
@@ -27,13 +27,13 @@ Azure NetApp Files supports three service levels: *Ultra*, *Premium*, and *Stand
27
27
* <aname="Ultra"></a>Ultra storage:
28
28
The Ultra service level provides up to 128 MiB/s of throughput per 1 TiB of capacity provisioned.
29
29
30
-
* <aname="Optimum"></a>Optimum storage:
31
-
The Optimum service level enables you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. The Optimum service level supports throughput values between 128 and 2560 MiB/s per 1 TiB of capacity provisioned.
30
+
* <aname="Flexible"></a>Flexible storage:
31
+
The Flexible service level enables you to adjust throughput and size limits independently for capacity pools using manual QoS. This service level is designed for demanding applications such as Oracle or SAP HANA. The Flexible service level supports throughput values between 128 and 2560 MiB/s per 1 TiB of capacity provisioned.
32
32
33
-
Optimum storage capacity pools enforce single encryption. They do not support double encryption.
33
+
Flexible storage capacity pools enforce single encryption. They do not support double encryption.
34
34
35
35
>[!IMPORTANT]
36
-
>The Optimum service level is only supported for _manual QoS_ capacity pools.
36
+
>The Flexible service level is only supported for _manual QoS_ capacity pools.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,21 +33,21 @@ Creating a capacity pool enables you to create volumes within it.
33
33
34
34
>[!IMPORTANT]
35
35
>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`.
36
-
* If you're using the Optimum service level:
36
+
* If you're using the Flexible service level:
37
37
* Cool access is not currently supported.
38
-
* Only single encryption is currently supported for Optimum service level capacity poools. Double encryption is not currently supported.
39
-
* The Optimum service level is only available for manual QoS capacity pools.
40
-
* To use the **Optimum** service level, you must first register the feature:
38
+
* Only single encryption is currently supported for Flexible service level capacity pools. Double encryption is not currently supported.
39
+
* The Flexible service level is only available for manual QoS capacity pools.
40
+
* To use the **Flexible** service level, you must first register the feature:
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
53
53
@@ -68,10 +68,10 @@ Creating a capacity pool enables you to create volumes within it.
68
68
69
69
* **Service level**
70
70
This field shows the target performance for the capacity pool.
71
-
Specify the service level for the capacity pool: [**Ultra**](azure-netapp-files-service-levels.md#Ultra), [**Premium**](azure-netapp-files-service-levels.md#Premium), [**Standard**],(azure-netapp-files-service-levels.md#Standard) or [**Optimum**](azure-netapp-files-service-levels.md#Optimum).
71
+
Specify the service level for the capacity pool: [**Ultra**](azure-netapp-files-service-levels.md#Ultra), [**Premium**](azure-netapp-files-service-levels.md#Premium), [**Standard**],(azure-netapp-files-service-levels.md#Standard) or [**Flexible**](azure-netapp-files-service-levels.md#Flexible).
72
72
73
73
>[!NOTE]
74
-
>The **Optimum** service level is only supported for manual QoS capacity pools.
74
+
>The **Flexible** service level is only supported for manual QoS capacity pools.
75
75
76
76
* **Size**
77
77
Specify the size of the capacity pool that you're purchasing.
@@ -81,7 +81,7 @@ Creating a capacity pool enables you to create volumes within it.
81
81
>[!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
82
82
83
83
* **Throughput**
84
-
This option is only available for Optimum service level capacity pools. Specify a value between 128 and 2,560 MiB/s.
84
+
This option is only available for Flexible service level capacity pools. Specify a value between 128 and 2,560 MiB/s.
85
85
86
86
* **Enable cool access** *(for Standard service level only)*
87
87
This option specifies whether volumes in the capacity pool support cool access. This option is currently supported for the Standard service level only. For details about using this option, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/performance-large-volumes-linux.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,12 @@ This article describes the tested performance capabilities of a single [Azure Ne
22
22
23
23
## Testing summary
24
24
25
-
* The Azure NetApp Files large volumes feature offers three service levels, each with throughput limits. The service levels can be scaled up or down nondisruptively as your performance needs change.
25
+
* The Azure NetApp Files large volumes feature offers [four service levels](azure-netapp-files-service-levels.md), each with throughput limits. The service levels can be scaled up or down nondisruptively as your performance needs change.
26
26
27
27
* Ultra service level: 10,240 MiB/s
28
28
* Premium service level: 6,400 MiB/s
29
29
* Standard service level: 1,600 MiB/s
30
+
*[Flexible service](azure-netapp-files-service-levels.md#flexible): The Flexible service level enables you to adjust throughput and size limits independently for capacity pools using manual QoS
0 commit comments