Skip to content

Commit 5422e8f

Browse files
authored
Merge pull request #108450 from ASchwarz1984/patch-1
Update faq-data-migration-protection.md
2 parents 5dfb7ea + e81df96 commit 5422e8f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-netapp-files/faq-data-migration-protection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ You can also use a wide array of free tools to copy data. For NFS, you can use w
4545

4646
The requirements for replicating an Azure NetApp Files volume to another Azure region are as follows:
4747
- Ensure Azure NetApp Files is available in the target Azure region.
48-
- Validate network connectivity between VNets in each region. Currently, global peering between VNets is not supported. You can establish connectivity between VNets by linking with an ExpressRoute circuit or using a S2S VPN connection.
48+
- Validate network connectivity between the source and the Azure NetApp Files target volume IP address. Data transfer between on premises and Azure NetApp Files volumes, or across Azure regions, is supported via [site-to-site VPN and ExpressRoute](azure-netapp-files-network-topologies.md#hybrid-environments), [Global VNet peering](azure-netapp-files-network-topologies.md#global-or-cross-region-vnet-peering), or [Azure Virtual WAN connections](configure-virtual-wan.md).
4949
- Create the target Azure NetApp Files volume.
5050
- Transfer the source data to the target volume by using your preferred file copy tool.
5151

0 commit comments

Comments
 (0)