Merge pull request #291934 from b-ahibbard/backup-large-vol

large volume backup PUBLIC PREVIEW

Author: prmerger-automator[bot]

articles/azure-netapp-files/backup-configure-manual.md

@@ -23,7 +23,7 @@ After you assign a backup vault, you can choose to manually back up a volume. A
 
 The following list summarizes manual backup behaviors:  
 
-* You can create manual backups on a volume even if the volume is already assigned to a backup vault and configured with backup policies.  However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup is blocked until the baseline transfer is complete.
+* You can create manual backups on a volume even if the volume is already assigned to a backup vault and configured with backup policies. However, there can be only one outstanding manual-backup request for the volume. If you assign a backup policy and if the baseline transfer is still in progress, then the creation of a manual backup is blocked until the baseline transfer is complete.
 
 * Unless you specify an existing snapshot to use for a backup, creating a manual backup automatically generates a snapshot on the volume. The snapshot is then transferred to Azure storage. The snapshot created on the volume will be retained until the next manual backup is created. During the subsequent manual backup operation, older snapshots are cleaned up. You can't delete the snapshot generated for the latest manual backup. 
 

articles/azure-netapp-files/backup-introduction.md

@@ -1,5 +1,5 @@
 ---
-title: Understand Azure NetApp Files backup | Microsoft Docs
+title: Understand Azure NetApp Files backup
 description: Describes what Azure NetApp Files backup does, supported regions, and the cost model.
 services: azure-netapp-files
 author: b-hchen
@@ -86,11 +86,11 @@ As a pricing example, assume the following situations:
 * Your source volume is from the Azure NetApp Files Premium service level. It has a volume quota size of 1000 GiB and a volume consumed size of 500 GiB at the beginning of the first day of a month. The volume is in the US South Central region.
 * For simplicity, assume your source volume has a constant 1% data change every day, but the total volume consumed size doesn't grow (remains at 500 GiB).
 
-When the backup policy is assigned to the volume, the baseline backup to service-managed Azure storage is initiated. When the backup is complete, the baseline backup of 500 GiB will be added to the backup list of the volume. After the baseline transfer, daily backups only back up changed blocks. Assume 5-GiB daily incremental backups added, the total backup storage consumed would be `500GiB + 30*5GiB = 650GiB`.
+When the backup policy is assigned to the volume, the baseline backup to service-managed Azure storage is initiated. When the backup is complete, the baseline backup of 500 GiB is added to the backup list of the volume. After the baseline transfer, daily backups only back up changed blocks. Assume 5-GiB daily incremental backups added, the total backup storage consumed is `500GiB + 30*5GiB = 650GiB`.
 
-You'll be billed at the end of month for backup at the rate of $0.05 per month for the total amount of storage consumed by the backup.  That is, 650 GiB with a total monthly backup charge of `650*$0.05=$32.5`. Regular Azure NetApp Files storage capacity applies to local snapshots. For more information, see the [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/) page.
+You're billed at the end of month for backup at the rate of $0.05 per month for the total amount of storage consumed by the backup. That is, 650 GiB with a total monthly backup charge of `650*$0.05=$32.5`. Regular Azure NetApp Files storage capacity applies to local snapshots. For more information, see the [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/) page.
 
-If you choose to restore a backup of, for example, 600 GiB to a new volume, you'll be charged at the rate of $0.02 per GiB of backup capacity restores. In this case, it will be `600*$0.02 = $12` for the restore operation. 
+If you choose to restore a backup of, for example, 600 GiB to a new volume, you're charged at the rate of $0.02 per GiB of backup capacity restores. In this case, it's `600*$0.02 = $12` for the restore operation. 
 
 ## Next steps
 

articles/azure-netapp-files/backup-requirements-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 07/28/2025
+ms.date: 08/19/2025
 ms.author: anfdocs
 ms.custom:
   - build-2025
@@ -23,9 +23,10 @@ You need to be aware of several requirements and considerations before using Azu
 >All backups require a backup vault. If you have existing backups, you must migrate backups to a backup vault before you can perform any operation with a backup. For more information, see [Manage backup vaults](backup-vault-manage.md).
 
 * Azure NetApp Files backup is available in the regions associated with your Azure NetApp Files subscription. 
-Azure NetApp Files backup in a region can only protect an Azure NetApp Files volume located in that same region. For example, backups created by the service in West US 2 for a volume located in West US 2 are sent to Azure storage also located in West US 2. Azure NetApp Files doesn't support backups or backup replication to a different region.  
 
