Skip to content

Commit 7652053

Browse files
Fix date and volume capacity details in migration guide
Updated the date and corrected the volume capacity description for Azure NetApp Files migration.
1 parent bce6c02 commit 7652053

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 09/09/2025
8+
ms.date: 10/22/2025
99
ms.author: anfdocs
1010
---
1111
# Migrate volumes to Azure NetApp Files
@@ -74,7 +74,7 @@ The network connectivity must be in place for all intercluster (IC) LIFs on the
7474
>[!IMPORTANT]
7575
>Ensure the size and other volume properties on the target volumes match with the source.
7676
>
77-
>You should create the Azure NetApp Files volume with 20% or more quota than the source volume. Azure NetApp Files volumes use raw capacity size. The source volume might be smaller due to deduplication and compression. You can shrink Azure NetApp Files nondisruptively after the migration to prevent over-provisioning.
77+
>You should create the Azure NetApp Files volume with 20% or more quota than the source volume. Azure NetApp Files volumes use logical capacity size. The source volume might be smaller due to deduplication and compression. For correct Azure NetApp Files volume sizing, use the logical space reported by the volume you are migrating. You can shrink Azure NetApp Files nondisruptively after the migration to prevent over-provisioning.
7878
7979
The "remote path" values are the host, server, and volume names of your on-premises storage.
8080

0 commit comments

Comments
 (0)