Getting started
Configuring GCP
Configuring the Migrate for Compute Engine Manager
Migrate on-premises VMs to GCP
-
Overview of on-premises to GCP migration
Migrate VMs to GCP.
-
Deploying the Migrate for Compute Engine on-premises backend
Deploy and configure the Migrate for Compute Engine backend.
-
Running and Migrating VMs
Use the vCenter plugin to start running or migrating individual VMs to GCP.
-
Migrating on-premises storage to GCP
Migrate on-premises storage to GCP.
-
Powering on, restarting, or shutting down a VM
Control VMs during a migration.
-
Reconfiguring a VM
Change the VM's instance type and storage policy using the Reconfigure Cloud Instance.
-
Detaching a VM
Prepare the VM for detach from Migrate for Compute Engine.
-
Moving a VM back on-premises
Moving a VM back to its source, and considerations on VM behaviors and storage.
Migrate AWS to GCP
-
Overview of AWS to GCP migration
General steps required for migrating VMs from AWS EC2 to GCP.
-
Migrate for Compute Engine AWS prerequisites
Prepare to migrate your AWS EC2 instances to GCP.
-
Configuring AWS as a source
Use AWS as a source for migrating VMs to GCP.
-
Migrating AWS VMs to GCP
Migrate VMs from AWS to Google Cloud Platform (GCP) using Migrate for Compute Engine.
Using Cloud Extensions
-
Setting up a Cloud Extension
General steps for creating a Cloud Extension, which connects GCP to your source VMs.
-
Setting up an HTTP(S) proxy
Configure a secure proxy for migration information.
-
Stopping, starting, and reconfiguring a Cloud Extension
Controlling a Cloud Extension.
-
Repairing a Cloud Extension
Fixing issues with Cloud Extensions, such as connectivity loss.
-
Deleting a Cloud Extension
Deleting a Cloud Extension.
Networking
-
Using multiple IP addresses
IP considerations and using multiple IP addresses with Migrate for Compute Engine.
-
Using external DNS
Configuring GCP and Migrate for Compute Engine to support external DNS.
-
Setting migration bandwidth throttling
Prevent network saturation for storage migration by throttling bandwidth usage.
Organizing migrations with waves
-
Overview of migration waves
Migrate for Compute Engine subdivides a migration sprint into a series of Waves, which group the VMs that run your application into batches for migration.
-
Creating and modifying runbooks
Create runbooks, which define the VMs in a wave.
-
Creating new waves
Create waves to organize and run your migrations.
-
Creating and aborting jobs
Migrate for Compute Engine defines a job as an operation performed on a group of VMs defined in a runbook.
-
Rightsizing instances in a wave
Choose the right size of VMs to migrate to, or use one of Migrate for Compute Engine's rightsizing methods to choose for you.
-
Monitoring waves, runbooks, and jobs
Monitoring wave status and view logs for your migration.
-
Migrating to sole-tenant nodes and Windows BYOL
Migrate to sole-tenant nodes and supporting Bring your own Windows licenses.
Testing migrated workloads
Monitoring Migrate for Compute Engine
-
Monitoring overview
Monitoring your Migrate for Compute Engine environment.
-
Using Stackdriver monitoring
Use Google Cloud Observability to monitor your Migrate for Compute Engine environment.
-
Viewing Stackdriver logs
Use Google Cloud Observability to view logs from your Migrate for Compute Engine environment.
-
Alarms and events
Types of alarms and how they display in Migrate for Compute Engine.
-
Monitoring the Cloud Extension
Monitor the current run state of the Cloud Extension.
-
Viewing a cloud instance's console log
View the console log of a VM running on Google Cloud Platform (GCP) from vCenter or the Wave UI.
-
Disabling Google Cloud Observability Monitoring
Disabling Google Cloud Observability Monitoring in Migrate for Compute Engine.
Automating migration tasks
Additional preparations for VMs and servers
-
Adaptation scripts overview
Customization / adaptation scripts to allow your VMs operate properly within the constraints of their new environment.
-
Windows adaptations
Windows adaptation scripts that Migrate for Compute Engine provides.
-
Linux adaptations
Linux adaptation scripts that Migrate for Compute Engine provides.
-
Preparing Linux VMs
Required customizations and adaptations for Linux VMs migrating to GCP.
-
Migrating physical servers
Migrating physical servers has the same prerequisites as migrating VMware VMs.
-
Using offline migration
Migrate for Compute Engine enables you to migrate workloads with operating systems that are not currently supported by Migrate for Compute Engine's streaming technology using offline migration.
-
Using premium OS licenses
Google Cloud Platform supports premium enterprise Linux distributions such as Red Hat Enterprise Linux (RHEL) or SuSE Linux Enterprise (SLES).