Quotas and limits

To reduce the risk of abuse, Google Cloud Platform (GCP) enforces limits on the usage of GCP services. New GCP customers using Migrate for Compute Engine should familiarize themselves with the limits that are applicable to their migration.

Migrate for Compute Engine uses the following Google Cloud Platform (GCP) resources which are subject to limits:

GCP Resource How used in Migrate for Compute Engine
Compute instances Needed to support migrated VMs, Velostrata Manager, Cloud Extensions, and worker nodes.
Persistent disks When deploying Cloud Extensions, ensure that you have SSD (solid-state disk) Persistent Disk quota set high enough to support the number of Cloud Extensions you intend to create. For more, see Cloud Extensions Overview.
External IP addresses The migration process creates Compute Engine VMs, and can create IP addresses for access over the public Internet (such as for inbound access from your corporate data center).
Cloud Storage While you are migrating, Migrate for Compute Engine uses Cloud Storage to hold data that is used by your applications on Compute Engine VMs.
VPC networks Migrate for Compute Engine uses Virtual Private Cloud (VPC) for secure access to GCP during migration. Ensure that your quotas for networks, subnets, IP addresses, and more will support your migration.

The number of worker nodes is equal to the number of VMs that are in Prepare to Detach or Detach phases.

Viewing your current quota usage

Console

The quotas page on the Google Cloud Platform Console shows your project's current quotas and their usage.

Requesting increases to your quotas

See the Compute Engine documentation for instructions on how to request a quota increase.

Send feedback about...

Migrate for Compute Engine - Cloud Migration Software for GCP