Migrate Azure Recovery Services vault to availability zone support

This article describes how to migrate Recovery Services vault from non-availability zone support to availability zone support.

Recovery Services vault supports local redundancy, zone redundancy, and geo-redundancy for storage. Storage redundancy is a setting that must be configured before protecting any workloads. Once a workload is protected in Recovery Services vault, the setting is locked and can't be changed. To learn more about different storage redundancy options, see Set storage redundancy.

To change your current Recovery Services vault to availability zone support, you need to deploy a new vault. Perform the following actions to create a new vault and migrate your existing workloads.

For more detailed information about availability zone and disaster recovery support for Azure Backup services and data redundancy, see Reliability for Azure Backup.

Prerequisites

Standard SKU is supported.

Downtime requirements

Because you're required to deploy a new Recovery Services vault and migrate your workloads to the new vault, some downtime is expected.

Considerations

When switching recovery vaults for backup, the existing backup data is in the old recovery vault and can't be migrated to the new one. 

Migration Step: Deploy a new Recovery Services vault

To change storage redundancy after the Recovery Services vault is locked in a specific configuration:

1. Deploy a new Recovery Services vault.

2. Configure the relevant storage redundancy option. Learn how to Set storage redundancy.

Choose an Azure service:

Azure Backup

If your workloads are backed-up by the old vault and you want to re-assign them to the new vault, follow these steps:

1. Stop backup for:

   1. Virtual Machines.

   2. SQL Server database in Azure VM.

   3. Storage Files.

   4. SAP HANA database in Azure VM.

2. To unregister from old vault, follow these steps:

   1. Virtual Machines.

   2. SQL Server database in Azure VM.

      Move the SQL database on Azure VM to another resource group to completely break the association with the old vault.

   3. Storage Files.

   4. SAP HANA database in Azure VM.

      Move the SAP HANA database on Azure VM to another resource group to completely break the association with the old vault.

3. Configure the various backup items for protection in the new vault.

Important

Existing recovery points in the old vault is retained and objects can be restored from these. However, as protection is stopped, backup policy no longer applies to the retained data. As a result, recovery points won't expire through policy, but must be deleted manually. If this isn't done, recovery points are retained and indefinitely incurs cost. To avoid the cost for the remaining recovery points, see Delete protected items in the cloud.

Azure Site Recovery

If you have any workloads in the old vault that are currently protected by Azure Site Recovery, see the following sections.

Azure to Azure replication

1. Disable replication in the old vault. See Disable protection for an Azure VM (Azure to Azure).

2. Enable replication in the new vault. See Enable replication.

3. If you don't need the old Recovery Service vault, you can then delete it (provided it has no other active replications). To delete the old vault, see Delete a Site Recovery Services vault.

VMware to Azure replication

Learn about Registering a VMware configuration server with a different vault.

Physical to Azure replication

Learn about Registering a configuration server with a different vault.

Hyper-V Site to Azure replication

Follow these steps:

1. Unregister the server in the old vault. See Unregister a Hyper-V host in a Hyper-V site.

2. Enable replication in the new vault.

Hyper-V VM to Azure replication

1. Disable replication in the old vault. See Disable protection for a Hyper-V virtual machine (Hyper-V to Azure).

2. Enable replication in the new vault.

SCVMM to Azure replication

1. Disable replication in the old vault. See Disable protection for a Hyper-V virtual machine replicating to Azure using the System Center VMM to Azure scenario.

2. Enable replication in the new vault.

Next steps

• Reliability for Azure Backup
• Azure services and regions that support availability zones