When Xtract for VMs launched just seven months ago, it provided Nutanix customers with a simple and granular method to onboard existing workloads to on-premises Nutanix Enterprise Clouds. The ease and speed in which migrations are completed reduces the time taken to onboard workloads, providing customers with a short time-to-value. This has resulted in great customer adoption with Xtract being used by hundreds of organizations to migrate in excess of 12,000 VMs, based on a variety of Microsoft Windows and Linux operating systems.
Today we proudly announce the next phase of Xtract’s application mobility story, enabling VM migrations from public cloud, available in a future release.
Introducing AWS cloud migrations
With the next release of Xtract, Nutanix adds Amazon Web Services (AWS) as a source for VM migrations from the public cloud to an on-premises Nutanix Enterprise Cloud.
Why introduce AWS VM migrations
To build or rent is a question all organizations ask themselves, and even when it appears easier and cheaper to rent infrastructure, a public cloud first strategy can prove both time consuming and costly when business priorities change and there is need to migrate VMs elsewhere, to another public cloud or on-premises infrastructure.
Examples of organizations that chose to migrate from public cloud deployments are not difficult to come by, and include names such as Facebook and Dropbox, however similar migration challenges exist regardless of organizational size. Recent high profile public cloud outages and latency issues only add to organizational fears over security and compliance.
Nutanix believes organizations should have freedom to manage hybrid cloud complexity with ease, without lock-in or spiraling costs.
How to manage AWS VM migrations: a guide
Xtract for VMs has been designed to simply add the AWS VM migration feature as a new source for VM migrations, adding to VMware ESXi used for on-premises migrations to AHV. Architecting Xtract in this manner means that the migration processes remains the same as it did before.
Adding an AWS connection source is very simple, requiring only an appropriate friendly name, your AWS access key ID, and AWS secret access key.
Once connected to your AWS account, the number of available regions and VMs contained in those regions is visible.
The process for creating a migration plan from AWS is now the same, requiring the same few steps as for other on-premises migration plans, including VM(s) selection.
The network mapping from the source to target occurs in the same manner as for on-premises migrations, and then within a few clicks, the migration plan is complete and can be executed.
Once a migration plan is executed, the initial data-seeding starts, taking as long as necessary depending on the volume of data and connection speeds. This process doesn’t impact the source VM which remains up and running.
Once all migrated VMs have been synchronized, they remain in-sync with periodic delta updates until such time you choose to cutover to the new target VM. Control of the cutover process is a key feature of Xtract enabling businesses to choose when is most appropriate to cutover, and helping to minimize any VM outage.
Nutanix testing has shown t2.micro instances to take as little as twenty minutes to complete, with the cutover being as short as one minute.
Can I migrate all workloads?
One of the more difficult aspects of public cloud migrations are the dependencies formed to cloud-native services. As such, for this initial release, standalone EC2 instances with attached EBS volumes are supported.
When can I start migrating AWS VMs to Nutanix Enterprise Cloud?
Nutanix is announcing this new public cloud VM migration feature just as the Xtract product team is preparing for an early access release, and we are looking for a small number of customers willing to participate in it. If you have an AWS public cloud presence and are willing to participate in an initial 30-60 minute exploratory call to discuss your requirements, please email email@example.com.
Disclaimer: This blog may contain links to external websites that are not part of Nutanix.com. Nutanix does not control these sites and disclaims all responsibility for the content or accuracy of any external site. Our decision to link to an external site should not be considered an endorsement of any content on such site.
Forward-Looking Disclaimer: This blog includes forward-looking statements, including but not limited to statements concerning our plans and expectations relating to product features and technology that are under development or in process and capabilities of such product features and technology and our plans to introduce product features in future releases. These forward-looking statements are not historical facts, and instead are based on our current expectations, estimates, opinions and beliefs. The accuracy of such forward-looking statements depends upon future events, and involves risks, uncertainties and other factors beyond our control that may cause these statements to be inaccurate and cause our actual results, performance or achievements to differ materially and adversely from those anticipated or implied by such statements, including, among others: failure to develop, or unexpected difficulties or delays in developing, new product features or technology on a timely or cost-effective basis; delays in or lack of customer or market acceptance of our new product features or technology; and other risks detailed in our Form 10-Q for the fiscal quarter ended January 31, 2018, filed with the Securities and Exchange Commission. These forward-looking statements speak only as of the date of this presentation and, except as required by law, we assume no obligation to update forward-looking statements to reflect actual results or subsequent events or circumstances.
© 2018 Nutanix, Inc. All rights reserved. Nutanix and the Nutanix logo 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).