借助 Migrate to Virtual Machines,您可以将虚拟机和虚拟机磁盘从以下四个迁移来源迁移到 Google Cloud:
vSphere 数据中心(本地)
AWS 云服务
Azure 云服务
Google Cloud VMware Engine
下图展示了将虚拟机和虚拟机磁盘从各种迁移来源迁移到 Google Cloud的架构:
Google Cloud 项目简介
Google Cloud 项目是执行下列操作的基础:创建、启用和使用 Google Cloud 服务,包括管理 API、启用结算功能、添加和移除协作者以及管理 Google Cloud 资源的权限。
Google Cloud 控制台
Google Cloud console 是 Google Cloud的图形界面。使用 Google Cloud 控制台管理迁移的所有方面、访问监控和日志记录数据,以及配置身份验证和授权。
Cloud IAM
借助 Identity and Access Management (IAM),您可以控制对特定 Google Cloud 资源的访问权限,并阻止对资源的不必要访问。为了让用户能够创建和管理您的 Compute Engine 资源,您可以将用户作为团队成员添加到项目或特定资源,然后使用 IAM 角色向这些用户授予权限。
迁移来源和目标
迁移的定义包括:
迁移来源:托管要迁移的虚拟机或虚拟机磁盘的本地数据中心或云服务。您可以在宿主项目上定义多个来源。
迁移目标: Google Cloud上的 Compute Engine 虚拟机或永久性磁盘卷。
宿主项目:用于控制迁移过程的项目称为宿主项目。在宿主项目中,启用 Migrate to Virtual Machines 服务以及 Migrate to Virtual Machines 所需的任何其他服务。启用后,您可以开始将来源虚拟机从宿主项目迁移到迁移目标。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-19。"],[],[],null,["# Migrate to Virtual Machines architecture\n\nMigrate to Virtual Machines lets you migrate VMs and disks of VMs from the\nfollowing four migration sources to Google Cloud:\n\n- vSphere data center (on-premises)\n- AWS cloud service\n- Azure cloud service\n- Google Cloud VMware Engine\n\nThe following diagram shows the architecture for migrating VMs and disks of VMs\nfrom various migration sources to Google Cloud:\n\n\u003cbr /\u003e\n\n[](../images/m2vm_architecture.svg)\n\n\u003cbr /\u003e\n\nAbout Google Cloud projects\n---------------------------\n\n[Google Cloud projects](/resource-manager/docs/creating-managing-projects)\nform the basis for creating, enabling, and using Google Cloud services\nincluding managing APIs, enabling billing, adding and removing collaborators,\nand managing permissions for Google Cloud resources.\n\n### Google Cloud console\n\n[Google Cloud console](https://console.cloud.google.com/) is the graphical user interface for Google Cloud.\nUse the Google Cloud console to manage all aspects of migration, access monitoring\nand logging data, and to configure authentication and authorization.\n\n### Cloud IAM\n\n[Identity and Access Management (IAM)](/compute/docs/access) lets you control\naccess to specific Google Cloud resources and prevents unwanted access to\nyour resources. To give users the ability to create and manage your\nCompute Engine resources, you can add users as team members to your project or\nto specific resources and grant them permissions using IAM roles.\n\nMigration sources and targets\n-----------------------------\n\nA migration is defined by:\n\n- The *migration source*: An on-premises data center or cloud service hosting\n the VMs or VM disks that you want to migrate. You can define multiple sources\n on a host project.\n\n- The *migration target*: A Compute Engine VM or Persistent Disk volumes\n on Google Cloud.\n\n- The *host* project: The project you use to control the migration process is\n referred to as your *host* project. Within your host project, you enable the\n Migrate to Virtual Machines service and any other services required by\n Migrate to Virtual Machines. Once enabled, you can begin migrating source VMs\n from the host project, to your migration targets.\n\n- The *target* project: The project that hosts the migration target. You can\n have multiple target projects to which you can migrate your VMs.\n\n### Migration sources\n\nMigrate to Virtual Machines lets you to migrate VMs from the following four\nmigration sources:\n\n- vSphere data center: Migrate on-premises VMs from the vSphere data center to Google Cloud.\n- VMware Engine data center: Migrate VMs from the VMware Engine data center to Compute Engine.\n- AWS Cloud service: Migrate your EC2 instances from your AWS account to Google Cloud.\n- Azure Cloud service: Migrate your VM instances from your Azure account to Google Cloud.\n\n### Migration targets\n\nA *migration target* is defined as the following:\n\n- For [VM migration](/migrate/virtual-machines/docs/5.0/migrate/migrating-vms), the *migration target* is an instance of Compute Engine running on Google Cloud.\n- For [disk migration](/migrate/virtual-machines/docs/5.0/migrate/migrating-disks), the *migration target* are Persistent Disk volumes running on Google Cloud.\n\nThe project that contains the *migration target* is called the *target* project.\nYou can use your host project as a target project, or you can migrate to\nadditional projects. For more information, see [Adding a target project](/migrate/virtual-machines/docs/5.0/get-started/target-project).\n\nUse multiple target projects to isolate migrated VMs or disks from each other.\nFor example, it is recommended to isolate a Compute Engine VM used for\ntesting from those used for production. You can use projects and VPCs to create\nsandbox environments for testing that are separate from your production\nenvironments. For more information, see\n[Decide a resource hierarchy for your Google Cloud landing zone](/architecture/landing-zones/decide-resource-hierarchy).\n\nYou can also use the [Deployment Manager](/deployment-manager/docs/fundamentals)\nto deploy migrated VMs or VM disks to production across multiple projects.\nSee [Using Images from Other Projects](/deployment-manager/docs/configuration/using-images-from-other-projects-for-vm-instances) for more.\n\nAlong with the Migrate to Virtual Machines services, you also use the following\nGoogle Cloud services when performing a migration.\n\n#### Compute Engine\n\n[Compute Engine](/compute/docs) lets you create and run VMs on\nGoogle Cloud. Compute Engine offers scale, performance, and value\nthat lets you launch large compute clusters on Google's infrastructure.\n\nAs part of defining the migration target, you set the project of the\nCompute Engine VM. The characteristics of the target Compute Engine\ninstance are based on the requirements of the migrated VM. You can customize the\nCompute Engine VM to specify:\n\n- Google Cloud project\n- Number of CPUs\n- Amount of memory\n- Disk type\n- Network configuration\n- many other options\n\nYou might have different requirements on the target Compute Engine VM\nbased on whether the instance is being used for testing a migrated VM or being\nused in a production environment. For example, you might test the migrated VM in\na single Compute Engine VM with 2 CPUs and 8 GB of RAM. Then, when\nyou move to a production environment, you define target Compute Engine\ninstances with different characteristics, such as 4 or 8 CPUs, and 16 GB of\nRAM.\n\n#### Persistent Disk\n\n[Persistent Disk](/compute/docs/disks#pdspecs) are durable network storage\ndevices that your Compute Engine VMs can access like physical disks in a\ndesktop or a server. The data on each persistent disk is distributed across\nseveral physical disks. Compute Engine manages the physical disks and the data\ndistribution for you to ensure redundancy and optimal performance.\n\nWhat's next\n-----------\n\n- [VM Migration lifecycle](/migrate/virtual-machines/docs/5.0/discover/lifecycle)\n- [Migrate from a VMware source](/migrate/virtual-machines/docs/5.0/migrate/create-a-vmware-source)\n- [Migrate from an AWS source](/migrate/virtual-machines/docs/5.0/migrate/create-an-aws-source)\n- [Migrate from an Azure source](/migrate/virtual-machines/docs/5.0/migrate/create-an-azure-source)"]]