Copy the disk (VHD file) from the managed disk to the storage account created in the target region.Create a storage account in the target region.Enable the Export function to generate a single URL containing the VHD of the managed disk to migrate.Of course, you could go through the whole manual process of: So what happens if the VNET is in a different resource group? Or the resource group contains more than one resource except the one VM we want to move? We might end up creating too many resources than we intended. It exports the whole resource group, and nothing but the resource group. Just export the template from the VM’s resource group, replace some strings and re-deploy the whole thing, right? No.Įxporting the resource group to an ARM template is exactly that. Using an ARM template sounds like an obvious solution. It can create the virtual network for you, but not the NSG, nor the public IP.For example, you cannot move a VM from US to Europe, or from Europe to Australia (check the compatibility matrix for more information on this). You can move VMs only between any two regions within the same geographic cluster.It has a long list of prerequisites and preparations to complete before you start.Though it is the current recommended approach, it still has several downsides: ![]() ![]() ![]() You could move your VMs using Azure Site Recovery. Additional reasons would be to improve manageability, or to move for governance reasons. In this scenario, you’d want to move your VMs as is to the new region to reduce latency. For example, if you already deployed in one region, and a new region support was added which is closer to the end users of your application or service. There are various scenarios in which you would want to move your existing Azure IaaS virtual machines (VMs) from one region to another.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |