Skip to content

Commit 6fb30b4

Browse files
authored
Merge pull request #244724 from anaharris-ms/rel-vmss
Reliability: VMSS
2 parents 6dbe77b + b9f7dcb commit 6fb30b4

File tree

9 files changed

+566
-106
lines changed

9 files changed

+566
-106
lines changed

articles/reliability/TOC.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@
4646
href: migrate-storage.md
4747
- name: Azure SQL managed instance
4848
href: migrate-sql-managed-instance.md
49-
- name: Azure Virtual Machines and virtual machine scale sets
49+
- name: Azure Virtual Machines and Virtual Machine Scale Sets
5050
href: migrate-vm.md
5151
- name: Workload - Azure Kubernetes and MySQL
5252
href: migrate-workload-aks-mysql.md
@@ -252,8 +252,7 @@
252252
- name: Azure Virtual Machines Image Builder
253253
href: reliability-image-builder.md
254254
- name: Azure Virtual Machine Scale Sets
255-
href: ../virtual-machines/availability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
256-
255+
href: reliability-virtual-machine-scale-sets.md
257256
- name: Azure Virtual Network
258257
href: ../vpn-gateway/create-zone-redundant-vnet-gateway.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
259258
- name: Azure VPN Gateway

articles/reliability/includes/reliability-availability-zone-description-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@ Azure availability zones are at least three physically separate groups of datace
1313

1414
Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Regions and availability zones](/azure/availability-zones/az-overview).
1515

16-
Azure availability zones-enabled services are designed to provide the right level of reliability and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Build solutions with availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability).
16+
Azure availability zones-enabled services are designed to provide the right level of reliability and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Build solutions with availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability).

articles/reliability/includes/reliability-recommendations-include.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,13 @@
1010
---
1111

1212

13+
1314
This section contains recommendations for achieving resiliency and availability. Each recommendation falls into one of two categories:
1415

16+
1517
- **Health items** cover areas such as configuration items and the proper function of the major components that make up your Azure Workload, such as Azure Resource configuration settings, dependencies on other services, and so on.
1618

17-
- **Risk items** cover areas such as availability and recovery requirements, testing, monitoring, deployment, and other items that if left unresolved increase the chances of problems in the environment. Usually the Well-Architected Framework best practices.
19+
- **Risk items** cover areas such as availability and recovery requirements, testing, monitoring, deployment, and other items that, if left unresolved, increase the chances of problems in the environment.
1820

1921

2022
### Reliability recommendations priority matrix

articles/reliability/migrate-vm.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,15 @@ ms.custom: references_regions, subject-reliability
1414

1515
This guide describes how to migrate Virtual Machines (VMs) and Virtual Machine Scale Sets from non-availability zone support to availability zone support. We take you through the different options for migration, including how you can use availability zone support for Disaster Recovery solutions.
1616

17-
Virtual Machine (VM) and Virtual Machine Scale Sets are zonal services, which means that VM resources can be deployed by using one of the following methods:
17+
Virtual Machine (VM) and Virtual Machine Scale Sets are availability zone enabled services, which means that VM resources can be deployed by using one of the following methods:
1818

19-
- VM resources are deployed to a specific, self-selected availability zone to achieve more stringent latency or performance requirements.
19+
- **Zonal**: VM resources are deployed to a specific, self-selected availability zone to achieve more stringent latency or performance requirements.
2020

21-
- VM resources are replicated to one or more zones within the region to improve the resiliency of the application and data in a High Availability (HA) architecture.
21+
- **Zone-redundant**: VM resources are replicated to one or more zones within the region to improve the resiliency of the application and data in a High Availability (HA) architecture.
2222

23-
When you migrate resources to availability zone support, we recommend that you select multiple zones for your new VMs and Virtual Machine Scale Sets, to ensure high-availability of your compute resources.
23+
To ensure high-availability of your compute resources, we recommend that you select multiple zones for your new VMs and Virtual Machine Scale Sets when you migrate to availability zones.
24+
25+
For more information on availability zone support for VM services, see [Reliability in Virtual Machines](./reliability-virtual-machines.md). For availability zone support for Virtual Machine scale sets, see [Reliability in Virtual Machine Scale Sets](./reliability-virtual-machine-scale-sets.md).
2426

2527
## Prerequisites
2628

@@ -146,7 +148,7 @@ The following requirements should be part of a disaster recovery strategy that h
146148

147149
## Next Steps
148150

149-
Learn more about:
151+
- [Azure services and regions that support availability zones](availability-zones-service-support.md)
152+
- [Reliability in Virtual Machines](./reliability-virtual-machines.md)
153+
- [Reliability in Virtual Machine Scale Sets](./reliability-virtual-machine-scale-sets.md)
150154

151-
> [!div class="nextstepaction"]
152-
> [Azure services and regions that support availability zones](availability-zones-service-support.md)

articles/reliability/reliability-guidance-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Azure reliability guidance contains the following:
3636
[Azure SQL](/azure/azure-sql/database/high-availability-sla?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
3737
[Azure Storage: Blob Storage](../storage/common/storage-disaster-recovery-guidance.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
3838
[Azure Storage Mover](reliability-azure-storage-mover.md)|
39-
[Azure Virtual Machine Scale Sets](../virtual-machines/availability.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|
39+
[Azure Virtual Machine Scale Sets](reliability-virtual-machine-scale-sets.md)|
4040
[Azure Virtual Machines](reliability-virtual-machines.md)|
4141
[Azure Virtual Machines Image Builder](reliability-image-builder.md)|
4242
[Azure Virtual Network](../vpn-gateway/create-zone-redundant-vnet-gateway.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|

0 commit comments

Comments
 (0)