Tuesday, March 21, 2023
HomeCloud ComputingMigrating Legacy and Non-vSphere Workloads to VMware Cloud Director

Migrating Legacy and Non-vSphere Workloads to VMware Cloud Director

Many organizations nonetheless run a minimum of a bit of their infrastructure on outdated bodily servers or legacy/non-VMware virtualization of their information facilities. The upkeep and day-to-day operations turn into a extra vital problem on daily basis due to the outdated {hardware} and hypervisors being out of help.

Due to that, these organizations search for potential options to cope with it by investing minimal money and time. One of many many choices is emigrate these workloads to a contemporary and up-to-date virtualization platform.

It makes such migrations a necessary a part of the Cloud Suppliers’ choices to allow them to be aggressive and ship a priceless service to their tenants.

VMware Cloud Director Availability already presents a migration possibility for legacy vSphere workloads working on vSphere 5.5U3, 6.0U2, and 6.0U3. [Read more]

A number of different instruments present migration capabilities from legacy or non-vSphere sources, however they’re normally costly or have fairly a couple of limitations in terms of VMware Cloud Director clouds being the vacation spot. 

ObserveVCPP companions are charged 0 factors per migrated workload utilizing VMware Cloud Director Availability.

VMware Merchandise in Scope

Product Objective
vCenter Converter Standalone Convert and migrate the VMs from the supply non-vSphere or Legacy vSphere to an intermediate vSphere
vSphere Intermediate for the migration course of. Vacation spot for the vCenter Converter Standalone conversions and a supply for the VMware Cloud Director Availability migrations to VMware Cloud Director
VMware Cloud Director Availability Migrations from the intermediate vSphere to the vacation spot VMware Cloud Director cloud underneath the specified group
VMware Cloud Director The vacation spot cloud

Please be aware that the next merchandise must run interoperable variations:

  • vCenter Converter Standalone with Intermediate website vSphere
  • VMware Cloud Director Availability with Intermediate website vSphere and Vacation spot website VMware Cloud Director

To grasp extra concerning the supported variations, please seek advice from the VMware Interoperability Matrix.


There are a number of prospects when providing a workload migration service from non-vSphere or legacy vSphere sources:

  • As a self-service totally operated by the tenant
  • As a completely managed service by the supplier
  • As a combined service – a part of the operations are dealt with by the tenant and the remaining by the Cloud Supplier


With Converter Standalone, you possibly can convert bodily machines, legacy VMware, and Hyper-V digital machines. Since there are a number of specifics about every machine sort, yow will discover extra details about every of the supported sources right here.

You’ll be able to set up Converter Standalone parts solely on Home windows working programs. Converter Standalone helps Home windows and Linux working programs as sources for powered-on-machine conversions and virtual-machine conversions. You can not reconfigure Linux distributions.

You’ll find extra concerning the supported Working Programs right here.

For any conversion limitations, please verify right here.


To use any Visitor Customization properties on the migrated VM on the vacation spot website, VMware instruments should be put in earlier than the migration to the tenant group is initiated. It may be performed previous to beginning the method whereas the VM is working on the supply or after it’s transformed on the intermediate website. 


Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Flow

The steps are as follows:

  1. Put together the vacation spot cloud if it doesn’t have VMware Cloud Director Availability working.
  2. Deploy and configure the intermediate website.
  3. Deploy vCenter Converter Standalone and its parts accordingly on the supply website.
  4. Convert a VM/bodily machine to the intermediate website. 
  5. Confirm all of the properties (GuestOS sort, model, SCSI controller, and so forth.) are accurately populated via the vSphere UI. 
  6. (Elective) Energy on the VM if wanted.
  7. Configure the migration utilizing VMware Cloud Director Availability. 
  8. (Elective) If the VM is powered off, carry out a handbook sync.
  9. (Elective) Configure the Restoration settings – Community configuration (Re-IP), Visitor Customization. 
  10. Provoke the migration.

The non-optional steps are marked with their numbers on the diagram.

Vacation spot Website

For the reason that supposed vacation spot for the transformed workloads is VMware Cloud Director, the presumption is that the VMware Cloud Director cloud (together with its group construction) is already in place. If, for some purpose, it isn’t, please comply with the VMware Cloud Director documentation to set it up correctly.

The primary necessary requirement is to have all of the VMware Cloud Director Availability home equipment deployed and configured on the VMware Cloud Director cloud.

You’ll be able to seek advice from the VMware Cloud Director Availability Reference Structure and documentation for particular solutions and directions on do it.

The cloud website is prepared for migrations when VMware Cloud Director Availability is prepared, and its Service Endpoint tackle is accessible.

Intermediate Website

The intermediate website will be deployed and managed by the Cloud Supplier or by the tenants of their information middle. Which possibility is extra appropriate should be decided based mostly on a number of elements equivalent to value, obtainable {hardware}, workload criticality, and so forth.The positioning should run vSphere 6.7U3 (already previous Finish of Basic Assist), 7.0, 7.0U1, 7.0U2, or 7.0U3. There should be a minimum of one current person with the next permissions required by vCenter Converter Standalone.

