Google Cloud Platform: VM Import

Google Cloud Platform bundles free CloudEndure as part of VM import, that is good saving compared to AWS marketplace where this costs $399/migration.

CloudEndure is commercial tools that allows live migration or DR of physical/virtual/cloud servers to another physical/virtual/cloud servers using replication technology. It supports physical servers, VMware, and all major clouds including: AWS, Microsoft Azure, Google Cloud Platform, and OpenStack. If needed, it is just as easy to use CloudEndure to migrate back from the cloud to on-premise or other cloud targets. It supports Windows and Linux migrations.

https://www.cloudendure.com/
https://cloud.google.com/compute/docs/tutorials/migrating-vms-compute-engine

Architecture Overview:

Videos:

Documentation:
https://docs.cloudendure.com/home/
It also has REST API, yet you have to request this from Cloudendure

How to configure for migration from AWS (with Amazon LInux)  to GCP:

1. Compute Engine ->  VM Instances -> Import VM (this lands in CloudEndure)
2. Create Service account key and download: API Manager -> Credentials -> Create Credentials -> Service account key - Select type JSON, Select Compute Engine default service account, See video here
3. In CloudEndure account provide your project ID and service account access key (the JSON key file you downloaded before).
4. On source instance: yum install -y gcc kernel-devel-4.4.41-36.55.amzn1.x86_64; wget -O ./installer_linux.py https://gcp.cloudendure.com/installer_linux.py; python ./installer_linux.py -t 96BB-9452-3E90-7D02-8A3B-FBBA-3E06-0188-4CC7-0D11-BA98-759A-8D46-2065-DC05-8E31, this will automatically start syncing all disks to target GCP persitant disk target.
5. Use Cloudendure console to process migration - https://gcp.cloudendure.com/#/liveMigration

Please note when CloudEndure is syncing data from source to replicator it is writing to standard persistent disk only, no target instance is yet created. Only when test/cutover is invoked is a target instance/disk created (as per blueprint specifications). Wait until systems are synced/ Once DATA REPLICATION PROGRESS status is in Continuous Data Protection the disks have been synced. At this stage options are

• Test: This will create a new target VM from standard persistent disk. Please note this can be done many times as data is continually asynchronously synced from source to standard persistent disk. Prior to this can specify blueprint for target machine type/subnet/persistent disk type:Here is sample log for Test:
• 3/16/2017, 11:25:36 PM Started creating replica
  3/16/2017, 11:25:36 PM Started waiting for latest snapshot
  3/16/2017, 11:26:06 PM Finished waiting for latest snapshot
  3/16/2017, 11:26:06 PM Started deleting replica
  3/16/2017, 11:26:09 PM Finished deleting replica
  3/16/2017, 11:26:09 PM Starting converters
  3/16/2017, 11:27:25 PM Finished starting converters
  3/16/2017, 11:27:25 PM Started creating disk vol-i-0243c6eb91830fe34:/dev/xvda
  3/16/2017, 11:27:25 PM Started creating firewall
  3/16/2017, 11:27:58 PM Finished creating firewall 4237851938389441089
  3/16/2017, 11:28:15 PM Finished creating disk 2856654472483387969
  3/16/2017, 11:28:15 PM Started creating a replica for machine i-0243c6eb91830fe34
  3/16/2017, 11:28:48 PM Finished creating a replica for machine i-0243c6eb91830fe34
  3/16/2017, 11:28:49 PM Finished creating replica

• Delete target machine: This will delete target VM. Here is sample log for Delete target machine:
  3/16/2017, 11:48:35 PM Started deleting replica
  3/16/2017, 11:48:36 PM Started cleanup of instance 6606330955351669296
  3/16/2017, 11:51:43 PM Finished cleanup of instance 6606330955351669296
  3/16/2017, 11:51:43 PM Started cleanup of firewall 4237851938389441089
  3/16/2017, 11:52:16 PM Finished cleanup of firewall 4237851938389441089
  3/16/2017, 11:52:16 PM Started cleanup of volume 2856654472483387969
  3/16/2017, 11:52:17 PM Finished cleanup of volume 2856654472483387969
  3/16/2017, 11:52:17 PM Finished deleting replica  

• Cutover: This will create a new target VM from  standard persistent disk.  In addition, the source machine will be marked as "cutover" on this date. Note: Any previously launched versions of this machine (including any associated cloud resources that were created by CloudEndure) will be deleted.

• Disconnect machine from Cloudendure: This will stop syncing and delete from Cloudendure

Cloudendure free trial (for other platforms or DR product):

https://appce.cloudendure.com/appce/?mod=signups&act=check.

AWS with Cloudendure: