Skip to content

Commit c8b7de2

Browse files
committed
edit
1 parent 3f725f6 commit c8b7de2

File tree

6 files changed

+9
-13
lines changed

6 files changed

+9
-13
lines changed

articles/reliability/TOC.yml

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@
227227
- name: Azure Cognitive Search
228228
href: ../search/search-reliability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
229229
- name: Azure Container Instances
230-
href: reliability-container.md#disaster-recovery
230+
href: reliability-containers.md#disaster-recovery
231231
- name: Azure Database for MySQL
232232
href: /azure/mysql/single-server/concepts-business-continuity#recover-from-an-azure-regional-data-center-outage
233233
- name: Azure Database for MySQL - Flexible Server
@@ -255,11 +255,7 @@
255255
- name: Azure Monitor - Log Analytics
256256
href: ../azure-monitor/logs/logs-data-export.md?tabs=portal#enable-data-export
257257
- name: Azure Monitor - Application Insights
258-
items:
259-
- name: Continuous export advanced storage configuration
260-
href: ../azure-monitor/app/export-telemetry.md#continuous-export-advanced-storage-configuration
261-
- name: Move Application Insights resource to a new region
262-
href: ../azure-monitor/faq.yml#how-do-i-move-an-application-insights-resource-to-a-new-region-
258+
href: ../azure-monitor/app/export-telemetry.md#continuous-export-advanced-storage-configuration
263259
- name: Azure SQL Server Registry
264260
href: /sql/sql-server/end-of-support/sql-server-extended-security-updates?preserve-view=true&view=sql-server-ver15#configure-regional-redundancy
265261
- name: Azure Stream Analytics

articles/reliability/availability-zones-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,11 +66,11 @@ Microsoft aims to deploy updates to Azure services to a single availability zone
6666

6767
## Paired and unpaired regions
6868

69-
Many regions also have a [*paired region*](./cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies). Paired regions support certain types of multi-region deployment approaches. Some newer regions have [multiple availability zones and don't have a paired region](./cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair). You can still deploy multi-region solutions into these regions, but the approaches you use might be different.
69+
Many regions also have a [*paired region*](./cross-region-replication-azure.md#azure-paired-regions). Paired regions support certain types of multi-region deployment approaches. Some newer regions have [multiple availability zones and don't have a paired region](./cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair). You can still deploy multi-region solutions into these regions, but the approaches you use might be different.
7070

7171
## Shared responsibility model
7272

73-
The [shared responsibility model](./overview.md#shared-responsibility) describes how responsibilities are divided between the cloud provider (Microsoft) and you. Depending on the type of services you use, you might take on more or less responsibility for operating the service.
73+
The [shared responsibility model](/azure/security/fundamentals/shared-responsibility) describes how responsibilities are divided between the cloud provider (Microsoft) and you. Depending on the type of services you use, you might take on more or less responsibility for operating the service.
7474

7575
Microsoft provides availability zones and regions to give you flexibility in how you design your solution to meet your requirements. When you use managed services, Microsoft takes on more of the management responsibilities for your resources, which might even include data replication, failover, failback, and other tasks related to operating a distributed system.
7676

articles/reliability/disaster-recovery-guidance-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The tables below lists each product that offers disaster recovery guidance and/o
5454
| [Azure Bastion](../bastion/bastion-faq.md?#dr) |
5555
| [Azure Cache for Redis](../azure-cache-for-redis/cache-how-to-geo-replication.md) |
5656
| [Azure Cognitive Search](../search/search-reliability.md) |
57-
| [Azure Container Instances](reliability-container.md#disaster-recovery) |
57+
| [Azure Container Instances](reliability-containers.md#disaster-recovery) |
5858
| [Azure Database for MySQL](/azure/mysql/single-server/concepts-business-continuity?#recover-from-an-azure-regional-data-center-outage) |
5959
| [Azure Database for MySQL - Flexible Server](/azure/mysql/flexible-server/how-to-restore-server-portal?#geo-restore-to-latest-restore-point) |
6060
| [Azure Database for PostgreSQL - Flexible Server](reliability-postgre-flexible.md#cross-region-disaster-recovery-and-business-continuity) |
@@ -68,7 +68,7 @@ The tables below lists each product that offers disaster recovery guidance and/o
6868
| [Azure Media Services](/azure/media-services/latest/architecture-high-availability-encoding-concept) |
6969
| [Azure Migrate](../migrate/resources-faq.md?#does-azure-migrate-offer-backup-and-disaster-recovery) |
7070
| [Azure Monitor - Log Analytics](../azure-monitor/logs/logs-data-export.md?&tabs=portal#enable-data-export) |
71-
| [Azure Monitor - Application Insights - Continuous export advanced storage configuration](../azure-monitor/app/export-telemetry.md#continuous-export-advanced-storage-configuration) and [Move Application Insights resource to a new region](../azure-monitor/faq.yml?#how-do-i-move-an-application-insights-resource-to-a-new-region-) |
71+
| [Azure Monitor - Application Insights](../azure-monitor/app/export-telemetry.md#continuous-export-advanced-storage-configuration) |
7272
| [Azure SQL Server Registry](/sql/sql-server/end-of-support/sql-server-extended-security-updates?preserve-view=true&view=sql-server-ver15#configure-regional-redundancy) |
7373
| [Azure Stream Analytics](../stream-analytics/geo-redundancy.md) |
7474
| [Azure Virtual WAN](../expressroute/designing-for-disaster-recovery-with-expressroute-privatepeering.md) |

articles/reliability/reliability-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ Applications that are deployed in an availability zone enabled Premium plan cont
152152

153153
When Functions allocates instances to a zone redundant Premium plan, it uses best effort zone balancing offered by the underlying Azure Virtual Machine Scale Sets. A Premium plan is considered balanced when each zone has either the same number of VMs (± 1 VM) in all of the other zones used by the Premium plan.
154154

155-
## Cross-region recovery and business continuity
155+
## Cross-region disaster recovery and business continuity
156156

157157
[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
158158

articles/reliability/reliability-hdinsight.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ When an availability zone goes down:
111111
- You still can submit new cluster creation request in a different region.
112112

113113

114-
## Cross-region recovery and business continuity
114+
## Cross-region disaster recovery and business continuity
115115

116116
[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
117117

articles/reliability/reliability-virtual-machines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -516,7 +516,7 @@ For more information, see [Azure VMs architectural components](../site-recovery/
516516

517517
### Capacity and proactive disaster recovery resiliency
518518

519-
Microsoft and its customers operate under the [Shared Responsibility Model](./overview.md#shared-responsibility). Shared responsibility means that for customer-enabled DR (customer-responsible services), you must address DR for any service they deploy and control. To ensure that recovery is proactive, you should always pre-deploy secondaries because there's no guarantee of capacity at time of impact for those who haven't preallocated.
519+
Microsoft and its customers operate under the [Shared Responsibility Model](./availability-zones-overview.md#shared-responsibility-model). Shared responsibility means that for customer-enabled DR (customer-responsible services), you must address DR for any service they deploy and control. To ensure that recovery is proactive, you should always pre-deploy secondaries because there's no guarantee of capacity at time of impact for those who haven't preallocated.
520520

521521
For deploying virtual machines, you can use [flexible orchestration](../virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md#scale-sets-with-flexible-orchestration) mode on Virtual Machine Scale Sets. All VM sizes can be used with flexible orchestration mode. Flexible orchestration mode also offers high availability guarantees (up to 1000 VMs) by spreading VMs across fault domains either within a region or within an availability zone.
522522

0 commit comments

Comments
 (0)