One of many following vSphere licenses must be utilized:

  • vSphere Analysis license (if the migration is completed inside 60 days of provisioning the vSphere intermediate website)
  • vSphere Necessities Plus
  • vSphere Customary
  • vSphere Enterprise
  • vSphere Enterprise Plus
  • vSphere Desktop

The vCenter tackle should be accessible from the vCenter Converter Standalone machine.

There are two potential choices for the deployment of the Intermediate vSphere surroundings:

  • A devoted vSphere per tenant with a VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment paired to the tenant Group within the VMware Cloud Director cloud. It may also be a vSphere surroundings working on the tenant’s infrastructure and managed by them.
Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Self-service
  • A shared vSphere with a VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment per tenant paired to the tenant Group within the VMware Cloud Director cloud.
Migrating Legacy and non-vSphere Workloads to VMware Cloud Director - Managed service

Possibility #1 is appropriate when the Cloud Supplier presents the migration as a self-service or a combined service. Then the tenants can management the entire course of or simply a part of it. For instance, the deployment and operation of the vCenter Converter Standalone. Choices #2 is appropriate when the Cloud Supplier presents a managed service as a result of limiting the visibility of tenants solely to their assets in a shared vSphere surroundings may be difficult.

TipTo optimize the fee gathered to the Cloud Supplier by working the Intermediate website, the transformed VMs can stay powered off and immediately be migrated to the cloud(Chilly Migration). It should require a handbook sync after the migration is configured however will enable even a deployment with much less compute assets for the Intermediate vSphere surroundings. It will possibly additionally make the most of a slower however cheaper storage answer (NFS, for instance). Nonetheless, these deployment selections must be made solely after contemplating the variety of workloads that shall be migrated. Additionally, this strategy may result in a increased downtime interval for the transformed workload.

Deployment steps

These steps should be adopted to get the intermediate website able to accommodate the transformed VMs.

  1. Deploy and put together the vSphere infrastructure in keeping with the chosen design (configure networking, storage, and so forth.). VMware Cloud Basis can be utilized for automating the deployment course of. 
  2. Deploy the VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment following the steps supplied within the documentation
  3.  Run the preliminary setup wizard of the newly deployed equipment to pair it with the vacation spot cloud. Use the VMware Cloud Director Availability Service Endpoint tackle and Group administrator credentials (relying on the design, the credentials must be for a tenant or system Group).
  4. Create a person for vCenter Converter Standalone with a minimum of these permissions.
  5. Carry out all of the community configurations essential to make the vCenter accessible from the tenant website. 

TipThroughout the preliminary setup wizard, think about enabling the Enable entry from Cloud setting, which can allow you to configure the migration from the cloud website. 

Supply Website

Due to the assorted sources supported by vCenter Converter Standalone (see Limitations for extra info) and every has totally different necessities, there isn’t a really helpful structure for the supply website. 

Probably the most appropriate conversion strategy must be decided by the machine (digital or bodily) proprietor in keeping with its compliance with the vCenter Converter Standalone necessities and limitations.

For instance, it’s potential to transform a Hyper-V VM utilizing two strategies:

  • Powered-off digital machine conversion
  • Powered-on machine conversion

A choice should be made based mostly on the Visitor OS distribution, its compatibility with vCenter Converter Standalone, and another elements, equivalent to downtime, the necessity to modify the community configuration, and so forth.

In case any configuration modifications to the Visitor OS are required in the course of the migration (equivalent to community reconfiguration, pc title change, and so forth.), then VMware instruments shall be necessary to be put in. Please seek advice from the Concerns part for extra info on what is required.


A number of steps will be automated to cut back the quantity of handbook work.

  1. Transport the binaries and silent set up of VMware instruments. (Hyperlink for Home windows & Hyperlink for Linux)
  2. Intermediate website deployment via VMware Cloud Basis. (Hyperlink)
  3. OVF Device to deploy the VMware Cloud Director Availability On-Premises to Cloud Director Replication equipment on the Intermediate website. (Hyperlink)
  4. Set up vCenter Converter Standalone via command-line. (Hyperlink)


You’ll find an in depth instance of the method in our Migrating Legacy and non-vSphere Workloads to VMware Cloud Director doc.


Although the circulation requires a number of handbook steps, most are trivial and require no particular information. Following the documentation is adequate for the profitable completion of the duties. Nonetheless, a few of them will be automated to cut back the quantity of handbook work.

The mix of vCenter Converter Standalone and VMware Cloud Director Availability is a sensible and environment friendly answer for migrating workloads from legacy or non-vSphere environments to VMware Cloud Director clouds with minimal effort. It will possibly take only a few hours to efficiently migrate and power-on a workload within the VMware Cloud Director cloud.

The fee-effectiveness of this answer can also be a indisputable fact that must be thought of (0 factors per migration).

Bear in mind, to get the newest updates, verify this weblog recurrently, you can also discover us on SlackFbTwitterLinkedIn in addition to many demo movies and enablement YouTube, particularly our Characteristic Fridays collection!



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments