Move Data between Cloud using Nutanix Move

By Ashok Vijay & Charul Kapil
| min

We are very happy to announce bi-directional cloud mobility of VMs through Nutanix Move. Available to all Nutanix customers, Move 3.4 will support moving VMs back and forth between Nutanix AHV and AWS. With this capability, you can move your running applications across completely different infrastructure stacks/clouds with very minimal downtime and zero manual efforts.

In a recently concluded study involving over 2650 IT decision makers, 85% of the respondents said hybrid clouds is their most preferred deployment architecture moving forward - combination of workloads running in Private clouds (within their datacenters) and Public cloud services such as AWS. Additionally, 85% of respondents also felt App mobility across clouds is an essential feature for Hybrid clouds. This is exactly what Nutanix Move attempts to do.

Move VMWare VMs to AWS

Nutanix Move (formerly Xtract) was originally built to support migration of workloads to Nutanix AHV from legacy IT infrastructure architecture. Since then the product has evolved to move workloads from AWS to Nutanix AHV, VMWare ESXi running on legacy infrastructure to ESXi on Nutanix as well as Hyper-V on legacy infrastructure to Nutanix AHV. With the 3.4 release of Move, we now support workloads moving from Nutanix AHV to AWS (in tech preview).

Nutanix Move Screen Shot

Move is available for download from the Nutanix support portal. Once deployed, you have the ability to add different providers (sources and targets) by entering information related to vCenter, Hyper-V sources, AWS credentials and regions etc.

Nutanix Move Migration Guide

As an example, from Move UI, an AWS account can be added using access and secret key. When the AWS account is added as a source, Move collects the EC2 instance details for that specific user and region for that user. Similarly if AWS is a target, the VPC information for the account is collected. Move will then scavenge through the deployment and collect information about all the deployed VMs. Based on the source and target combination, Move will automatically determine if specific VMs can be moved.

The VMs to be moved can then be added to a “migration plan”. Migration plan is a logical grouping of VMs that needed to be migrated together. Move takes snapshots of running applications and copies the snapshot over and eventually cutsover in a very time sensitive and efficient manner. The downtime during such moves are typically a few minutes - to copy the last set of changed data, shutdown source VMs and start the VMs on the target. 

Optimise Data Transfer between Clouds

Additionally, Move also optimizes data transfers to reduce the time taken to move VMs across different stacks. In true Nutanix fashion, Move also supports “one-click upgrades”. As we make the product better and add new functionality, you can easily upgrade Move with minimal information loss or downtime. You can always read through the user guide to understand more about how Move works.

The beauty of Nutanix Move lies in its simplicity. The ability to move workloads from/to AWS without any manual steps, without any complicated scripting, with very minimal downtime is where the power of Move stands out. As customers are looking at build hybrid clouds, a super simple product to move workloads across clouds based on business requirements (security, performance, cost, etc.) is a high priority feature. 

We are just beginning our journey to simplify App and Data mobility across clouds. There is a long way to go. But as we embark on this journey, we would love for you to try these capabilities out and provide us feedback so that we can continue making the product better & something you find an integral part of your IT toolkit.

© 2019 Nutanix, Inc. All rights reserved. Nutanix, the Nutanix logo, and all Nutanix product and service names mentioned herein are registered trademarks or trademarks of Nutanix, Inc. in the United States and other countries. All other brand names mentioned herein are for identification purposes only and may be the trademarks of their respective holder(s).