Shulou(Shulou.com)06/03 Report--

Today, let's talk about the migration of ASM and ARM. ASM and ARM are two different modes in Azure. ASM is a very old mode, which has a lot of inconveniences compared with ARM mode.

For example, ASM creation resources can only be serial, there is no way for multiple resources to be created in parallel, resources cannot be tag, and there are many problems such as high coupling between components. So Microsoft has been recommending customers to use ARM resources for a long time.

In many cases, users who have created ASM resources, such as virtual machines, are now preparing to migrate to ARM. So how to migrate? let's introduce it today. Coincidentally, I have an ASM resource from a long time ago in Global Azure that I can experiment with.

Generally speaking, the migration of VM from ASM to ARM can be divided into two situations.

1:VM shutdown migration

This situation is relatively simple. First copy a vhd file through Azcopy, create a disk directly through vhd, and then create an ARM VM through disk.

2:VM boot migration

It's a little more complicated, but it's actually very simple. First, take a snapshot of the disk, then export the snapshot to vhd, use vhd to create disk, and then create ARM VM through disk. This method is common to both HDD and SSD disks.

Generally speaking, for this kind of tedious operation, I write PowerShell scripts to execute, in Mooncake, this is a last resort, but in Global Azure, we can actually be much simpler.

After selecting an ASM vm, you can see that there is an option that is directly migrate to ARM. It's really simple and rude. I like it very much.

First of all, some checks should be carried out before migration, because there are actually many elements that do not support migration.

During the verification process

You can see that there is a problem with the verification, because there is an extension that does not support migration, so the verification fails

It doesn't matter. Go directly to VM, select extension, and then uninstall the extension directly.

Endpoint rules can also lead to failure. After deleting the rules, verify it again. At this time, it is finally successful.

The second step is to prepare for the migration.

After the preparation is completed, it will tell us which resource group the resources will be placed in after migrating to ARM mode. In addition, it will also delete and indicate that the ASM resources before migration will be deleted. After entering yes, click commit.

Has begun to migrate.

After waiting for some time, the migration has been completed

The previous ASM resources have been gone, replaced by ARM resources!

If Public IP is Reserved IP, then it can be retained, because my IP is dynamic, so it will be gone after migration

In addition, the unmanaged disk is used after the migration, which can be updated manually

At this point, what we see is a brand new ARM virtual machine! The experience is completely different from that of mooncake.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.