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/backup/backup-azure-move-recovery-services-vault.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,22 +22,22 @@ France Central, France South, Germany Northeast, Germany Central, US Gov Iowa, C
22
22
23
23
- During vault move across resource groups, both the source and target resource groups are locked preventing the write and delete operations. For more information, see this [article](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-move-resources).
24
24
- Only admin subscription has the permissions to move a vault.
25
-
- For moving vault across subscriptions, the target subscription must reside in the same tenant as the source subscription and its state should be enabled.
25
+
- For moving vaults across subscriptions, the target subscription must reside in the same tenant as the source subscription and its state should be enabled.
26
26
- You must have permission to perform write operations on the target resource group.
27
-
- Moving the vault only changes the resource group. The Recovery Services vault will reside on the same location and it cannot be changed.
27
+
- Moving the vault only changes the resource group. The Recovery Services vault will reside on the same location and it can't be changed.
28
28
- You can move only one Recovery Services vault, per region, at a time.
29
-
- If a VM doesn’t move with the Recovery Services vault across subscriptions, or to a new resource group, the current VM recovery points will remain intact in the vault until they expire.
29
+
- If a VM doesn't move with the Recovery Services vault across subscriptions, or to a new resource group, the current VM recovery points will remain intact in the vault until they expire.
30
30
- Whether the VM is moved with the vault or not, you can always restore the VM from the retained backup history in the vault.
31
31
- The Azure Disk Encryption requires that the key vault and VMs reside in the same Azure region and subscription.
32
32
- To move a virtual machine with managed disks, see this [article](https://azure.microsoft.com/blog/move-managed-disks-and-vms-now-available/).
33
-
- The options for moving resources deployed through the Classic model differ depending on whether you are moving the resources within a subscription, or to a new subscription. For more information, see this [article](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-move-resources).
33
+
- The options for moving resources deployed through the Classic model differ depending on whether you're moving the resources within a subscription, or to a new subscription. For more information, see this [article](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-move-resources).
34
34
- Backup policies defined for the vault are retained after the vault moves across subscriptions or to a new resource group.
35
-
- Moving vault with the Azure Files, Azure File Sync, or SQL in IaaS VMs across subscriptions and resource groups is not supported.
35
+
- Moving vaults with the Azure Files, Azure File Sync, or SQL in IaaS VMs across subscriptions and resource groups isn't supported.
36
36
- If you move a vault containing VM backup data, across subscriptions, you must move your VMs to the same subscription, and use the same target VM resource group name (as it was in old subscription) to continue backups.
37
37
38
38
> [!NOTE]
39
-
>
40
-
> Recovery Services vaults configured to use with **Azure Site Recovery** can’t move, yet. If you have configured any VMs (Azure IaaS, Hyper-V, VMware) or physical machines for disaster recovery using the **Azure Site Recovery**, the move operation will be blocked. The resource move feature for Site Recovery service is not yet available.
39
+
>Moving Recovery Services vaults for Azure Backup across Azure regions isn't supported.<br><br>
40
+
> If you have configured any VMs (Azure IaaS, Hyper-V, VMware) or physical machines for disaster recovery using **Azure Site Recovery**, the move operation will be blocked. If you want to move vaults for Azure Site Recovery, review [this article](https://docs.microsoft.com/azure/site-recovery/move-vaults-across-regions) to learn about moving vaults manually.
41
41
42
42
## Use Azure portal to move Recovery Services vault to different resource group
43
43
@@ -48,15 +48,15 @@ To move a recovery services vault and its associated resources to different reso
48
48
49
49
50
50
51
-
If you do not see the **Essentials** information for your vault, click the drop-down icon. You should now see the Essentials information for your vault.
51
+
If you don't see the **Essentials** information for your vault, click the drop-down icon. You should now see the Essentials information for your vault.
52
52
53
53
54
54
55
55
3. In the vault overview menu, click **change** next to the **Resource group**, to open the **Move resources** blade.
4. In the **Move resources** blade, for the selected vault it is recommended to move the optional related resources by selecting the checkbox as shown in the following image.
59
+
4. In the **Move resources** blade, for the selected vault it's recommended to move the optional related resources by selecting the checkbox as shown in the following image.
After executing the above cmdlets, you will be asked to confirm that you want to move the specified resources. Type **Y** to confirm. After a successful validation, the resource moves.
120
+
After executing the above cmdlets, you'll be asked to confirm that you want to move the specified resources. Type **Y** to confirm. After a successful validation, the resource moves.
0 commit comments