|
| 1 | +--- |
| 2 | +title: Migrate Azure Virtual Machines and Azure Virtual Machine Scale Sets to availability zone support |
| 3 | +description: Learn how to migrate your Azure Virtual Machines and Virtual Machine Scale Sets to availability zone support. |
| 4 | +author: anaharris-ms |
| 5 | +ms.service: azure |
| 6 | +ms.topic: conceptual |
| 7 | +ms.date: 04/21/2022 |
| 8 | +ms.author: anaharris |
| 9 | +ms.reviewer: anaharris |
| 10 | +ms.custom: references_regions |
| 11 | +--- |
| 12 | + |
| 13 | +# Migrate Virtual Machines and Virtual Machine Scale Sets to availability zone support |
| 14 | + |
| 15 | +This guide describes how to migrate Virtual Machines (VMs) and Virtual Machine Scale Sets (VMSS) from non-availability zone support to availability zone support. We'll take you through the different options for migration, including how you can use availability zone support for Disaster Recovery solutions. |
| 16 | + |
| 17 | +Virtual Machine (VM) and Virtual Machine Scale Sets (VMSS) are zonal services, which means that VM resources can be deployed by using one of the following methods: |
| 18 | + |
| 19 | +- VM resources are deployed to a specific, self-selected availability zone to achieve more stringent latency or performance requirements. |
| 20 | + |
| 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. |
| 22 | + |
| 23 | +When you migrate resources to availability zone support, we recommend that you select multiple zones for your new VMs and VMSS, to ensure high-availability of your compute resources. |
| 24 | + |
| 25 | +## Prerequisites |
| 26 | + |
| 27 | +To migrate to availability zone support, your VM SKUs must be available across the zones in for your region. To check for VM SKU availability, use one of the following methods: |
| 28 | + |
| 29 | +- Use PowerShell to [Check VM SKU availability](../virtual-machines/windows/create-PowerShell-availability-zone.md#check-vm-sku-availability). |
| 30 | +- Use the Azure CLI to [Check VM SKU availability](../virtual-machines/linux/create-cli-availability-zone.md#check-vm-sku-availability). |
| 31 | +- Go to [Foundational Services](az-region.md#an-icon-that-signifies-this-service-is-foundational-foundational-services). |
| 32 | + |
| 33 | +## Downtime requirements |
| 34 | + |
| 35 | +Because zonal VMs are created across the availability zones, all migration options mentioned in this article require downtime during deployment because zonal VMs are created across the availability zones. |
| 36 | + |
| 37 | +## Migration Option 1: Redeployment |
| 38 | + |
| 39 | +### When to use redeployment |
| 40 | + |
| 41 | +Use the redeployment option if you have good Infrastructure as Code (IaC) practices setup to manage infrastructure. The redeployment option gives you more control, and the ability to automate various processes within your deployment pipelines. |
| 42 | + |
| 43 | +### Redeployment considerations |
| 44 | + |
| 45 | +- When you redeploy your VM and VMSS resources, the underlying resources such as managed disk and IP address for the VM are created in the same availability zone. You must use a Standard SKU public IP address and load balancer to create zone-redundant network resources. |
| 46 | + |
| 47 | +- For zonal deployments that require reasonably low network latency and good performance between application tier and data tier, use [proximity placement groups](../virtual-machines/co-location.md). Proximity groups can force grouping of different VM resources under a single network spine. For an example of an SAP workload that uses proximity placement groups, see [Azure proximity placement groups for optimal network latency with SAP applications](../virtual-machines/workloads/sap/sap-proximity-placement-scenarios.md) |
| 48 | + |
| 49 | +### How to redeploy |
| 50 | + |
| 51 | +To redeploy, you'll need to recreate your VM and VMSS resources. To ensure high-availability of your compute resources, it's recommended that you select multiple zones for your new VMs and VMSS. |
| 52 | + |
| 53 | +To learn how create VMs in an availability zone, see: |
| 54 | + |
| 55 | +- [Create VM using Azure CLI](../virtual-machines/linux/create-cli-availability-zone.md) |
| 56 | +- [Create VM using Azure PowerShell](../virtual-machines/windows/create-PowerShell-availability-zone.md) |
| 57 | +- [Create VM using Azure portal](../virtual-machines/create-portal-availability-zone.md?tabs=standard) |
| 58 | + |
| 59 | +To learn how to create VMSS in an availability zone, see [Create a virtual machine scale set that uses Availability Zones](../virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md). |
| 60 | + |
| 61 | +## Migration Option 2: Azure Resource Mover |
| 62 | + |
| 63 | +### When to use Azure Resource Mover |
| 64 | + |
| 65 | +Use Azure Resource Mover for an easy way to move VMs or encrypted VMs from one region without availability zones to another with availability zones. If you want to learn more about the benefits of using Azure Resource Mover, see [Why use Azure Resource Mover?](../resource-mover/overview.md#why-use-resource-mover). |
| 66 | + |
| 67 | +### Azure Resource Mover considerations |
| 68 | + |
| 69 | +When you use Azure Resource mover, all keys and secrets are copied from the source key vault to the newly created destination key vault in your target region. All resources related to your customer-managed keys, such as Azure Key Vaults, disk encryption sets, VMs, disks, and snapshots, must be in the same subscription and region. Azure Key Vault’s default availability and redundancy feature can't be used as the destination key vault for the moved VM resources, even if the target region is a secondary region to which your source key vault is replicated. |
| 70 | + |
| 71 | +### How to use Azure Resource Mover |
| 72 | + |
| 73 | +To learn how to move VMs to another region, see [Move Azure VMs to an availability zone in another region](../resource-mover/move-region-availability-zone.md) |
| 74 | + |
| 75 | +To learn how to move encrypted VMs to another region, see [Tutorial: Move encrypted Azure VMs across regions](../resource-mover/tutorial-move-region-encrypted-virtual-machines.md) |
| 76 | + |
| 77 | +## Disaster Recovery Considerations |
| 78 | + |
| 79 | +Typically, availability zones are used to deploy VMs in a High Availability configuration. They may be too close to each other to serve as a Disaster Recovery solution during a natural disaster. However, there are scenarios where availability zones can be used for Disaster Recovery. To learn more, see [Using Availability Zones for Disaster Recovery](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md#using-availability-zones-for-disaster-recovery). |
| 80 | + |
| 81 | +The following requirements should be part of a disaster recovery strategy that helps your organization run its workloads during planned or unplanned outages across zones: |
| 82 | + |
| 83 | +- The source VM must already be a zonal VM, which means that it's placed in a logical zone. |
| 84 | +- You'll need to replicate your VM from one zone to another zone using Azure Site Recovery service. |
| 85 | +- Once your VM is replicated to another zone, you can follow steps to run a Disaster Recovery drill, fail over, reprotect, and failback. |
| 86 | +- To enable VM disaster recovery between availability zones, follow the instructions in [Enable Azure VM disaster recovery between availability zones](../site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md) . |
| 87 | + |
| 88 | +## Next Steps |
| 89 | + |
| 90 | +Learn more about: |
| 91 | + |
| 92 | +> [!div class="nextstepaction"] |
| 93 | +> [Regions and Availability Zones in Azure](az-overview.md) |
| 94 | +
|
| 95 | +> [!div class="nextstepaction"] |
| 96 | +> [Azure Services that support Availability Zones](az-region.md) |
0 commit comments