Would You Rather: Migrate to the Cloud in 6 minutes or 60 hours?

October 17, 2016

Michele Borovac

It’s my kids’ favorite car game. Would you rather be invisible, or be able to fly? Would you rather eat a snail or a give up Minecraft for a week? You get the idea.

Anyway, with the news last week about VMware Cloud on AWS, some of our engineers did some testing in the context of how Velostrata cloud migration software would fare against vMotion for moving a workload from a data center to an instance in AWS. The results were striking (and, frankly, they make for a pretty unfair game of ‘Would You Rather’).

If you’re not familiar with Velostrata, our software platform makes it possible for enterprises to build a dynamic, multi-vendor hybrid cloud so IT managers can move workloads from on-premises data centers to and from public cloud in minutes. With Velostrata, organizations can take advantage of public cloud as a true extension of their datacenter: applications include capacity on demand, accelerated dev/test and full migration.

Here’s our test scenario:

We began with a multi-tier SugarCRM application consisting of 2 VMs (one for the database and one for the application server). Together, the total virtual disk size was 1.1TB. The application was running in a Miami, FL co-lo facility, and our target destination was AWS North Virginia. We had a 40Mbps link between the locations, with 30ms roundtrip latency.

Using Velostrata’s plug-in to VMware vCenter, we initiated the migration with a simple right mouse click to select ‘Run in Cloud.’ 6 minutes later, both VMs were running, and the application was live in the cloud (!). During the process, a maximum of 8Mbps was consumed, with the average being 2Mbps. This highly efficient bandwidth utilization is due to Velostrata WAN optimizations, which include cross-VM de-duplication, and multi-tier caching.

By comparison, given what we know about using vMotion to accomplish the same objective, the two VMs will only be live in the cloud when all the disks have been moved. Using the same configuration allocated above (assuming it was dedicated and fully utilized for this migration), this would take over 60 hours!

I know which choice I’d rather…