Azure Resource Mover is a new service in Azure that lets you move resources across regions.
• Move resources from one resource group to another resource
group
• Move resource from one Azure subscription to another
Azure resource mover supports only the following types of resources
• Azure VMs and associated disks
• NICs
• Availability sets
• Azure virtual networks
• Public IP addresses
• Network security groups (NSGs)
• Internal and public load balancers
• Azure SQL databases and elastic pools
Azure Resource Mover requires either Owner or Contributor and User Access Administrator permissions on subscription level for the first time resources are moved for a source / target region pair.
Moving a VM from East US to West US
1) Log in to Azure Portal as Global Administrator
2) Click on Resource groups and click on the Source Resource group
3) Select resources need to move to another region (or) you can search for Azure Resource Mover in the Azure portal and using the Resource Mover interface you specify the subscription and the source as well the target region.
4) Click on move then click on move to another region
Note: If you are moving an VM, do not select VM disks separately. VM disks are moved as part of the selected VM. Otherwise, it will give an error during the validation.
5) Select West US as the destination region. Then click on Next to proceed.
6) In Move resources window, verify there are no errors. Then click Next to proceed
7) In the Review + Add page, accept the changes and click on Proceed.
8) In Azure Resource Mover page. Click on validate dependencies before starting the prepare step.
9) When dependencies exist add them to the resource list with add dependencies.
10) Once dependencies are added, select the source resource group you want to move and click on prepare but only for the resource group.
Note: It is a requirement that the resource group need to be moved first before you start with the other resources.
11) The next steps are prepare, initiate move and commit move.
12) Once resource group status is changed to ‘Initiate move‘ pending, select it and click on Initiate move
13) On the next page, verify the selection of resources and click on Initiate Move
14) After a few minutes the status of the resource group will change to ‘Commit move‘ pending. Then select it and click on Commit Move.
15) On the next page, verify the selection of resources and click on Commit.
16) Once the resource group status changed to ‘Delete source‘ pending. This means the move is completed for the resource group.
17) Now follow the same steps (Prepare, Initiate move & Commit move) and move other resources.
18) Prepare step will take time to complete when moving a VM and in the background the Azure Site Recovery agent gets installed on the VM and the replication process is set upped.
Note: Azure Resource Mover uses an Azure Site Recovery vault in the backend for moving VMs across regions.
19) Once the other resources status is changed to ‘Initiate move‘ pending, select it and click on Initiate move. During the initiate move step, the source VM gets deallocated and the target VM will get started.
20) Once the move is completed, we can see all the resources under the new resource group.
21) After a few minutes the status of the resources will change to ‘Commit move‘ pending. Then select it and click on Commit Move.
22) All resources have now the status delete source pending which indicates a successful move.
23) The VM runs in West US and the source VM in East US is deallocated.
24) Logged in to the VM in the new resource group. As expected, it is working.
25) Before removing the resources from Azure Resource Mover, you should delete the source resources first.
URLs:
· https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-region
No comments:
Post a Comment