-* There can be a delay of up to 5 minutes in displaying a backup after the backup is actually completed.
+  Azure NetApp Files backup in a region can only protect an Azure NetApp Files volume located in that same region. For example, backups created by the service in West US 2 for a volume located in West US 2 are sent to Azure storage also located in West US 2. Azure NetApp Files doesn't support backups or backup replication to a different region.  
+
+* There can be a delay of up to five minutes in displaying a backup after the backup is actually completed.
 
 * For volumes larger than 10 TiB, it can take multiple hours to transfer all the data from the backup media.
 
@@ -49,9 +50,11 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
 
 * If you delete a volume, the backups remain. If you no longer need the backups, you should [manually delete the backups](backup-delete.md).
 
-* If you need to delete a parent resource group or subscription that contains backups, you should delete any backups first. Deleting the resource group or subscription doesn't delete the backups.
+* If you need to delete a parent resource group or subscription that contains backups, delete any backups first. Deleting the resource group or subscription doesn't delete the backups.
+
+* Azure NetApp Files backups are supported with large volumes. To create a backup of an Azure NetApp Files large volume, you must be registered to use [large volumes](large-volumes-requirements-considerations.md#register-the-feature).
 
-* If the volume reaches its maximum quota, backup creation can fail depending on the quantity of data changes to the volume. If the backup fails, increase the size of the volume then wait for the next scheduled backup. 
+* If the volume reaches its maximum quota, backup creation can fail depending on the amount of data changed. If the backup fails, increase the size of the volume then wait for the next scheduled backup. 
 
 ## Next steps
 

articles/azure-netapp-files/backup-restore-new-volume.md

@@ -1,17 +1,17 @@
 ---
-title: Restore a backup to a new Azure NetApp Files volume | Microsoft Docs
+title: Restore a backup to a new Azure NetApp Files volume
 description: Describes how to restore a backup to a new volume.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 04/07/2025
+ms.date: 08/19/2025
 ms.author: anfdocs
 # Customer intent: As a cloud administrator, I want to restore a backup to a new volume in Azure NetApp Files, so that I can recover data without affecting existing volumes while ensuring proper capacity and protocol settings are maintained.
 ---
 # Restore a backup to a new volume
 
-Restoring a backup creates a new volume with the same protocol type. This article explains the restore operation. 
+When you restore a backup, a new volume is created using the same protocol type as the original. This article explains how to perform a restore.
 
 ## Considerations
 
@@ -27,6 +27,8 @@ Restoring a backup creates a new volume with the same protocol type. This articl
 
 * For volumes greater than 10 TiB, it can take multiple hours to transfer all the data from the backup media.
 
+* When restoring a [large volume](large-volumes.md), the new volume must also be a large volume. When restoring a regular volume, the new volume must also be a regular volume. 
+
 * Restoring a backup to a new volume isn't dependent on the networking type used by the source volume. You can restore the backup of a volume configured with Basic networking to a volume configured with Standard networking and vice versa.
 
 * In the Volume overview page, refer to the **Originated from** field to see the name of the snapshot used to create the volume. 
@@ -35,7 +37,7 @@ Restoring a backup creates a new volume with the same protocol type. This articl
 
 
 > [!IMPORTANT]
-> Running multiple concurrent volume restores using Azure NetApp Files backup may increase the time it takes for each individual, in-progress restore to complete. I time is a factor, prioritize and sequentialize the most important volume restores and wait until the restores are complete before starting other, lower priority volume restores.  
+> Running multiple concurrent volume restores using Azure NetApp Files backup may increase the time it takes for each individual, in-progress restore to complete. If time is a factor, prioritize and sequentialize the most important volume first. Wait until the restore operations complete before starting lower priority volume restores.  
 
 See [Requirements and considerations for Azure NetApp Files backup](backup-requirements-considerations.md) for more considerations about using Azure NetApp Files backup. See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md) for information about minimums and maximums. 
 
