In my last post, I provided a detailed explanation of the migration methods available within VMware HCX. Specifically, I discussed when to utilize No-Downtime, Cold Migration, and/or Bulk Replication and how each method operates. In this final post on HCX migration, I explain and walk through the workflow used to migrate to–and from–the IBM Cloud.
In my last post, I provided a quick component-level overview of VMware Hybrid Cloud Extension (HCX). I also discussed how to deploy each component to securely connect your on-premises vSphere infrastructure to VMware vCenter Server or VMware Cloud Foundation instance within the IBM Cloud. In this post, I explain the three main HCX migration methods that you can use to migrate to–and from–the IBM Cloud.
Part of my role within the Office of the CTO at IBM is to evaluate innovative solutions and lead proof-of-concepts with clients using new technologies. Lately, I’ve been focused on understanding VMware Hybrid Cloud Extension (i.e., HCX). I’ve also been fortunate to deploy pre-release GA versions of this solution (as a proof-of-concepts) for customers that want to migrate their VMware workloads into the IBM Cloud. So, what is Hybrid Cloud Extension and how does one deploy it on-prem and on the IBM Cloud? First, let’s start with a little history of the product.