windows脚本 Migrating Windows Workload VMs

脚本

To deploy the Migrate for Compute Engine infrastructure,you'll need to follow a few steps。 Migrate for Compute Engine uses a secure VPN tunnel or interconnect to connect your source environmentwindows脚本, and requires a setup of specific networking rules before migrations can begin。 After network is set up, you'll need to create Google Cloud roles and service accounts that Migrate for Compute Engine can use to create Google Cloud resources and manage the Cloud Storage API。 Migrate for Compute Engine includes a Cloud Shell script for making these changes。

When your Google Cloud project is configured properly, you can deploy the Migrate for Compute Engine Manager from Google Cloud Marketplace, in just a few clicks。 You then deploy the appropriate appliance, based on your source environment。 A backend on vSphere if you're migrating virtual machines from one premises or an importer if you're migrating from Zoom。 To complete the process, you deploy a Cloud extension back at the destination environment。 After installing Migrate for Compute Engine in your source environment in Google Cloud, you can start the migration process which is composed of three main phases。

The first phase is called Full Migration。 Migrate for Compute Engine will execute three sub-steps。 Run in Cloud sub-step。 The process starts by turning off the source virtual machine and creating an image。 If you migrate to Windows machine, the process will perform relevant adaptations to the Cloud environment automatically。 When the image is ready for the Cloud, it will be streamed to the Cloud extension and boot within a few minutes。 Migrate for Compute Engine then streams any data on demand when the migrated virtual machine needs it。

The Storage Migration sub-step, proactively migrates the full data to the Cloud so that streaming is no longer necessary。 When Storage migration is completed, Migrate for Compute Engine prepares to detach, which copies all the cached data from the previous operations to a native Compute Engine persistent disk。 It's important to note that you can manually go through each of these phases, but we recommend automatically executing them sequentially by choosing full migration。 Full migration is just the first out of three steps。

After full migration is completed, all reads and writes from the migrated virtual machine still go through the Cloud extension to avoid interrupting the migrating Machine's operation。 When you're ready to fully detach from the Cloud extension, which involves a brief downtime, you can initiate the detach step。 It moves the remaining data in the Cloud extension to the native persistent disk and then shuts down the migrated virtual machine so it can boot natively and securely from this persistent disk, thus becoming fully independent。 Finally, a cleaner remote VM is unmanaged by Migrate from Compute Engine and remove migrational defects。

（编辑：重庆站长网）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!