Merge pull request #289469 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

articles/azure-netapp-files/TOC.yml

@@ -99,6 +99,8 @@
       href: regional-capacity-quota.md
     - name: Understand default and individual user and group quotas
       href: default-individual-user-group-quotas-introduction.md
+    - name: Understand large volumes 
+      href: large-volumes.md
     - name: Requirements and considerations for large volumes
       href: large-volumes-requirements-considerations.md
   - name: Performance

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -77,7 +77,7 @@ When you use a manual QoS capacity pool with, for example, an SAP HANA system, a
 
 ## Large volumes
 
-Azure NetApp Files allows you to create large volumes up to 1 PiB in size. Large volumes begin at a capacity of 50 TiB and scale up to 1 PiB. Regular Azure NetApp Files volumes are offered between 50 GiB and 102,400 GiB. 
+Azure NetApp Files allows you to create [large volumes](large-volumes.md) up to 1 PiB in size. Large volumes begin at a capacity of 50 TiB and scale up to 1 PiB. Regular Azure NetApp Files volumes are offered between 50 GiB and 102,400 GiB. 
 
 For more information, see [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md).
 
@@ -88,4 +88,5 @@ For more information, see [Requirements and considerations for large volumes](la
 - [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md)
 - [Create a capacity pool](azure-netapp-files-set-up-capacity-pool.md)
 - [Manage a manual QoS capacity pool](manage-manual-qos-capacity-pool.md)
+- [Understand large volumes](large-volumes.md)
 - [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -118,6 +118,7 @@ If this is your first time using large volumes, register the feature with the [l
 
 ## Next steps
 
+* [Understand large volumes](large-volumes.md)
 * [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)
 * [Create an NFS volume](azure-netapp-files-create-volumes.md)

articles/azure-netapp-files/large-volumes.md

@@ -0,0 +1,64 @@
+---
+title: Understand large volumes in Azure NetApp Files 
+description: Learn about the benefits, use cases, and requirements for using large volumes in Azure NetApp Files. 
+services: azure-netapp-files
+author: b-ahibbard
+ms.service: azure-netapp-files
+ms.custom: references_regions
+ms.topic: conceptual
+ms.date: 10/29/2024
+ms.author: anfdocs
+---
+# Understand large volumes in Azure NetApp Files 
+
+Volumes in Azure NetApp Files are the way you present high performance, cost-effective storage to your network attached storage (NAS) clients in the Azure cloud. Volumes act as independent file systems with their own capacity, file counts, ACLs, snapshots, and file system IDs. These qualities provide a way to separate datasets into individual secure tenants.
+
+:::image type="content" source="./media/large-volumes/large-volumes-diagram.png" alt-text="Diagram of large and regular volume size." lightbox="./media/large-volumes/large-volumes-diagram.png":::
+
+All resources in Azure NetApp files have [limits](azure-netapp-files-resource-limits.md). _Regular_ volumes have the following limits: 
+
+| Limit type | Limits | 
+| - | - | 
+| Capacity | <ul><li>50 GiB minimum</li><li>100 TiB maximum</li></ul> |
+| File count | 2,147,483,632 |
+| Performance | <ul><li>Standard: 1,600</li><li>Premium: 1,600</li><li>Ultra: 4,500</li></ul> |
+
+Large volumes have the following limits: 
+
+| Limit type | Values | 
+| - | - | 
+| Capacity | <ul><li>50 TiB minimum</li><li>1 PiB maximum (or [2 PiB by special request](azure-netapp-files-resource-limits.md#request-limit-increase))</li></ul> |
+| File count | 15,938,355,048 |
+| Performance | <ul><li>Standard: 1,600</li><li>Premium: 6,400</li><li>Ultra: 12,800</li></ul> |
+
+
+## Large volumes effect on performance 
+
+In many cases, a regular volume can handle the performance needs for a production workload, particularly when dealing with database workloads, general file shares, and Azure VMware Service or virtual desktop infrastructure (VDI) workloads. When workloads are metadata heavy or require scale beyond what a regular volume can handle, a large volume can increase performance needs with minimal cost impact.
+
+For instance, the following graphs show that a large volume can deliver two to three times the performance at scale of a regular volume.
+
+For more information about performance tests, see [Large volume performance benchmarks for Linux](performance-large-volumes-linux.md) and [Regular volume performance benchmarks for Linux](performance-benchmarks-linux.md).
+
+For example, in benchmark tests using Flexible I/O Tester (FIO), a large volume achieved higher I/OPS and throughput than a regular volume.
+
+:::image type="content" source="./media/large-volumes/large-regular-volume-comparison.png" alt-text="Diagram comparing large and regular volumes with random I/O." lightbox="./media/large-volumes/large-regular-volume-comparison.png":::
+
+:::image type="content" source="./media/large-volumes/large-volume-throughput.png" alt-text="Diagram comparing large and regular volumes with sequential I/O." lightbox="./media/large-volumes/large-volume-throughput.png":::
+
+## Work load types and use cases
+
+Regular volumes can handle most workloads. Once capacity, file count, performance, or scale limits are reached, new volumes must be created. This condition adds unnecessary complexity to a solution.
+
+Large volumes allow workloads to extend beyond the current limitations of regular volumes. The following table shows some examples of use cases for each volume type.
+
+| Volume type | Primary use cases | 
+| - | -- |
+| Regular volumes | <ul><li>General file shares</li><li>SAP HANA and databases (Oracle, SQL Server, Db2, and others)</li><li>VDI/Azure VMware Service</li><li>Capacities less than 50 TiB</li></ul> |
+| Large volumes | <ul><li>General file shares</li><li>High file count or high metadata workloads (such as electronic design automation, software development, FSI)</li><li>High capacity workloads (such as AI/ML/LLP, oil & gas, media, healthcare images, backup, and archives)</li><li>Large-scale workloads (many client connections such as FSLogix profiles)</li><li>High performance workloads</li><li>Capacity quotas between 50 TiB and 1 PiB</li></ul> |
+
+## More information
+
+* [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)
+* [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
+* [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)

articles/azure-netapp-files/media/large-volumes/large-regular-volume-comparison.png

@@ -492,7 +492,15 @@ In the following tables, the term alphanumeric refers to:
 > | scheduledQueryRules | resource group | 1-260 | Can't use:<br>`*<>%{}&:\\?/#|` or control characters <br><br>Can't end with space or period.  |
 > | metricAlerts | resource group | 1-260 | Can't use:<br>`*#&+:<>?@%{}\/|` or control characters <br><br>Can't end with space or period.  |
 > | activityLogAlerts | resource group | 1-260 | Can't use:<br>`<>*%{}&:\\?+/#|` or control characters <br><br>Can't end with space or period.  |
-> | PrometheusAlerts | resource group | 1-260 | Can't use:<br>`<>*%{}&:\\?+/#|` or control characters <br><br>Can't end with space or period.  |
+
+## Microsoft.AlertsManagement 
+
+> [!div class="mx-tableFixed"]
+> | Entity | Scope | Length | Valid Characters |
+> | --- | --- | --- | --- |
+> | prometheusRuleGroups  | resource group | 1-260 | Can't use:<br>`<>*%{}&:\\?+/#|` or control characters <br><br>Can't end with space or period.  |
+
+
 
 ## Microsoft.IoTCentral
 

articles/azure-netapp-files/media/large-volumes/large-volume-throughput.png

@@ -1,7 +1,7 @@
 ---
 title: Regulatory Compliance details for Australian Government ISM PROTECTED
 description: Details of the Australian Government ISM PROTECTED Regulatory Compliance built-in initiative. Each control is mapped to one or more Azure Policy definitions that assist with assessment.
-ms.date: 10/21/2024
+ms.date: 10/30/2024
 ms.topic: sample
 ms.custom: generated
 ---

articles/azure-netapp-files/media/large-volumes/large-volumes-diagram.png

@@ -1,7 +1,7 @@
 ---
 title: Regulatory Compliance details for Microsoft cloud security benchmark
 description: Details of the Microsoft cloud security benchmark Regulatory Compliance built-in initiative. Each control is mapped to one or more Azure Policy definitions that assist with assessment.
-ms.date: 10/21/2024
+ms.date: 10/30/2024
 ms.topic: sample
 ms.custom: generated
 ---