|
| 1 | +--- |
| 2 | +title: Relocate Azure Recovery Vault and Site Recovery to another region |
| 3 | +description: Learn how to relocate an Azure Recovery Vault and Site Recovery to a new region |
| 4 | +services: site-recovery |
| 5 | +author: ankitaduttaMSFT |
| 6 | +ms.service: site-recovery |
| 7 | +ms.topic: how-to |
| 8 | +ms.date: 06/25/2024 |
| 9 | +ms.author: ankitadutta |
| 10 | +ms.custom: |
| 11 | + - subject-relocation |
| 12 | +--- |
| 13 | + |
| 14 | +# Relocate Azure Recovery Vault and Site Recovery to another region |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | +This article shows you how to relocate [Azure Recovery Vault and Site Recovery](../site-recovery/site-recovery-overview.md) when moving your workload to another region. |
| 19 | + |
| 20 | + |
| 21 | +[!INCLUDE [Relocation reasons](includes/service-relocation-reason-include.md)] |
| 22 | + |
| 23 | + |
| 24 | +One of the related resources you might want to relocate when you relocate your Azure VMs is your Recovery Services vault configuration. |
| 25 | + |
| 26 | +There's no first-class way to move an existing Recovery Services vault configuration from one region to another. This is because you configured your target region based on your source VM region. When you decide to change the source region, the previously existing configurations of the target region can't be reused and must be reset. This article defines the step-by-step process to reconfigure the disaster recovery setup and move it to a different region. |
| 27 | + |
| 28 | + |
| 29 | +## Prerequisites |
| 30 | + |
| 31 | +- Copy the details replication goal from the SourceRecovery Services vault. |
| 32 | + |
| 33 | +- Copy the details replication policy from the Source Recovery Services vault with the critical details such as: |
| 34 | + |
| 35 | + - *RPO threshold* defines how often recovery points are created. |
| 36 | + - *Recovery point retention* specifies how longer each recovery point is retained. |
| 37 | + - *App-consistent snapshot frequency* specifies how often app-consistent snapshots are created. |
| 38 | + |
| 39 | +- Copy internal resources or settings of Azure Resource Vault. |
| 40 | + - Network firewall reconfiguration |
| 41 | + - Alert Notification. |
| 42 | + - Move workbook if configured |
| 43 | + - Diagnostic settings reconfiguration |
| 44 | + |
| 45 | +- List all Recovery Service Vault dependent resources. The most common dependencies are: |
| 46 | + - Azure Virtual Machine (VM) |
| 47 | + - Public IP address |
| 48 | + - Azure Virtual Network |
| 49 | + - Azure Recovery Service Vault |
| 50 | + |
| 51 | +- Determine network bandwidth need vs. RPO assessment |
| 52 | + - Estimated network bandwidth that’s required for delta replication |
| 53 | + - Throughput that Site Recovery can get from on-premises to Azure |
| 54 | + - Number of VMs to batch, based on the estimated bandwidth to complete initial replication in a given amount of time |
| 55 | + - RPO that can be achieved for a given bandwidth |
| 56 | + - Impact on the desired RPO if lower bandwidth is provisioned |
| 57 | + |
| 58 | +- As it's a relocation of Recovery service vault, you must cross check the permission requirement in the current VMware vCenter server/VMware vSphere ESXi host during profiling. |
| 59 | + |
| 60 | +- Make sure that you remove and delete the Site Recovery configuration before you try to move the Azure VMs to a different region. |
| 61 | + |
| 62 | + > [!NOTE] |
| 63 | + > If your new target region for the Azure VM is the same as the Site Recovery target region, you can use your existing replication configuration and move it. Follow the steps in [Move Azure IaaS VMs to another Azure region](../site-recovery/azure-to-azure-tutorial-migrate.md). |
| 64 | +
|
| 65 | +- Ensure that you're making an informed decision and that stakeholders are informed. Your VM won't be protected against disasters until the move of the VM is complete. |
| 66 | + |
| 67 | + |
| 68 | +## Identify Azure Site Recovery dependencies |
| 69 | + |
| 70 | +We recommend that you do this step before you proceed to the next one. It's easier to identify the relevant resources while the VMs are being replicated. |
| 71 | + |
| 72 | +For each Azure VM that's being replicated, go to **Protected Items** > **Replicated Items** > **Properties** and identify the following resources: |
| 73 | + |
| 74 | +- Target resource group |
| 75 | +- Cache storage account |
| 76 | +- Target storage account (in case of an unmanaged disk-based Azure VM) |
| 77 | +- Target network |
| 78 | + |
| 79 | + |
| 80 | +## Disable the existing disaster recovery configuration |
| 81 | + |
| 82 | +1. Go to the Recovery Services vault. |
| 83 | +2. In **Protected Items** > **Replicated Items**, right-click the machine and select **Disable replication**. |
| 84 | +3. Repeat this step for all the VMs that you want to move. |
| 85 | + |
| 86 | +> [!NOTE] |
| 87 | +> The mobility service won't be uninstalled from the protected servers. You must uninstall it manually. If you plan to protect the server again, you can skip uninstalling the mobility service. |
| 88 | +
|
| 89 | +## Delete the resources |
| 90 | + |
| 91 | +1. Go to the Recovery Services vault. |
| 92 | +2. Select **Delete**. |
| 93 | +3. Delete all the other resources you [previously identified](#identify-azure-site-recovery-dependencies). |
| 94 | + |
| 95 | +## Relocate Azure VMs to the new target region |
| 96 | + |
| 97 | +Follow the steps in these articles based on your requirement to relocate Azure VMs to the target region: |
| 98 | + |
| 99 | +- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md) |
| 100 | +- [Move Azure VMs into Availability Zones](../site-recovery/move-azure-VMs-AVset-Azone.md) |
| 101 | + |
| 102 | +## Set up Site Recovery based on the new source region for the VMs |
| 103 | + |
| 104 | +Configure disaster recovery for the Azure VMs that were moved to the new region by following the steps in [Set up disaster recovery for Azure VMs](../site-recovery/azure-to-azure-tutorial-enable-replication.md). |
0 commit comments