Skip to content

Commit 2dfa3e2

Browse files
committed
Update reliability links
1 parent 3203983 commit 2dfa3e2

17 files changed

+19
-19
lines changed

Diff for: articles/cosmos-db/dedicated-gateway.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ There are many different ways to provision a dedicated gateway:
8080
- Note: You can't deprovision a dedicated gateway using ARM templates
8181

8282
> [!NOTE]
83-
> You can provision a dedicated gateway in Azure Cosmos DB accounts with [availability zones](/azure/availability-zones/az-region) by request. Reach out to cosmoscachefeedback@microsoft.com for more information.
83+
> You can provision a dedicated gateway in Azure Cosmos DB accounts with [availability zones](/azure/reliability/availability-zones-region-support) by request. Reach out to cosmoscachefeedback@microsoft.com for more information.
8484
8585
## Dedicated gateway in multi-region accounts
8686

Diff for: articles/cosmos-db/includes/cosmos-db-tutorial-global-distribution-portal.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ There are two common scenarios for configuring two or more regions:
2424

2525
For delivering low-latency to end users, it is recommended that you deploy both the application and Azure Cosmos DB in the regions that correspond to where the application's users are located.
2626

27-
For BCDR, it is recommended to add regions based on the region pairs described in the [Cross-region replication in Azure: Business continuity and disaster recovery](/azure/availability-zones/cross-region-replication-azure) article.
27+
For BCDR, it is recommended to add regions based on the region pairs described in the [Cross-region replication in Azure: Business continuity and disaster recovery](/azure/reliability/cross-region-replication-azure) article.
2828

2929
[1]: ./media/cosmos-db-tutorial-global-distribution-portal/azure-cosmos-db-add-region.png
3030
[2]: ./media/cosmos-db-tutorial-global-distribution-portal/azure-cosmos-db-manual-failover-1.png

Diff for: articles/cosmos-db/periodic-backup-restore-introduction.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The following steps show how Azure Cosmos DB performs data backup:
2323

2424
- Azure Cosmos DB stores these backups in Azure Blob storage whereas the actual data resides locally within Azure Cosmos DB.
2525

26-
- To guarantee low latency, the snapshot of your backup is stored in Azure Blob storage in the same region as the current write region (or **one** of the write regions, in case you have a multi-region write configuration). For resiliency against regional disaster, each snapshot of the backup data in Azure Blob storage is again replicated to another region through geo-redundant storage (GRS). The region to which the backup is replicated is based on your source region and the regional pair associated with the source region. To learn more, see the [list of geo-redundant pairs of Azure regions](/azure/availability-zones/cross-region-replication-azure) article. You can't access this backup directly. Azure Cosmos DB team restores your backup when you request through a support request.
26+
- To guarantee low latency, the snapshot of your backup is stored in Azure Blob storage in the same region as the current write region (or **one** of the write regions, in case you have a multi-region write configuration). For resiliency against regional disaster, each snapshot of the backup data in Azure Blob storage is again replicated to another region through geo-redundant storage (GRS). The region to which the backup is replicated is based on your source region and the regional pair associated with the source region. To learn more, see the [list of geo-redundant pairs of Azure regions](/azure/reliability/cross-region-replication-azure) article. You can't access this backup directly. Azure Cosmos DB team restores your backup when you request through a support request.
2727

2828
The following image shows how an Azure Cosmos DB container with all the three primary physical partitions in West US. The container is backed up in a remote Azure Blob Storage account in West US and then replicated to East US:
2929

Diff for: articles/cosmos-db/periodic-backup-storage-redundancy.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 03/21/2023
1313

