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/includes/region-pairs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.custom: include file, references_regions
9
9
# azure-netapp-files/replication.md
10
10
# Customer intent: As a cloud architect, I want to understand Azure NetApp Files volume replication across different regional pairs, so that I can plan and implement resilient data storage solutions for multi-region applications.
11
11
---
12
-
Azure NetApp Files volume replication is supported between various [Azure regional pairs](../../reliability/cross-region-replication-azure.md#paired-regions) and nonstandard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B, and vice versa.
12
+
Azure NetApp Files volume replication is supported between various [Azure regional pairs](../../reliability/cross-region-replication-azure.md#paired-regions) and nonstandard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B and from Regional Pair B to Regional Pair A.
13
13
14
14
### Azure regional pairs
15
15
@@ -68,5 +68,5 @@ Azure NetApp Files volume replication is supported between various [Azure region
68
68
| UK/Europe | UK South | North Europe |
69
69
| US Government | US Gov Arizona | US Gov Virginia |
70
70
71
-
>[!NOTE]
72
-
>There can be a discrepancy in the size and number of snapshots between the source and the destination. This discrepancy is expected. Snapshot policies and replication schedules influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data that changes between snapshots, influence the size of snapshots. For more information, see [How Azure NetApp Files snapshots work](../snapshots-introduction.md).
71
+
>[!NOTE]
72
+
>There can be a discrepancy in the size and number of snapshots between the source and the destination. This discrepancy is expected. Snapshot policies and replication schedules influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data that changes between snapshots, influence the size of snapshots. For more information, see [How Azure NetApp Files snapshots work](../snapshots-introduction.md).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/manage-availability-zone-volume-placement.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,8 @@ You can deploy new volumes in the logical availability zone of your choice. You
33
33
34
34
* <aname="file-path-uniqueness"></a> For volumes in different availability zones, Azure NetApp Files allows you to create volumes with the same file path (NFS), share name (SMB), or volume path (dual-protocol).
35
35
36
-
>[!IMPORTANT]
37
-
>We don't recommend that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).
36
+
>[!IMPORTANT]
37
+
>We don't recommend that you use availability zones for Terraform-managed volumes. If you do, you must [add the zone property to your volume](#populate-availability-zone-for-terraform-managed-volumes).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/replication-requirements.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Requirements and Considerations for Azure NetApp Files Replication
3
-
description: Understand the considerations and individual and shared requirements to configure Azure NetApp Files cross-zone and cross-region replication.
3
+
description: Understand the considerations and individual and shared requirements for configuring Azure NetApp Files cross-zone and cross-region replication.
4
4
services: azure-netapp-files
5
5
author: b-ahibbard
6
6
ms.service: azure-netapp-files
@@ -11,7 +11,7 @@ ms.custom: references_regions
11
11
---
12
12
# Requirements and considerations for Azure NetApp Files replication
13
13
14
-
Before you configure [cross-zone or cross-region replication](replication.md), understand the requirements for each.
14
+
Before you configure [cross-zone or cross-region replication](replication.md), make sure that you understand the requirements for each option.
15
15
16
16
If you use [cross-zone-region replication](replication.md#cross-zone-region-replication), you must adhere to all the requirements.
17
17
@@ -27,7 +27,7 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
27
27
28
28
* Consult [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of destination volumes that you can create. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes for each subscription in a region.
29
29
30
-
* Cascading and fan-in topologies aren't supported. To learn about support for fan-out deployments, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md#requirements).
30
+
* Cascading and fan-in topologies aren't supported. To learn about support for fan-out deployments, see [Configure cross-zone-region replication](cross-zone-region-replication-configure.md#requirements).
31
31
32
32
* Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
33
33
@@ -49,8 +49,8 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
49
49
50
50
* The destination volume is read-only until you fail over to the destination zone to enable the destination volume for read and write. For more information about the failover process, see [Fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
51
51
52
-
>[!IMPORTANT]
53
-
>Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you first need to break replication peering and then mount the destination volume. For more information, see [Fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
52
+
>[!IMPORTANT]
53
+
>Failover is a manual process. When you need to activate the destination volume (like when you want to fail over to the destination region), you first need to break replication peering and then mount the destination volume. For more information, see [Fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
54
54
55
55
* When you revert a source volume that has an active volume replication relationship, only snapshots dated more recently than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume by using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
56
56
@@ -62,10 +62,10 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
62
62
63
63
* The replication destination volume is read-only until you [fail over to the destination region](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume) to enable the destination volume for read and write.
64
64
65
-
>[!IMPORTANT]
66
-
>Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering and then mount the destination volume. For more information, see [Fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
65
+
>[!IMPORTANT]
66
+
>Failover is a manual process. When you need to activate the destination volume (like when you want to fail over to the destination region), you need to break replication peering and then mount the destination volume. For more information, see [Fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
67
67
68
-
>[!IMPORTANT]
68
+
>[!IMPORTANT]
69
69
> A volume that has an active backup policy enabled can't be the destination volume in a reverse resync operation. You must suspend the backup policy on the volume before you start the reverse resync. You can resume the backup policy when the reverse resync completes.
70
70
71
71
* You can revert a source or destination volume of a cross-region replication to a snapshot if the snapshot is newer than the most recent SnapMirror snapshot. You can't use snapshots that are older than the SnapMirror snapshot for a volume revert operation. For more information, see [Revert a volume by using snapshot revert](snapshots-revert-volume.md).
@@ -82,7 +82,7 @@ If you use [cross-zone-region replication](replication.md#cross-zone-region-repl
82
82
83
83
* If you use the cool access feature, understand the considerations in [Manage Azure NetApp Files storage with cool access](manage-cool-access.md#considerations).
84
84
85
-
* 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.
85
+
* 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.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/replication.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,12 +28,12 @@ Azure NetApp Files supports cross-zone replication, which relies on availability
28
28
Azure [availability zones](../reliability/availability-zones-overview.md) are physically separate locations within each supporting Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Redundancy and logical isolation of Azure services achieve this tolerance to failures. To ensure resiliency, a minimum of three separate availability zones are present in all [availability zone-enabled regions](../reliability/regions-list.md).
29
29
30
30
>[!IMPORTANT]
31
-
> Availability zones are called _logical zones_. Each datacenter is assigned to a physical zone. [Physical zones are mapped to logical zones in your Azure subscription](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones), and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription.
31
+
> Availability zones are known as *logical zones*. Each datacenter is assigned to a physical zone. [Physical zones are mapped to logical zones in your Azure subscription](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones), and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription.
32
32
33
33
To learn more about availability zones in Azure NetApp Files, see [Reliability in Azure NetApp Files](../reliability/reliability-netapp-files.md).
34
34
35
-
>[!IMPORTANT]
36
-
>We don't recommend that you use availability zones with Terraform-managed volumes. If you do, you must [add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
35
+
>[!IMPORTANT]
36
+
>We don't recommend that you use availability zones with Terraform-managed volumes. If you do, you must [add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
37
37
38
38
#### Azure regions with availability zones
39
39
@@ -65,11 +65,11 @@ For more information about SLOs, see [Azure NetApp Files reliability](../reliabi
65
65
66
66
When you use Azure NetApp Files cross-region replication, you pay only for the amount of data that 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 that you choose during the initial replication configuration. For more information, see [Azure NetApp Files pricing](https://azure.microsoft.com/pricing/details/netapp/).
67
67
68
-
Regular Azure NetApp Files storage capacity charges apply to the replication destination volume, also called the *data protection* volume.
68
+
Regular Azure NetApp Files storage capacity charges apply to the replication destination volume, also known as the *data protection* volume.
69
69
70
70
#### Pricing examples
71
71
72
-
The cross-region replication amount that's billed in a month is based on the amount of data that's replicated through the cross-region replication feature during that month. The amount of replicated data is measured in GiB. It represents the sum of data that's replicated across two regions during all regular replications from the source volumes to the destination volumes and during all resync replications from the destination volumes to the source volumes. The following prices are for example purposes only.
72
+
The cross-region replication amount that's billed in a month is based on the amount of data that's replicated through the cross-region replication feature during that month. The amount of replicated data is measured in gibibyte (GiB). It represents the sum of data that's replicated across two regions during all regular replications from the source volumes to the destination volumes and during all resync replications from the destination volumes to the source volumes. The following prices are for example purposes only.
73
73
74
74
##### Example 1: Month 1 baseline replication and incremental replications
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/test-disaster-recovery.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.author: anfdocs
14
14
15
15
An effective disaster recovery plan includes testing your disaster recovery configuration. Testing your disaster recovery configuration demonstrates the efficacy of your disaster recovery configuration and that it can achieve the desired recovery point objective (RPO) and recovery time objective (RTO). Testing disaster recovery also ensures that operational runbooks are accurate and that operational staff are trained on the workflow.
16
16
17
-
You can test this disaster recovery workflow with [cross-region or cross-zone replication](replication.md). You can test your disaster recovery understanding and preparedness without disrupting the existing replication schedule, posing no risk to RPO or RTO. This test plan also uses Azure NetApp Files' ability to [create new volumes from the snapshots](snapshots-restore-new-volume.md) in cross-region replication.
17
+
You can test this disaster recovery workflow for [cross-region or cross-zone replication](replication.md). You can test your disaster recovery understanding and preparedness without disrupting the existing replication schedule, which poses no risk to RPO or RTO. This test plan also uses Azure NetApp Files' ability to [create new volumes from the snapshots](snapshots-restore-new-volume.md) in cross-region replication.
Copy file name to clipboardExpand all lines: articles/reliability/reliability-netapp-files.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,7 +166,7 @@ Cross-region replication charges are based on the amount of data that you replic
166
166
167
167
-**Enable cross-region replication:** To improve the resiliency of your solution, [configure cross-region replication](../azure-netapp-files/cross-region-replication-create-peering.md).
168
168
169
-
-**Disable cross-region replication:** You can disable cross-region replication by breaking the replication pairing. For more information, see [Manage disaster recovery using Azure NetApp Files](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
169
+
-**Disable cross-region replication:** You can disable cross-region replication by breaking the replication pairing. For more information, see [Manage disaster recovery by using Azure NetApp Files](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
170
170
171
171
### Normal operations
172
172
@@ -209,23 +209,23 @@ This section describes what to expect when Azure NetApp Files volumes are config
209
209
210
210
### Failback
211
211
212
-
Failback is a manual process that requires you to perform a resync operation, reestablish the replication, and remount the source volume for the client to access. For more information, see [Manage disaster recovery using Azure NetApp Files](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md).
212
+
Failback is a manual process that requires you to perform a resync operation, reestablish the replication, and remount the source volume for the client to access. For more information, see [Manage disaster recovery by using Azure NetApp Files](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md).
213
213
214
214
### Testing for region failures
215
215
216
216
You can test your cross-region replication configuration safely by using snapshots of your volume. To learn about a high-level approach to test your cross-region replication configuration, see [Test disaster recovery for Azure NetApp Files](../azure-netapp-files/test-disaster-recovery.md).
217
217
218
218
## Backups
219
219
220
-
[Azure NetApp Files backup](../azure-netapp-files/backup-introduction.md) expands the data protection capabilities of Azure NetApp Files by providing a fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independently of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups.
220
+
[Azure NetApp Files backup](../azure-netapp-files/backup-introduction.md) expands the data protection capabilities of Azure NetApp Files by providing a fully managed backup solution for long-term recovery, archive, and compliance. Backups that the service creates are stored in Azure storage, independently of volume snapshots that are available for near-term recovery or cloning. Backups that the service takes can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups.
221
221
222
222
For further security, Azure NetApp Files [snapshots](../azure-netapp-files/data-protection-disaster-recovery-options.md#snapshots) add stability, scalability, and fast recoverability without affecting performance. They provide the foundation for other redundancy solutions, including backup, cross-region replication, and cross-zone replication.
223
223
224
224
For most solutions, you shouldn't rely exclusively on backups. Instead, use the other capabilities described in this guide to support your resiliency requirements. However, backups protect against some risks that other approaches don't. For more information, see [Redundancy, replication, and backup](concept-redundancy-replication-backup.md).
225
225
226
226
## Service-level agreement
227
227
228
-
The service-level agreement (SLA) for Azure NetApp Files describes the expected availability of the service and the conditions that must be met to achieve that availability expectation. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
228
+
The service-level agreement (SLA) for Azure NetApp Files describes the expected availability of the service and the conditions that must be met to achieve that availability expectation. For more information, see [SLAs for online services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
0 commit comments