Merge pull request #221747 from b-ahibbard/anf-16dec

issue #102790. south africa north to czr

Author: liljack17

articles/azure-netapp-files/cross-zone-replication-introduction.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 12/15/2022
+ms.date: 12/16/2022
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -23,22 +23,6 @@ In many cases resiliency across availability zones is achieved by HA architectur
 
 Similar to the Azure NetApp Files [cross-region replication feature](cross-region-replication-introduction.md), the cross-zone replication (CZR) capability provides data protection between volumes in different availability zones. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one availability zone to another Azure NetApp Files volume (destination) in another availability. This capability enables you to fail over your critical application if a zone-wide outage or disaster happens. 
 
-## Service-level objectives 
-
-Recovery Point Objective (RPO) indicates the point in time to which data can be recovered. The RPO target is typically less than twice the replication schedule, but it can vary. In some cases, it can go beyond the target RPO based on factors such as the total dataset size, the change rate, the percentage of data overwrites, and the replication bandwidth available for transfer. 
-
-* For the replication schedule of 10 minutes, the typical RPO is less than 20 minutes. 
-
-* For the hourly replication schedule, the typical RPO is less than two hours. 
-
-* For the daily replication schedule, the typical RPO is less than two days. 
-
-Recovery Time Objective (RTO), or the maximum tolerable business application downtime, is determined by factors in bringing up the application and providing access to the data at the second site. The storage portion of the RTO for breaking the peering relationship to activate the destination volume and provide read and write data access in the second site is expected to be complete within a minute. 
-
-## Cost model for cross-zone replication 
-
-Replicated volumes are hosted on a [capacity pool](azure-netapp-files-understand-storage-hierarchy.md#capacity_pools). As such, the cost for cross-zone replication is based on the provisioned capacity pool size and tier as normal. There is no additional cost for data replication.
-
 ## Supported regions
 
 The preview of cross-zone replication is available in the following regions: 
@@ -55,6 +39,7 @@ The preview of cross-zone replication is available in the following regions:
 * Japan East
 * North Europe
 * Norway East 
+* South Africa North
 * Southeast Asia
 * South Central US 
 * UK South
@@ -64,6 +49,22 @@ The preview of cross-zone replication is available in the following regions:
 
 In the future, cross-zone replication is planned for all [AZ-enabled regions](../availability-zones/az-overview.md#azure-regions-with-availability-zones) with [Azure NetApp Files presence](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&regions=all&rar=true).
 
+## Service-level objectives 
+
+Recovery Point Objective (RPO) indicates the point in time to which data can be recovered. The RPO target is typically less than twice the replication schedule, but it can vary. In some cases, it can go beyond the target RPO based on factors such as the total dataset size, the change rate, the percentage of data overwrites, and the replication bandwidth available for transfer. 
+
+* For the replication schedule of 10 minutes, the typical RPO is less than 20 minutes. 
+
+* For the hourly replication schedule, the typical RPO is less than two hours. 
+
+* For the daily replication schedule, the typical RPO is less than two days. 
+
+Recovery Time Objective (RTO), or the maximum tolerable business application downtime, is determined by factors in bringing up the application and providing access to the data at the second site. The storage portion of the RTO for breaking the peering relationship to activate the destination volume and provide read and write data access in the second site is expected to be complete within a minute. 
+
+## Cost model for cross-zone replication 
+
+Replicated volumes are hosted on a [capacity pool](azure-netapp-files-understand-storage-hierarchy.md#capacity_pools). As such, the cost for cross-zone replication is based on the provisioned capacity pool size and tier as normal. There is no additional cost for data replication.
+
 ## Next steps
 
 * [Requirements and considerations for using cross-zone replication](cross-zone-replication-requirements-considerations.md)

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

@@ -6,18 +6,18 @@ ms.workload: storage
 ms.topic: conceptual
 author: b-hchen
 ms.author: anfdocs
-ms.date: 10/11/2021
+ms.date: 12/16/2022
 ---
 # Data migration and protection FAQs for Azure NetApp Files
 
 This article answers frequently asked questions (FAQs) about Azure NetApp Files data migration and protection.
 
 ## How do I migrate data to Azure NetApp Files?
-Azure NetApp Files provides NFS and SMB volumes.  You can use any file-based copy tool to migrate data to the service. 
+Azure NetApp Files provides NFS and SMB volumes. You can use any file-based copy tool to migrate data to the service. 
 
-NetApp offers a SaaS-based solution, [NetApp Cloud Sync](https://cloud.netapp.com/cloud-sync-service).  The solution enables you to replicate NFS or SMB data to Azure NetApp Files NFS exports or SMB shares. 
+NetApp offers a SaaS-based solution, [NetApp Cloud Sync](https://cloud.netapp.com/cloud-sync-service). The solution enables you to replicate NFS or SMB data to Azure NetApp Files NFS exports or SMB shares. 
 
-You can also use a wide array of free tools to copy data. For NFS, you can use workloads tools such as [rsync](https://rsync.samba.org/examples.html) to copy and synchronize source data into an Azure NetApp Files volume. For SMB, you can use workloads [robocopy](/windows-server/administration/windows-commands/robocopy) in the same manner.  These tools can also replicate file or folder permissions. 
+You can also use a wide array of free tools to copy data. For NFS, you can use workloads tools such as [rsync](https://rsync.samba.org/examples.html) to copy and synchronize source data into an Azure NetApp Files volume. For SMB, you can use workloads [robocopy](/windows-server/administration/windows-commands/robocopy) in the same manner. These tools can also replicate file or folder permissions. 
 
 The requirements for data migration from on premises to Azure NetApp Files are as follows: 
 
@@ -26,6 +26,9 @@ The requirements for data migration from on premises to Azure NetApp Files are a
 - Create the target Azure NetApp Files volume.
 - Transfer the source data to the target volume by using your preferred file copy tool.
 
+>[!NOTE]
+>[AzCopy](../storage/common/storage-use-azcopy-v10.md) can only be used in migration scenarios where the source or target is a storage account. Azure NetApp Files is not a storage account.
+
 ## Where does Azure NetApp Files store customer data?   
 
 By default, your data stays within the region where you deploy your Azure NetApp Files volumes. However, you can choose to replicate your data on a volume-by-volume basis to available destination regions using [cross-region replication](cross-region-replication-introduction.md).