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/reliability/availability-zones-baseline.md
+5-10Lines changed: 5 additions & 10 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
-
title: Availability zone migration baseline
3
-
description: Learn about availabilityzone migration baseline
2
+
title: Azure availability zone migration baseline
3
+
description: Learn how to assess the availability-zone readiness of your application for the purposes of migrating from non-availability zone to availability zone support.
4
4
author: anaharris-ms
5
5
ms.service: reliability
6
6
ms.subservice: availability-zones
@@ -10,8 +10,7 @@ ms.author: anaharris
10
10
ms.custom: references_regions
11
11
---
12
12
13
-
# Availability zone migration baseline
14
-
13
+
# Azure availability zone migration baseline
15
14
16
15
This article shows you how to assess the availability-zone readiness of your application for the purposes of migrating from non-availability zone to availability zone support. We'll take you through the steps you'll need to determine which how to take advantage of availability zone support in alignment with your application and regional requirements. For more detailed information on availability zones and the regions that support them, see [What are Azure regions and availability zones?](availability-zones-overview.md).
17
16
@@ -71,10 +70,6 @@ The recommended approach to achieving high availability, if low latency isn't a
71
70
For critical application components that require physical proximity and low latency, such as gaming, engineering simulation, and high-frequency trading (HFT), we recommend that you configure a zonal deployment. [VMSS Flex](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes) provides zone aligned compute along with attached storage disks.
72
71
73
72
74
-
75
-
76
-
77
-
78
73
#### Does your application code have the readiness to handle a distributed model?
79
74
80
75
For a [distributed microservices model](/azure/architecture/guide/architecture-styles/microservices) and depending on your application, there is the possibility of ongoing data exchange between microservices across zones. This continual data exchange through APIs, could affect performance. To improve performance and maintain a reliable architecture, you can choose zonal deployment.
@@ -110,9 +105,9 @@ For specialized workload on Azure as below examples, please refer to the respect
110
105
-[Oracle on Azure architecture design](/azure/architecture/solution-ideas/articles/oracle-on-azure-start-here)
111
106
112
107
113
-
#### Do you want to achieve business continuity and disaster recovery (BCDR) in the **same** Azure region due to compliance, data residency, or governance requirements?
108
+
#### Do you want to achieve BCDR in the same Azure region due to compliance, data residency, or governance requirements?
114
109
115
-
To achieve BCDR within the same region and when there **is no regional pair**, we highly recommend that you configure your workload with zone-redundancy. A single-region approach is also applicable to certain industries that have strict data residency and governance requirements within the same Azure region. To learn how to replicate, failover, and failback Azure virtual machines from one availability zone to another within the same Azure region, see [Enable Azure VM disaster recovery between availability zones](/azure/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery).
110
+
To achieve business continuity and disaster recovery within the same region and when there **is no regional pair**, we highly recommend that you configure your workload with zone-redundancy. A single-region approach is also applicable to certain industries that have strict data residency and governance requirements within the same Azure region. To learn how to replicate, failover, and failback Azure virtual machines from one availability zone to another within the same Azure region, see [Enable Azure VM disaster recovery between availability zones](/azure/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery).
116
111
117
112
If multi-region is needed, or when availability zones aren't available in the Azure region, we recommend that you use regional pairs. Regional pairs are situated at far distance at around 100 miles apart, and give you blast radius protection from regional level failures such as fire, flooding, earthquake and other natural or unforeseen calamities. For more information see [Cross-region replication in Azure: Business continuity and disaster recovery](/azure/reliability/cross-region-replication-azure).
Copy file name to clipboardExpand all lines: articles/reliability/availability-zones-migration-overview.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,8 @@ ms.custom: subject-reliability
14
14
15
15
Azure services that support availability zones, including zonal and zone-redundant offerings, are continually expanding. For that reason, resources that don't currently have availability zone support, may have an opportunity to gain that support. The Migration Guides section offers a collection of guides for each service that requires certain procedures in order to move a resource from non-availability zone support to availability support. You'll find information on prerequisites for migration, download requirements, important migration considerations and recommendations.
16
16
17
+
To check the readiness of your application for availability zone support, see [Azure availability zone migration baseline](./availability-zones-baseline.md).
18
+
17
19
The table below lists each product that offers migration guidance and/or information.
0 commit comments