Skip to main content

VMware Cloud Director - Migrate from VMware vSphere on OVHcloud

Stephanie R.
Updated

Learn the information you need to migrate to a VMware Cloud Director on OVHcloud environment.

 

Requirements

 

Instructions

This guide is designed to provide you with information about and solutions for migrating your managed VMware vSphere on OVHcloud services to a managed VMware Cloud Director on OVHcloud solution.

It also details the requirements for each use case and, if applicable, explains the requirements for a migration.

This hot migration will minimize disruptions to your public or private networks. Private networks are the most likely to be affected, with downtime of a few minutes.

Your virtual machines will remain operational during the migration with no downtime. However, there is a risk that some network packets will be lost during vMotion.

This migration should be done with no noticeable impact for most applications, but we recommend that you monitor them closely throughout the process.

As a reminder, if you decide to switch to the managed VCD on OVHcloud offer, the new prices will not be applied to your existing servers/hosts. We will cover the increase in licensing prices until the migration is complete.

 

Migration information

Please review the product demo and webinar to familiarize yourself with this new offering.

You can find all the information you need on our VCD pages:

Migrations will be carried out in waves; contact your account manager with any questions about the timing of your migration.

During this process, your data will remain unchanged except for vSAN Storage. Your IP addresses will also remain unchanged.

The migration date will be sent to you by email at least 15 days before the migration starts.

We recommend reading our VMware Cloud Director - The Fundamentals of VCD guide to see which features are included in each migration wave of your environments.

 

Checklist before migration

Click each use case to see the requirements that must be met before migration. If action is required after migration, the steps will also be listed.

Blocking specific use cases: these prevent any possible migration to a managed VCD on OVHcloud environment.

#1: Multi-vDC

  • Goal(s): Migrate VMs and vApps to a single vDC
  • Additional information: This can only be migrated if your architecture has only one vDC (for now).
    If not, please ensure that you transfer all your data (VMs, vApp) into the vDC that will be used for the migration by the OVHcloud teams.
  • Help and references: Migrating an infrastructure to a new vDC
After migration:
  • Goal(s): Re-migrate the VMs and vApp data to your multi-vDc datastore in VCD on OVHcloud if you are in this use case
  • Help and references:

#2: Non-active PCI-DSS and HDS options

  • Goal(s): No solution for now
  • Additional information: Cannot be migrated if, to date, your VMware vSphere on OVHcloud workloads are PCI-DSS or HDS certified.

#3: Encryption VMs (KMS/OKMS or vNKP)

After migration:
  • Goal(s): Reactivate the encryption policy for the VMs in VCD on OVHcloud with your defined solutions (KMS/OKMS/vNKP) after migration and launch the VM encryption.
  • Help and references: It is not currently possible to migrate with VMs or encrypted vApps.
    You will need to import or configure your encryption solution (KMS/OKMS, vNKP) before enabling VM encryption in VCD on OVHcloud

#4: Zerto

Non-blocking specific use cases:

#5: FT (fault tolerance)

  • Goal(s): Disable VM Fault Tolerance in VMware vSphere on OVHcloud
  • Additional information: Right-click your VMs and select Fault Tolerance > Disable Fault Tolerance in managed VMware vSphere on OVHcloud
  • Help and references: VMware fault tolerance
After migration:
  • Goal(s): Fault Tolerance is not available in VCD.

#6: Affinity/anti-affinity rules DRS

  • Goal(s): Reconstruction of affinity/anti-affinity rules in VCD on OVHcloud
  • Additional information: To be retained, DRS affinity/anti-affinity rules will have to be manually recreated by you in VCD on OVHcloud after migration (for now).
  • Help and references: VMware DRS distributed resource scheduler
After migration:

#7: Special devices (CD, DVD, etc...)

  • Goal(s): Unplug all special equipment in VMware vSphere on OVHcloud
  • Additional information: All special devices (CDs, DVDs, etc.) must be removed before migration; otherwise, they will be removed by the migration process (for now).
  • Help and references: Modify virtual machine resources
After migration:

#8: Datastore clusters

  • Goal(s): Delete all clustering rules in VMware vSphere on OVHcloud
  • Additional information: Clustering rules must be removed before migration, as this concept no longer exists with VCD on OVHcloud
  • Help and references: Cluster creation and EVC activation

#9: Over-committed memory

  • Goal(s): Plan or scale your resource requirements in VCD on OVHcloud.
    Or optimize your requirements before migrating (vSphere control panel side)
  • Additional information: Because you cannot over-commit resources within VCD on OVHcloud. This concept does not exist.
  • Help and references: Modify virtual machine resources

#10: Resource pools (share)

  • Goal(s): Replace with vApps in VCD on OVHcloud
  • Additional information: Resource pools will be lost after the migration, as this concept no longer exists on the VCD on OVHcloud side. Instead, we recommend using vApp concepts within the VCD on OVHcloud Control Panel.
  • Help and references: Using vApps in the control panel VCD on OVHcloud

#11: Hosts + Datastore

  • Goal(s): Free up resources (hosts + datastore) in VMware vSphere on OVHcloud
  • Additional information: Any resources not currently billed monthly (e.g., "Freespare" data stores or "Hourly" hosts) need to be switched to a monthly billing cycle.
  • Help and references: Managing resources with Hosted Private Cloud

 

Managed Veeam for VCD (mandatory)

Storage repository configuration

After the migration, you will need to configure your new Veeam Data Platform on managed VCD on OVHcloud storage implementation with the correct settings.

These settings can be customized to suit your chosen service levels:

Repository Target Offers Comments
🥉 Bronze Repository (100 TB) Standard Standard Object Storage
🥈 Silver Repository (100 TB) Advanced Standard Object Storage with off-site backup
🥇 Gold Repository (100 TB) Premium High Performance Object Storage with off-site backup and 14 immutability points

All these repositories have a storage quota of 100 TB. You can contact the support teams to increase this quota.

For more information, please refer to our VMware Cloud Director - Backup with Veeam Data Platform guide.

 

Reset the "Admin" password on Managed VMware Cloud Director

You can now reset the Admin password for a Managed VMware Cloud Director organization using APIv2:

POST /vmwareCloudDirector/organization/[organizationId}/password

 

Go further

For more information and tutorials, please see our other VMware on OVHcloud or Hosted Private Cloud guides. You can also explore the guides for other OVHcloud products and services.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

Related articles