有关从经典部署模型迁移到 Azure Resource Manager 部署模型的常见问题Frequently asked questions about classic to Azure Resource Manager migration

重要

目前,大约有 90% 的 IaaS VM 在使用 Azure 资源管理器Today, about 90% of IaaS VMs are using Azure Resource Manager. 自 2020 年 2 月 28 日起,经典 VM 已弃用,并将于 2023 年 3 月 1 日完全停用。As of February 28, 2020, classic VMs have been deprecated and will be fully retired on March 1, 2023. 详细了解此弃用以及它对你的影响Learn more about this deprecation and how it affects you.

迁移需要多长时间?What is the time required for migration?

计划迁移和执行迁移很大程度都取决于体系结构的复杂性,这可能需要几个月的时间。Planning and execution of migration greatly depends on the complexity of the architecture and could take couple of months.

IaaS VM(经典版)新客户的定义是什么?What is the definition of a new customer on IaaS VMs (classic)?

2020 年 2 月(开始弃用之前的一个月)的订阅中没有 IaaS VM(经典版)的客户则视为新客户。Customers who did not have IaaS VMs (classic) in their subscriptions in the month of Febrauary 2020 (a month before deprecation started) are considered as new customers.

IaaS 虚拟机(经典版)现有客户的定义是什么?What is the definition of an existing customer on IaaS Virtual Machines (classic)?

2020 年 2 月在其订阅中有过活跃的或已停止但曾分配过的 IaaS VM(经典版)的客户则视为现有客户。Customer who had active or stopped but allocated IaaS VMs (Classic) in their subscriptions in the month of February 2020, are considered as an existing customer. 只有这些客户才会在 2023 年 3 月 1 日之后将其 VM 从 Azure Service Manager 迁移到 Azure 资源管理器。Only these customers get until March 1, 2023 to migrate their VMs from Azure Service Manager to Azure Resource Manager.

为什么会收到“NewClassicVMCreationNotAllowedForSubscription”这样的错误信息?Why am I getting an error stating "NewClassicVMCreationNotAllowedForSubscription"?

停用过程开始后,IaaS VM(经典版)不再适用于新客户。As part of the retirement process, IaaS VM (classic) are no longer available for new customers. 我们已将你识别为新客户,因此你无权执行该操作。We identified you as new customers and hence your operation was not authorized. 我们强烈推荐使用使用 ARM 的 Azure 虚拟机We strongly recommend using Azure Virtual Machines using ARM. 如果无法通过 ARM 使用 Azure VM,请联系订阅允许列表上的支持人员。If you cannot use Azure VMs using ARM, please contact support for subscription whitelisting.

此迁移计划是否影响 Azure 虚拟机上运行的任何现有服务或应用程序?Does this migration plan affect any of my existing services or applications that run on Azure virtual machines?

2023 年 3 月 1 日前都是 IaaS VM (经典版),所以不会产生影响。Not until March 1st, 2023 for IaaS VMs (classic). IaaS VM(经典版)是公开上市的完全受支持的服务。The IaaS VMs (classic) are fully supported services in general availability. 可以继续使用这些资源来拓展你在 Azure 上的足迹。You can continue to use these resources to expand your footprint on Azure. 2023 年 3 月 1 日起会全面停用这些 VM,并且会停止或解除分配任何活跃的或分配的 VM。On March 1st, 2023, these VMs will be fully retired and any active or allocated VMs will be stopped & deallocated. 这不会影响到其他经典的资源,如云服务(经典版)、存储帐户(经典版)等。There will be no impact to other classic resources like Cloud Services (Classic), Storage Accounts (Classic), etc.

如果我近期不打算迁移,我的 VM 会出现什么情况?What happens to my VMs if I don't plan on migrating in the near future?

2023 年 3 月 1 日起会全面停用 IaaS VM(经典版),并且会停止或解除分配任何活跃的或分配的 VM。On March 1st, 2023, the IaaS VMs (Classic) will be fully retired and any active or allocated VMs will be stopped & deallocated. 为避免影响业务,我们强烈建议现在就开始计划迁移并在 2023 年 3 月 1 日之前完成迁移。To prevent business impact, we highly recomment to start planning your migration today and complete it before March 1st, 2023. 我们近期不会淘汰现有的经典 API、云服务和资源模型。We are not deprecating the existing classic APIs, Cloud Services and resource model. 我们想要通过 Resource Manager 部署模型中提供的高级功能,让迁移变得简单。We want to make migration easy, considering the advanced features that are available in the Resource Manager deployment model. 我们建议现在开始计划将这些资源迁移到 Azure 资源管理器。We recommend that you start planning to migrate these resources to Azure Resource Manager.

