large volume support for czr & crr

Author: b-ahibbard

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

@@ -76,8 +76,12 @@ Cross-region replication supports three replication schedules: 10 minutes, hourl
 * 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.  
 
+>[IMPORTANT]
+>[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-region replication do not support the 10-minute replication schedule. 
+
 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-region replication  
 
 With Azure NetApp Files cross-region replication, you pay only for the amount of data you replicate. There's no setup charge or minimum usage fee. The replication price is based on the replication frequency and the region of the *destination* volume you choose during the initial replication configuration. For more information, see the [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/) page.  

articles/azure-netapp-files/cross-region-replication-requirements-considerations.md

@@ -31,6 +31,7 @@ This article describes requirements and considerations about [using the volume c
 * You can revert a source or destination volume of a cross-region replication to a snapshot, provided the snapshot is newer than the most recent SnapMirror snapshot. Snapshots older than the SnapMirror snapshot can't be used for a volume revert operation. For more information, see [Revert a volume using snapshot revert](snapshots-revert-volume.md). 
 * Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
 * If you use the cool access feature, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md#considerations) for more considerations.
+* [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-region replication only with an hourly or daily replication schedule.
 
 ## Next steps
 * [Create volume replication](cross-region-replication-create-peering.md)

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

@@ -60,6 +60,9 @@ Cross-zone replication supports three replication schedules: 10 minutes, hourly,
 * 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. 
 
+>[IMPORTANT]
+>[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) for cross-zone replication do not support the 10-minute replication schedule. 
+
 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 

articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md

@@ -32,8 +32,7 @@ This article describes requirements and considerations about [using the volume c
 * You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You cannot delete manual snapshots for the destination volume until you break the replication relationship.
 * When reverting a source volume with an active volume replication relationship, only snapshots that are more recent than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
 * Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
-* You can't currently use cross-zone replication with [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes).
-
+* [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-zone replication only with an hourly or daily replication schedule.
 
 ## Next steps
 * [Understand cross-zone replication](cross-zone-replication-introduction.md)

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

@@ -27,8 +27,6 @@ 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 cannot be resized to less than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits).
 * Large volumes are currently not supported with Azure NetApp Files backup.
-* Large volumes aren't currently supported with cross-region replication.
-* Large volumes aren't currently supported with cross-zone replication.
 * 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.
 * Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to 500 TiB with the throughput ceiling per the following table:  

articles/azure-netapp-files/whats-new.md

@@ -18,6 +18,8 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Large volumes](large-volumes-requirements-considerations.md) are now generally available (GA).
 
+    Cross-zone replication and cross-region replication now support large volumes. 
+
 * [Support for one Active Directory connection per NetApp account](create-active-directory-connections.md#multi-ad) (Preview)
 
     The Azure NetApp Files support for one Active Directory (AD) connection per NetApp account feature now allows each NetApp account to connect to its own AD Forest and Domain, providing the ability to manage more than one AD connections within a single region under a subscription. This enhancement enables distinct AD connections for each NetApp account, facilitating operational isolation and specialized hosting scenarios. AD connections can be configured multiple times for multiple NetApp accounts to make use of it. With the creation of SMB volumes in Azure NetApp Files now tied to AD connections in the NetApp account, the management of AD environments becomes more scalable, streamlined and efficient. This feature is in preview.