Leverage vCenter Converter to migrate to VMware Cloud on AWS

Nico Vibert cross-post series part 3 | Find out how to leverage vCenter converter with VMware Cloud on AWS and learn how to migrate VMs and workloads running on top of different hypervisors.

Original was posted here.

This blog post will walk through leveraging vCenter converter with VMware Cloud on AWS.

I’ve had multiple customers asking questions such as:

  • How do I migrate my virtual machines to VMware Cloud on AWS when I don’t have access to vCenter? There are cases where customers have outsourced their infrastructure to a 3rd party and don’t have access to the VMware infrastructure ; only to the actual Virtual Machines. Migration tools like HCX require access to vCenter and therefore would not work in this scenario.
  • What do I do with my physical machines when I want to evacuate my DC and move all my stuff to VMC on AWS? There are 3rd parties like Platespin that also provide this capability but they are not free.
  • How do I convert and migrate workloads running on top of different hypervisorsto VMware Cloud on AWS?

Well – an answer (and there are others) is to use vCenter Converter.

For the non-initiated, vCenter Converter has been around for a long time to do P2V (Physical-To-Virtual) migration and V2V (Virtual-to-Virtual) but this is still a perfectly valid option for a migration to VMware Cloud on AWS.

This detailed blog post is a great walk-through on how to set up vCenter Converter.

Installation and Conversion Walkthrough

First, go and download vCenter Converter. I downloaded the vCenter Converter Standalone version from my.vmware.com. It has to be installed on Windows.

You can run it on the actual machine you’re migrating or from a jumpbox.

It can convert physical machines or virtual machines, Windows or Linux, etc…

Once installed, it’s fairly straight-forward but there are some gotchas to be aware of when you want to migrate to VMware Cloud on AWS. First, go ahead and click “Convert machine”.

vCenter Converter Standalone - 1
It’s like going back in time!

You can convert a powered-on or powered-off machine. It can be physical or virtual and it can be local or remote.

vCenter Converter Standalone - 2
Powered-on VM options

You can also attach directly to a vCenter or Hyper-V server:

vCenter Converter Standalone - 3
Powered-off VM options

I just wanted to validate the process so I converted the local machine I had installed vCenter Converter on.

vCenter Converter Standalone - 4

The destination is the Cloud vCenter. This page lists the required ports so you need to make sure you allow ports 443 and 902 (TCP) on the Management Gateway on VMware Cloud on AWS. You can specify the source IP in the security rules on the VMware Cloud on AWS MGW to be the public IP of the VM you’re migrating to the Cloud to narrow down access to your VMC environment.

vCenter Converter Standalone - 5

Select the Folder and the name of the converted VM (“Converted-VM”… I win the prize for originality on this one).

vCenter Converter Standalone - 6

Make sure you select the “WorkloadDatastore” and not the “vSANDatastore”. Note I select the Virtual machine version 14. Make sure you also select the “Compute-ResourcePool”.

vCenter Converter Standalone - 7

Make sure you select the correct “Network” because by default, vCenter Converter picked up an internal network that VMs cannot connect to.

vCenter Converter Standalone - 8

I will connect it to “sddc-cgw-network-1”.

vCenter Converter Standalone - 8

Verify you’re happy with the settings and press Finish.

vCenter Converter Standalone - 9

Watch the conversion and migration. It just took minutes to migrate the VM across.

Let’s look at the end-result: we now have a VM connected to the network I specified, with the boring name I picked (“Converted-VM”) and on hardware version 14.

And that’s one more workload migrated to the Cloud!

Even better, all the data was encrypted in transit via SSL Encryption!

Thanks for reading.

About the Authors

Nicolas Vibert

Lead Solution Engineer - VMware Cloud at VMware

I am Nico Vibert and currently work for VMware as a Lead Solution Engineer for the VMware Cloud on AWS service. Most of my career has been spent in the networking world, from a junior support engineer working for a Cisco partner to a senior network architect working for Cisco itself. I finally joined VMware late in 2015 and worked on the network virtualization software NSX until I transitioned to the VMware Cloud on AWS team. If you’re really that curious, you can find out more on my LinkedIn profile. I have a strong technical background which I have validated with 17 certifications over my career, across multiple vendors (Cisco, VMware, AWS, etc.). I hold the Cisco CCIE certification, recognised as one of the toughest certifications in the IT Industry (I recently published some thoughts on my 10-year anniversary as a CCIE). To complement my technical certifications and expertise, I built solid enterprise architecture skills (based on TOGAF) and have written business cases and devised complex financial ROI models. I am a polished presenter and can articulate complex solutions from CxO-level to entry-level engineer. I regularly speak at events, whether on a large scale such as VMworld, Cisco Live or at smaller forums such as VMUGs or local events. Finally, I’m passionate about knowledge sharing and mentoring: I regularly train new hires and take the time to mentor individuals across VMware.

Leave a Reply

Your email address will not be published. Required fields are marked *