Skip to content

Commit 67a2179

Browse files
committed
fix broken links
1 parent 7efc9d8 commit 67a2179

File tree

8 files changed

+15
-55
lines changed

8 files changed

+15
-55
lines changed

articles/azure-netapp-files/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@
7676
- name: Service levels for Azure NetApp Files
7777
href: azure-netapp-files-service-levels.md
7878
- name: Guidelines for Azure NetApp Files network planning
79-
href: azure-netapp-files-network-topolo199gies.md
79+
href: azure-netapp-files-network-topologies.md
8080
- name: Resource limits for Azure NetApp Files
8181
href: azure-netapp-files-resource-limits.md
8282
- name: Reliability in Azure NetApp Files

articles/azure-netapp-files/azure-netapp-files-service-levels.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ As illustrated in the diagram, the SAP HANA backup volume received the 128MiB/s
9393
| 1,024 | 128 | 5 * 128 * 1,024 = 655,360 |
9494

9595
>[!NOTE]
96-
>A baseline throughput of 128 MiB/s is provided for every pool, at no additional cost.
96+
>A baseline throughput of 128 MiB/s is provided for every pool at no additional cost.
9797
9898
## Next steps
9999

@@ -102,4 +102,4 @@ As illustrated in the diagram, the SAP HANA backup volume received the 128MiB/s
102102
- [Create a capacity pool](azure-netapp-files-set-up-capacity-pool.md)
103103
- [Service Level Agreement (SLA) for Azure NetApp Files](https://azure.microsoft.com/support/legal/sla/netapp/)
104104
- [Dynamically change the service level of a volume](dynamic-change-volume-service-level.md)
105-
- [Service-level objectives for cross-region replication](replication.md#service-level-objectives)
105+
- [Service-level objectives](../reliability/reliability-netapp-files.md#region-down-experience)

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

Lines changed: 0 additions & 42 deletions
This file was deleted.

articles/azure-netapp-files/replication.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -43,20 +43,24 @@ For a list of regions that currently support availability zones, see [Azure regi
4343

4444
In many cases resiliency across availability zones is achieved by high-availability (HA) architectures using application-based replication and HA. Simpler, more cost-effective approaches are often considered by using storage-based data replication instead.
4545

46-
Similar to the Azure NetApp Files [cross-region replication feature](replication.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 zone. This capability enables you to fail over your critical application if a zone-wide outage or disaster happens.
46+
Similar to Azure NetApp Files [cross-region replication](#cross-region-replication), cross-zone replication (CZR) 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 zone. This capability enables you to fail over your critical application if a zone-wide outage or disaster happens.
4747

4848
Cross-zone replication is available in all [availability zone-enabled regions](../reliability/availability-zones-region-support.md) with [Azure NetApp Files presence](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&regions=all&rar=true).
4949

50+
For service level objects, see [Azure NetApp Files reliability](../reliability/reliability-netapp-files.md#region-down-experience).
51+
5052
### Cost model for cross-zone replication
5153

5254
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.
5355

5456
## Cross-region replication
5557

56-
The Azure NetApp Files replication functionality provides data protection through cross-region volume replication. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region. This capability enables you to fail over your critical application if a region-wide outage or disaster happens.
58+
Azure NetApp Files replication is available across regions. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region. This capability enables you to fail over your critical application if a region-wide outage or disaster happens.
5759

5860
Azure NetApp Files cross-region replication must adhere to [supported regional pairs](#supported-region-pairs).
5961

62+
For service level objects, see [Azure NetApp Files reliability](../reliability/reliability-netapp-files.md#region-down-experience).
63+
6064
### Cost model for cross-region replication
6165

6266
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.
@@ -115,15 +119,15 @@ Azure NetApp Files supports using cross-zone and cross-region replication on the
115119

116120
* Cross-region and​ cross-zone replication target volumes
117121

118-
:::image type="content" source="./media/cross-zone-region-introduction/zone-region.png" alt-text="Diagram of cross-zone and cross-region replication." lightbox="./media/cross-zone-region-introduction/zone-region.png":::
122+
:::image type="content" source="./media/reliability/zone-region.png" alt-text="Diagram of cross-zone and cross-region replication." lightbox="./media/reliability/zone-region.png":::
119123

120124
* Two cross-region replication target volumes
121125

122-
:::image type="content" source="./media/cross-zone-region-introduction/double-region.png" alt-text="Diagram of double cross-region replication." lightbox="./media/cross-zone-region-introduction/double-region.png":::
126+
:::image type="content" source="./media/reliability/double-region.png" alt-text="Diagram of double cross-region replication." lightbox="./media/reliability/double-region.png":::
123127

124128
* Two cross-zone replication target volumes in any combination of availability zones, including in-zone replication
125129

126-
:::image type="content" source="./media/cross-zone-region-introduction/double-zone.png" alt-text="Diagram of double cross-zone replication." lightbox="./media/cross-zone-region-introduction/double-zone.png":::
130+
:::image type="content" source="./media/reliability/double-zone.png" alt-text="Diagram of double cross-zone replication." lightbox="./media/reliability/double-zone.png":::
127131

128132
### Requirements for cross-zone-region replication
129133

articles/reliability/reliability-netapp-files.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article describes reliability support in Azure NetApp Files, covering intra
1717

1818
Azure NetApp Files is a native, enterprise-grade file storage solution that's integrated seamlessly within Azure, enabling file sharing across clients via SMB and NFS protocols. Designed for high performance, Azure NetApp Files offers scalable and secure file storage that's managed as a service.
1919

20-
To use Azure NetApp Files, you create *volumes* within a NetApp account, as well as *capacity pools*. You can configure capacity and throughput independently, and manage data protection options tailored to various needs. You can enable replication between volumes, even if they're in different locations.
20+
To use Azure NetApp Files, you must configure a NetApp account which contain *capacity pools* that in turn host *volumes*. You can configure capacity and throughput independently, and manage data protection options tailored to various needs. You can enable replication between volumes, even if they're in different locations.
2121

2222
## Production deployment recommendations
2323

@@ -53,7 +53,7 @@ For further recommendations, see [Azure NetApp Files application resilience FAQs
5353

5454
[!INCLUDE [AZ support description](includes/reliability-availability-zone-description-include.md)]
5555

56-
Azure NetApp Files supports *zonal* deployments of volumes. [Azure NetApp Files' availability zone volume placement feature](../azure-netapp-files/use-availability-zones.md) lets you deploy each volume in a single availability zone of your choice, as long as Azure NetApp Files is present in that availability zone and has sufficient capacity. If you have latency-sensitive applications, you can deploy a volume to the same availability zone as your Azure compute resources and other services in the same zone.
56+
Azure NetApp Files supports *zonal* deployments of volumes. [Azure NetApp Files' availability zone volume placement feature](../azure-netapp-files/replication.md#availablity-zones) lets you deploy each volume in a single availability zone of your choice, as long as Azure NetApp Files is present in that availability zone and has sufficient capacity. If you have latency-sensitive applications, you can deploy a volume to the same availability zone as your Azure compute resources and other services in the same zone.
5757

5858
In the diagram below, all virtual machines (VMs) within the region in (peered) VNets can access all Azure NetApp Files resources (blue arrows). VMs accessing Azure NetApp Files volumes in the same zone (green arrows) share the availability zone failure domain. Note there's no replication between the different volumes at the platform level.
5959

@@ -156,9 +156,7 @@ You can test your cross-zone replication configuration safely by using snapshots
156156

157157
## Multi-region support
158158

159-
Azure NetApp Files is a single-region service. If the region becomes unavailable, volumes stored in that region are also unavailable.
160-
161-
However, Azure NetApp Files provides data protection through cross-region volume replication. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region preselected by Microsoft. This capability enables you to fail over your critical application if a region-wide outage or disaster happens.
159+
By default, Azure NetApp Files is a single region service. To improve resiliency in the event of a regional outage, Azure NetApp Files supports cross-region replication. You can asynchronously replicate data from an Azure NetApp Files volume (source) in one region to another Azure NetApp Files volume (destination) in another region preselected by Microsoft. This capability enables you to fail over your critical application if a region-wide outage or disaster happens.
162160

163161
> [!NOTE]
164162
> You can also replicate a single volume to another availability zone *and* to another region. To learn more, see [Understand cross-zone-region replication in Azure NetApp Files](../azure-netapp-files/cross-zone-region-replication.md).

0 commit comments

Comments
 (0)