1414
[!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
1515

16-
By default, Azure Cosmos DB stores periodic mode backup data in geo-redundant [Azure Blob Storage](/azure/storage/common/storage-redundancy). The blob storage is then, by default, replicated to a [paired region](/azure/availability-zones/cross-region-replication-azure). You can update this default value using Azure PowerShell or Azure CLI and define an Azure policy to enforce a specific storage redundancy option. For more information, see [update backup storage redundancy](periodic-backup-update-storage-redundancy.md).
16+
By default, Azure Cosmos DB stores periodic mode backup data in geo-redundant [Azure Blob Storage](/azure/storage/common/storage-redundancy). The blob storage is then, by default, replicated to a [paired region](/azure/reliability/cross-region-replication-azure). You can update this default value using Azure PowerShell or Azure CLI and define an Azure policy to enforce a specific storage redundancy option. For more information, see [update backup storage redundancy](periodic-backup-update-storage-redundancy.md).
1717

1818
## Best practices
1919

@@ -30,7 +30,7 @@ You can configure storage redundancy for periodic backup mode at the time of acc
3030
- **Locally-redundant backup storage:** This option copies your data synchronously three times within a single physical location in the primary region. For more information, see [locally redundant storage.](/azure/storage/common/storage-redundancy#redundancy-in-the-primary-region)
3131

3232
> [!NOTE]
33-
> Zone-redundant storage is currently available only in [specific regions](/azure/availability-zones/az-region). Depending on the region you select for a new account or the region you have for an existing account; the zone-redundant option will not be available.
33+
> Zone-redundant storage is currently available only in [specific regions](/azure/reliability/availability-zones-region-support). Depending on the region you select for a new account or the region you have for an existing account; the zone-redundant option will not be available.
3434
>
3535
> Updating backup storage redundancy will not have any impact on backup storage pricing.
3636

Diff for: articles/cosmos-db/periodic-backup-update-storage-redundancy.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell
1414

1515
[!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
1616

17-
Azure Cosmos DB period mode backup data is replicated in different ways. If the primary region supports [paired regions](/azure/availability-zones/cross-region-replication-azure) then, by default, Azure Cosmos DB stores periodic mode backup data in geo-redundant [blob storage](/azure/storage/common/storage-redundancy) that is replicated to the pair. You can override the default backup storage redundancy. Alternatively, if you use a [non-paired region](/azure/reliability/cross-region-replication-azure#regions-with-availability-zones-and-no-region-pair), you need to explicitly choose the backup storage redundancy. This article explains how to update the backup storage redundancy using Azure CLI and PowerShell. It also shows how to configure an Azure policy on your accounts to enforce the required storage redundancy.
17+
Azure Cosmos DB period mode backup data is replicated in different ways. If the primary region supports [paired regions](/azure/reliability/cross-region-replication-azure) then, by default, Azure Cosmos DB stores periodic mode backup data in geo-redundant [blob storage](/azure/storage/common/storage-redundancy) that is replicated to the pair. You can override the default backup storage redundancy. Alternatively, if you use a [non-paired region](/azure/reliability/cross-region-replication-azure#regions-with-availability-zones-and-no-region-pair), you need to explicitly choose the backup storage redundancy. This article explains how to update the backup storage redundancy using Azure CLI and PowerShell. It also shows how to configure an Azure policy on your accounts to enforce the required storage redundancy.
1818

1919
## Prerequisites
2020

Diff for: articles/cosmos-db/postgresql/concepts-backup.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -89,4 +89,4 @@ In most cases, cluster restore takes up to 1 hour.
8989
* See the steps to [restore a cluster](howto-restore-portal.md)
9090
in the Azure portal.
9191
* See [backup and restore limits and limitations](./reference-limits.md#backup-and-restore).
92-
* Learn about  [Azure availability zones](/azure/availability-zones/az-overview).
92+
* Learn about  [Azure availability zones](/azure/reliability/availability-zones-overview).

Diff for: articles/cosmos-db/postgresql/resources-regions.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Azure Cosmos DB for PostgreSQL is available in the following Azure regions:
5050
| West US 2 | :heavy_check_mark: | :heavy_check_mark: | West Central US |
5151
| West US 3 | :heavy_check_mark: | :heavy_check_mark: | :x: |
5252

53-
† This Azure region is a [restricted one](/azure/availability-zones/cross-region-replication-azure#azure-paired-regions). To use it, you need to request access to it by opening a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
53+
† This Azure region is a [restricted one](/azure/reliability/cross-region-replication-azure#azure-paired-regions). To use it, you need to request access to it by opening a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
5454

5555
Some of these regions may not be activated on all Azure
5656
subscriptions. If you want to use a region from the list and don't see it

Diff for: articles/cosmos-db/serverless.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ You can use the same [chart in Azure Monitor](monitor-request-unit-usage.md). Wh
6565

6666
## High availability
6767

68-
Azure Cosmos DB serverless extends high availability support with availability zones in [designated regions](/azure/reliability/availability-zones-service-support#azure-regions-with-availability-zone-support). The associated Service Level Agreements (SLAs) are aligned with the [Single-region writes with availability zone](../../articles/cosmos-db/high-availability.md#slas) configuration, ensuring reliability for your deployments.
68+
Azure Cosmos DB serverless extends high availability support with availability zones in [designated regions](/azure/reliability/availability-zones-region-support). The associated Service Level Agreements (SLAs) are aligned with the [Single-region writes with availability zone](../../articles/cosmos-db/high-availability.md#slas) configuration, ensuring reliability for your deployments.
6969

7070

7171
## Next steps

Diff for: articles/managed-instance-apache-cassandra/configure-hybrid-cluster-cli.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ This quickstart demonstrates how to use the Azure CLI commands to configure a hy
166166
> Note also that `--availability-zone` is set to `false`. To enable availability zones, set this to `true`. Availability zones increase the availability SLA of the service. For more details, review the full SLA details [here](https://azure.microsoft.com/support/legal/sla/managed-instance-apache-cassandra/v1_0/).
167167
168168
> [!WARNING]
169-
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
169+
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
170170
171171
1. Now that the new datacenter is created, run the show datacenter command to view its details:
172172

Diff for: articles/managed-instance-apache-cassandra/create-cluster-cli.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ This quickstart demonstrates how to use the Azure CLI commands to create a clust
122122
> Note also that `--availability-zone` is set to `false`. To enable availability zones, set this to `true`. Availability zones increase the availability SLA of the service. For more details, review the full SLA details [here](https://azure.microsoft.com/support/legal/sla/managed-instance-apache-cassandra/v1_0/).
123123
124124
> [!WARNING]
125-
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
125+
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
126126
127127
1. Once the datacenter is created, if you want to scale up, or scale down the nodes in the datacenter, run the [az managed-cassandra datacenter update](/cli/azure/managed-cassandra/datacenter#az-managed-cassandra-datacenter-update) command. Change the value of `node-count` parameter to the desired value:
128128

Diff for: articles/managed-instance-apache-cassandra/create-cluster-portal.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
9191
:::image type="content" source="./media/create-cluster-portal/create-datacenter-page.png" alt-text="Review summary to create the datacenter." lightbox="./media/create-cluster-portal/create-datacenter-page.png" border="true":::
9292

9393
> [!WARNING]
94-
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
94+
> Availability zones are not supported in all regions. Deployments will fail if you select a region where Availability zones are not supported. See [here](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) for supported regions. The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
9595
9696
1. Next, select **Review + create** > **Create**
9797

Diff for: articles/managed-instance-apache-cassandra/create-multi-region-cluster.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -192,7 +192,7 @@ If you encounter errors when you run `az role assignment create`, you might not
192192
> Note also that `--availability-zone` is set to `false`. To enable availability zones, set this to `true`. Availability zones increase the availability SLA of the service. For more information, see [SLA for Azure Managed Instance for Apache Cassandra](https://azure.microsoft.com/support/legal/sla/managed-instance-apache-cassandra/v1_0/).
193193
194194
> [!WARNING]
195-
> Availability zones are not supported in all regions. Deployments fail if you select a region where Availability zones are not supported. For supported regions, see [Azure regions with availability zones](/azure/availability-zones/az-overview#azure-regions-with-availability-zones).
195+
> Availability zones are not supported in all regions. Deployments fail if you select a region where Availability zones are not supported. For supported regions, see [Azure regions with availability zones](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones).
196196
>
197197
> The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in the given region. Deployments may fail if the SKU you have selected, or capacity, is not available across all zones.
198198

Diff for: articles/managed-instance-apache-cassandra/manage-resources-cli.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Currently, Azure Managed Instance for Apache Cassandra doesn't support transitio
177177
In the preceding command, `--availability-zone` is set to `false`. To enable availability zones, set this value to `true`. Availability zones increase the service-level agreement (SLA) for availability of the service. For more information, review the [full SLA details](https://azure.microsoft.com/support/legal/sla/managed-instance-apache-cassandra/v1_0/).
178178

179179
> [!WARNING]
180-
> Azure Managed Instance for Apache Cassandra doesn't support availability zones in all regions. If you select a region where availability zones aren't supported, deployments will fail. See the [list of supported regions](/azure/availability-zones/az-overview#azure-regions-with-availability-zones).
180+
> Azure Managed Instance for Apache Cassandra doesn't support availability zones in all regions. If you select a region where availability zones aren't supported, deployments will fail. See the [list of supported regions](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones).
181181
>
182182
> The successful deployment of availability zones is also subject to the availability of compute resources in all of the zones in a region. Deployments might fail if the VM or the capacity that you selected isn't available across all zones.
183183

Diff for: articles/managed-instance-apache-cassandra/resilient-applications.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ RTO ("how long you're down in an outage") will be low because the cluster will b
3333

3434
## Availability zones
3535

36-
Cassandra's masterless architecture brings fault tolerance from the ground up, and Azure Managed Instance for Apache Cassandra provides support for [availability zones](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) in selected regions to enhance resiliency at the infrastructure level. Given a replication factor of 3, availability zone support ensures that each replica is in a different availability zone, thus preventing a zonal outage from impacting your database/application. We recommend enabling availability zones where possible.
36+
Cassandra's masterless architecture brings fault tolerance from the ground up, and Azure Managed Instance for Apache Cassandra provides support for [availability zones](/azure/reliability/availability-zones-overview#azure-regions-with-availability-zones) in selected regions to enhance resiliency at the infrastructure level. Given a replication factor of 3, availability zone support ensures that each replica is in a different availability zone, thus preventing a zonal outage from impacting your database/application. We recommend enabling availability zones where possible.
3737

3838

3939
## Multi-region redundancy

0 commit comments

Comments
 (0)