@@ -45,23 +47,22 @@ See [Requirements and considerations for Azure NetApp Files backup](backup-requi
 >All backups must be migrated to backup vaults. You are unable to perform any operation on or with a backup until you have migrated the backup to a backup vault. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
 
 1. Select **Backup Vault**. Navigate to **Backups**.
-<!-- 
-    > [!NOTE]
-    > If a volume is deleted but the backup policy wasn’t disabled before the volume deletion, all the backups related to the volume are retained in the Azure storage, and you can find them under the associated NetApp account. -->
 
 2. From the backup list, select the backup to restore. Select the three dots (`…`) to the right of the backup, then select **Restore to new volume** from the Action menu.   
 
     :::image type="content" source="./media/backup-restore-new-volume/backup-restore-new-volume.png" alt-text="Screenshot of selecting restore backup to new volume." lightbox="./media/backup-restore-new-volume/backup-restore-new-volume.png":::
 
-3. In the Create a Volume page that appears, provide information for the fields in the page as applicable, and select **Review + Create** to begin restoring the backup to a new volume.   
+3. In the Create a Volume page, provide information for the fields in the page as applicable. 
 
     * The **Protocol** field is pre-populated from the original volume and cannot be changed.    
-        However, if you restore a volume from the backup list at the NetApp account level, you need to specify the Protocol field. The Protocol field must match the protocol of the original volume. Otherwise, the restore operation fails with the following error:  
+        If you restore a volume from the backup list at the NetApp account level, you must specify the protocol. The **Protocol** field must match the protocol of the original volume. Otherwise, the restore operation fails with the following error:  
         `Protocol Type value mismatch between input and source volume of backupId <backup-id of the selected backup>. Supported protocol type : <Protocol Type of the source volume>`
 
     * The **Quota** value must be **at least 20% greater** than the size of the backup from which the restore is triggered. Once the restore is complete, the volume can be resized depending on the size used. 
 
-    * The **Capacity pool** that the backup is restored into must have sufficient unused capacity to host the new restored volume. Otherwise, the restore operation fails.   
+    * The **Capacity pool** that the backup is restored into must have sufficient unused capacity to host the new restored volume. Otherwise, the restore operation fails.
+
+    Select **Review + Create** to begin restoring the backup to a new volume.
 
     ![Screenshot that shows the Create a Volume page.](./media/backup-restore-new-volume/backup-restore-create-volume.png)
 

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

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: concept-article
-ms.date: 07/18/2025
+ms.date: 08/19/2025
 ms.author: anfdocs
 # Customer intent: As a storage administrator, I want to review the requirements and limitations of large volumes in Azure NetApp Files, so that I can effectively plan the deployment and management of storage solutions to meet my organization's data capacity and performance needs.
 ---
@@ -23,10 +23,9 @@ The following requirements and considerations apply to large volumes. For perfor
 * You can't resize a large volume to less than 50 TiB.
     * A large volume can't be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the desired size in TiB. 
     * When reducing the size of a large volume, the size you can decrease to depends on the size of files written to the volume and the snapshots currently active on the volumes. 
-* Large volumes are currently not supported with Azure NetApp Files backup.
 * You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).
-*	The throughput ceiling for the Standard, Premium, and Ultra service levels with large volumes is 12,800 MiB/s. You're able to grow to 1 PiB with the throughput ceiling per the following table:  
+*	The throughput ceiling for the Standard, Premium, and Ultra service levels with large volumes is 12,800 MiB/s. You can grow a large volume to 1 PiB with the throughput ceiling per the following table:  
 
     <table><thead>
       <tr>
@@ -70,8 +69,7 @@ The following requirements and considerations apply to large volumes. For perfor
 
     For the latest performance benchmark numbers conducted on Azure NetApp Files Large volumes, see [Azure NetApp Files large volume performance benchmarks for Linux](performance-large-volumes-linux.md) and [Benefits of using Azure NetApp Files for Electronic Design Automation (EDA)](solutions-benefits-azure-netapp-files-electronic-design-automation.md).
 
-
-* Large volumes are supported with cool access. You must be [registered to use cool access](manage-cool-access.md#register-the-feature) before creating a cool access-enabled large volume. 
+* Cool access is supported with large volumes. You must be [registered to use cool access](manage-cool-access.md#register-the-feature) before creating a cool access-enabled large volume. 
 
 ## About 64-bit file IDs
 
@@ -129,7 +127,7 @@ Support for Azure NetApp Files large volumes is available in the following regio
 >[!IMPORTANT]
 >Before you can use large volumes, you must first request [an increase in regional capacity quota](azure-netapp-files-resource-limits.md#request-limit-increase).
 
-Once your [regional capacity quota](regional-capacity-quota.md) has increased, you can create volumes that are up to 1 PiB in size. When creating a volume, after you designate the volume quota, you must select **Yes** for the **Large volume** field. Once created, you can manage your large volumes in the same manner as regular volumes. 
+Once your [regional capacity quota](regional-capacity-quota.md) has increased, you can create volumes up to 1 PiB. When creating a volume, after you designate the volume quota, you must select **Yes** for the **Large volume** field. Once created, you can manage your large volumes in the same manner as regular volumes. 
 
 ### Register the feature 
 

articles/azure-netapp-files/snapshots-restore-file-single.md

@@ -1,11 +1,11 @@
 ---
-title: Restore individual files in Azure NetApp Files using single-file snapshot restore | Microsoft Docs
+title: Restore individual files in Azure NetApp Files using single-file snapshot restore
 description: Describes how to recover individual files directly within a volume from a snapshot.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 01/28/2025
+ms.date: 06/23/2025
 ms.author: anfdocs
 # Customer intent: "As an IT administrator, I want to restore individual files from a snapshot in Azure NetApp Files, so that I can quickly recover specific data without the need for entire volume restoration."
 ---