This post will demonstrate a live migration of a virtual machine from an on-premise VMware infrastructure, to VMware Cloud on AWS. The steps below will demonstrate how quick and easy it is to move virtual machines between VMware Cloud on AWS and on-premise VMware environments using HCX, without the need to re-IP or re-architect services.
You may also want to review VMware Cloud on AWS Deployment Planning, and VMware Cloud on AWS Live Migration Demo. For more information on Stretched Clusters for VMware Cloud on AWS see Overview and Documentation, as well as the following external links:
The VMware Cloud environment in this demo is setup as follows:
- SDDC deployed consisting of a 6 host stretched cluster in eu-west-2
- On-premise connectivity provided by Direct Connect
- On-premise vCenter and SDDC vCenter in hybrid linked mode
- HCX Cloud add-on enabled, and appliances deployed on-premise
- On-premise networks are VLAN backed port groups in a distributed switch
- VLAN_98 has been stretched for the purposes of this demo
The virtual machine I am going to migrate is the web server from a 3-tier application: VMC-DEMO-WEB-01, with a private IPv4 address of 192.168.98.15.
In the on-premise vCenter Server I have selected the HCX plugin from the Menu drop-down. The dashboard shows my site pairing and cloud overview. Under Network Extension I can see that VLAN_98 has been stretched to VMware Cloud on AWS.
From the Migration screen I can see previous migration history, and I select Migrate Virtual Machines.
The migration interface loads and I search for the virtual machine.
Having selected the virtual machine to migrate I can now go ahead and select the folder, resource pool, and datastore to use. In this example the machine is already thin provisioned and I am using the vMotion migration type. The network has automatically been populated with the stretched network VLAN_98.
HCX will perform some validation checks and then I click Finish to start the migration.
The virtual machine migration progress is now underway.
After 4 minutes, the migration is complete.
The virtual machine did not drop any pings during the migration, the web site is still accessible and able to pull data from the database.
A HTTP monitor setup in Solarwinds shows that there was no loss of service during the migration.
The virtual machine is now running in VMware Cloud on AWS and is visible in the SDDC vCenter.
Should the machine need moving back on-premise the same process can be followed, with the Reverse Migration tick-box.
Once virtual machines are running in VMware Cloud on AWS they have access to native AWS services using the 25 Gbps Elastic Network Interface (ENI): Connecting VMware Cloud on AWS to Amazon EC2, Load Balancing VMware Cloud on AWS with Amazon ELB.