对于我现有的工具而言,此迁移计划有何意义?What does this migration plan mean for my existing tooling?

将工具更新为 Resource Manager 部署模型,是必须在迁移计划中考虑的最重要的更改之一。Updating your tooling to the Resource Manager deployment model is one of the most important changes that you have to account for in your migration plans.

管理平面的停机时间持续多久?How long will the management-plane downtime be?

这取决于迁移的资源数量。It depends on the number of resources that are being migrated. 对于较小型部署(几十个 VM),整个迁移过程应该不超过一小时。For smaller deployments (a few tens of VMs), the whole migration should take less than an hour. 如果是大规模部署(数百个 VM),迁移过程可能需要花费几个小时。For large-scale deployments (hundreds of VMs), the migration can take a few hours.

在 Resource Manager 中提交迁移的资源之后,是否还可以回滚?Can I roll back after my migrating resources are committed in Resource Manager?

只要资源处于准备就绪状态,就可以中止迁移。You can abort your migration as long as the resources are in the prepared state. 但是,在通过提交操作成功迁移资源之后,就不支持回滚。Rollback is not supported after the resources have been successfully migrated through the commit operation.

提交操作失败时,是否可以回滚迁移?Can I roll back my migration if the commit operation fails?

如果提交操作失败,就无法中止迁移。You cannot abort migration if the commit operation fails. 包括提交操作在内的所有迁移操作都是幂等的。All migration operations, including the commit operation, are idempotent. 因此,建议在片刻之后重试操作。So we recommend that you retry the operation after a short time. 如果仍遇到错误,请创建支持票证。If you still face an error, create a support ticket.

如果我必须使用 Resource Manager 下的 IaaS,是否必须购买其他 ExpressRoute 线路?Do I have to buy another express route circuit if I have to use IaaS under Resource Manager?

不会。No. 我们近期实现了 将 ExpressRoute 线路从经典部署模型转移到 Resource Manager 部署模型We recently enabled moving ExpressRoute circuits from the classic to the Resource Manager deployment model. 如果已有 ExpressRoute 线路,则不需要购买新的线路。You don't have to buy a new ExpressRoute circuit if you already have one.

如果我已经为经典 IaaS 资源配置基于角色的访问控制策略,该怎么办?What if I had configured Role-Based Access Control policies for my classic IaaS resources?

在迁移期间,资源从经典资源转换为 Resource Manager 资源。During migration, the resources transform from classic to Resource Manager. 因此,建议计划需要在迁移之后进行的 RBAC 策略更新。So we recommend that you plan the RBAC policy updates that need to happen after migration.

我已在保管库中备份了经典 VM。I backed up my classic VMs in a vault. 是否可以将 VM 从经典模式迁移到 Resource Manager 模式并在恢复服务保管库中保护它们?Can I migrate my VMs from classic mode to Resource Manager mode and protect them in a Recovery Services vault?

将 VM 从经典模式移到资源管理器模式时,在迁移之前进行的备份不会迁移到新迁移的资源管理器 VM 中。When you move a VM from classic to Resource Manager mode, backups taken prior to migration will not migrate to newly migrated Resource Manager VM. 但是,如果希望保留经典 VM 的备份,请在迁移之前执行以下步骤。However, if you wish to keep your backups of classic VMs, follow these steps before the migration.

  1. 在恢复服务保管库中,转到“受保护的项”选项卡并选择 VM。In the Recovery Services vault, go to the Protected Items tab and select the VM.
  2. 单击停止保护。Click Stop Protection. 将“删除关联的备份数据”选项保留为“未选中”状态。Leave Delete associated backup data option unchecked.

备注

在保留数据前将收取备份实例成本。You will be charged backup instance cost till you retain data. 备份副本将按保持期进行删除。Backup copies will be pruned as per retention range. 但是,最后的备份副本会始终保留,直至你显式删除备份数据。However, last backup copy is always kept until you explicitly delete backup data. 建议检查虚拟机的保留期,并在保留期结束后对保管库中受保护项触发“删除备份数据”。It is advised to check your retention range of the Virtual machine and trigger "Delete Backup Data" on the protected item in the vault once the retention range is over.

若要将虚拟机迁移到资源管理器模式,To migrate the virtual machine to Resource Manager mode,

  1. 从 VM 中删除备份/快照扩展。Delete the backup/snapshot extension from the VM.
  2. 将虚拟机从经典模式迁移到 Resource Manager 模式。Migrate the virtual machine from classic mode to Resource Manager mode. 确保与虚拟机对应的存储和网络信息也已迁移到 Resource Manager 模式。Make sure the storage and network information corresponding to the virtual machine is also migrated to Resource Manager mode.

此外,如果想要备份迁移的 VM,请转至“虚拟机管理”边栏选项卡,以启用备份Additionally, if you want to back up the migrated VM, go to Virtual Machine management blade to enable backup.

我是否可以验证订阅或资源,以查看其是否能够迁移?Can I validate my subscription or resources to see if they're capable of migration?

是的。Yes. 在平台支持的迁移选项中,准备迁移的第一个步骤,就是验证资源是否能够进行迁移。In the platform-supported migration option, the first step in preparing for migration is to validate that the resources are capable of migration. 如果验证操作失败,用户会收到包含无法完成迁移的所有原因的消息。In case the validate operation fails, you receive messages for all the reasons the migration cannot be completed.

如果我在准备要迁移的 IaaS 资源时遇到配额错误,会发生什么情况?What happens if I run into a quota error while preparing the IaaS resources for migration?

建议用户中止迁移,并记录支持请求,以在要迁移 VM 的区域中增加配额。We recommend that you abort your migration and then log a support request to increase the quotas in the region where you are migrating the VMs. 配额请求经过批准后,可以重新开始执行迁移步骤。After the quota request is approved, you can start executing the migration steps again.

如何报告问题?How do I report an issue?

请在 Azure 支持上使用关键字 ClassicIaaSMigration 发布有关迁移的问题和疑惑。Post your issues and questions about migration to our Azure support, with the keyword ClassicIaaSMigration. 建议将所有问题都发布在此论坛上。We recommend posting all your questions on this forum. 如果有支持协定,也欢迎你记录支持票证。If you have a support contract, you're welcome to log a support ticket as well.

如果我不喜欢平台在迁移期间选择的资源名称,该怎么做?What if I don't like the names of the resources that the platform chose during migration?

在经典部署模型中为其显式提供名称的所有资源都会在迁移期间得到保留。All the resources that you explicitly provide names for in the classic deployment model are retained during migration. 在某些情况下,会创建新资源。In some cases, new resources are created. 例如:为每个 VM 创建网络接口。For example: a network interface is created for every VM. 目前无法控制迁移期间所创建的这些新资源的名称。We currently don't support the ability to control the names of these new resources created during migration. 请在 Azure 反馈论坛上针对此功能进行投票。Log your votes for this feature on the Azure feedback forum.

不停机无法自动迁移使用跨订阅授权链接的 ExpressRoute 线路。ExpressRoute circuits which use cross-subscription authorization links cannot be migrated automatically without downtime. 我们提供了有关如何使用手动步骤迁移这些线路的指南。We have guidance on how these can be migrated using manual steps. 有关步骤和详细信息,请参阅将 ExpressRoute 线路和关联的虚拟网络从经典部署模型迁移到 Resource Manager 部署模型See Migrate ExpressRoute circuits and associated virtual networks from the classic to the Resource Manager deployment model for steps and more information.

我收到消息,指出 “VM 报告总体代理状态为‘未就绪’。因此,此 VM 无法迁移。请确保 VM 代理报告总体代理状态为‘就绪’”“VM 包含未报告其状态的扩展。因此,此 VM 无法迁移。”I got the message "VM is reporting the overall agent status as Not Ready. Hence, the VM cannot be migrated. Ensure that the VM Agent is reporting overall agent status as Ready" or "VM contains Extension whose Status is not being reported from the VM. Hence, this VM cannot be migrated."

当 VM 未建立到 Internet 的出站连接时,会收到此消息。This message is received when the VM does not have outbound connectivity to the internet. VM 代理使用出站连接访问 Azure 存储帐户,每隔五分钟更新一次代理状态。The VM agent uses outbound connectivity to reach the Azure storage account for updating the agent status every five minutes.

后续步骤Next steps