Options: full migration includes (run in cloud, migrate storage, detach). Run in cloud mean the compute is on GCP, storage is still at the source.
Cross-OS through adaptions. Optionally, you can write custom configurations for Linux as needed.
Agentless: i.e. there is no agent installed on the source VM, instead a separate standalone manager is set up.
Migrate for Compute Engine v. 4.2. V5 is WIP which will be managed service (!? is it not now?)
Supports on-prem, AWS. Azure is in beta.
Online/offline migration: offline migration is needed when the entire storage needs to be migrated before the VM can be made available on the cloud (e.g. Windows VMs)
Waves, runbooks.
Processes:
Test clone option
Stream compute (Run in cloud)
Migrate storage: while the remote VM still can access data on source’s storage (through Cloud Extension)
Detach and cleanup.
Switch access to source’s storage to cloud native
On GCP:
Velostrata Manager: GCE instance deployed through Marketplace
Cloud Extension: used to migrate VMs/data
On VMWare:
Velostrata backend: appliance in the Data center; extension of Velostrata manager; required by Velostrata vCenter Plugin
Velostrata vCenter Plugin
On AWS:
VM Importer: run on EC2 instance, takes over the disks to be migrated and streams the data to the Cloud Extension.