You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-requirements-considerations.md
+1-24Lines changed: 1 addition & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: conceptual
8
-
ms.date: 09/12/2024
8
+
ms.date: 02/13/2025
9
9
ms.author: anfdocs
10
10
---
11
11
@@ -37,29 +37,6 @@ This article describes requirements and considerations about [using the volume c
37
37
*[Large volumes](large-volumes-requirements-considerations.md) are supported with cross-region replication only with an hourly or daily replication schedule.
38
38
* If the volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail depending on the rate of data changes.
39
39
40
-
## Large volumes configuration
41
-
42
-
[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported with cross-region replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-region replication:
43
-
44
-
>[!NOTE]
45
-
>Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-zone replication, the registration also works for cross-region replication.
46
-
47
-
1. Register the feature by running the following commands:
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md
+1-24Lines changed: 1 addition & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-ahibbard
6
6
ms.service: azure-netapp-files
7
7
ms.topic: conceptual
8
-
ms.date: 07/30/2024
8
+
ms.date: 02/13/2025
9
9
ms.author: anfdocs
10
10
---
11
11
# Requirements and considerations for using cross-zone replication
@@ -33,29 +33,6 @@ This article describes requirements and considerations about [using the volume c
33
33
* Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
34
34
*[Large volumes](large-volumes-requirements-considerations.md) are supported with cross-zone replication only with an hourly or daily replication schedule.
35
35
36
-
## Large volumes configuration
37
-
38
-
[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported in cross-zone replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-zone replication:
39
-
40
-
>[!NOTE]
41
-
>Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-region replication, the registration also works for cross-zone replication.
42
-
43
-
1. Register the feature by running the following commands:
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
0 commit comments