Knowledge Base: Virtual Servers & Datacenter

Back to listing

Nov 23


Copaco Cloud is hosting Hyper-v and VMware based virtual machine infrastructures. This manual will show the steps you need to take in order to convert your existing Copaco Hyper-V (or Azure Pack) environment to a VMware based infrastructure.

In this active we will go over the order and configuration of your VMware virtual Infrastructure and the migration scenarios to it from the Copaco Hyper-V Cloud products for existing virtual machines.

  • Prepare a list of the currently allocated resource amounts (CPU/Memory/Disk space/IP addresses).
  • If your Hyper-v subscription was purchased on a reseller account in the past, please continue with creation of a customer account for own use.

  1. Login to the Customer Account

    We start with logging in to the customer account that is going to own the VMware Subscription.

  2. Subscription and resources order

    Now you need to place an under for Copaco VMware Cloud service and the needed resources.

    A detailed order guide is available on

    During order placement you are asked to make a decision in which data center your virtual infrastructure must be located. All data center sites are built on top of similar hardware and have the same price. You can pick whatever location you prefer or can purposely spread your customers over different locations to spread the risk in case of a data center failure. One customer can also own subscriptions for multiple separate sites.

    We also offer a multi-site service on which we synchronously replicate your VM storage and have your resource reserved in two data centers. In case of a data center failure, your virtual machines will immediately start rebooting in a separate data center location which allows for quick recovery in a data center outage or SAN failure. Please note you will need to make the decision now and cannot easily migrate your environment to a different data center site afterwards.

    The amount of CPU, Memory and Disk space resources is calculated differently on VMware than it was on Hyper-V. Please take these changes in consideration when placing your order based on resource allocation of existing VM's.

    CPU resources are allocated based on GHz within VMware and one virtual core consumes 2GHz, while in Hyper-V CPU is allocated as virtual cores without guarantee on the amount of GHz this core will deliver.

    Memory resource are dedicated to a virtual machine, but VMware will create a swap-file on disk for the amount of memory that is allocated to a powered on virtual machine. A virtual machine in powered on state with a 100GB hard disk and 32GB of memory will consume at least 132GB of disk space.

    Hard disk resources on the virtualization host count towards your disk space quota and must be purchased before you can use it. This included VM Configuration files, Virtual Hard disk files, Memory Swap files, Snapshot files, Templates files, and ISO images.

    Network bandwidth is consumed in a simular way on Hyper-V and VMware with unlimited in-and out traffic. The main difference is that Hyper-V used a shared edge network for all customers while VMware uses a dedicated network edge per virtual data center(Subscription). This guarantees much higher network throughput as long as your virtual machine (CPU) can process it.

  3. Network Edge Setup

    Once the virtual data center is created you will need to login to the customer panel again and open the vCloud Director service page. Within this page you must setup your virtual network configuration and define your network information. Please note this is a required step before continuing within the VMware infrastructure and these network setting cannot be changes afterwards without fully redeploying your infrastructure.

    If you want to keep the same internal IP addresses on your VM's as you did within the Hyper-V environment we recommend you to configure the same network subnet. Please note that you have no control over the public subset or IP addresses that will be allocated to your environment. These cannot be transferred over from your Hyper-V infrastructure!

    A detailed guide is available on

  4. Network Edge configuration

    VMware offers advanced configurations of firewall and network translations(NAT) to expose your virtual machines to the internet. We recommend you to familiarize yourself with the network setup and prefigure your existing Hyper-V NAT rules in the VMware Edge firewall and NAT translation tables.

    Please note that while Hyper-V only offered NAT rule configuration, VMware offers Firewall and NAT configuration. By default all ports and translations are disabled/denied.

    A detailed guide on firewall configuration is available on

    A detailed guide on NAT Translation is available on

    Once your network Edge is deployed you will known the Public IP allocated to your personal Edge gateway. You can use this to prepare DNS and configuration changes that must be applied after VM migration to make them accessible again from the internet.

    In case you purchased more than one public IP address you can allocate your additional IP addresses by opening the vCloud Director service page within the customer control panel and opening the VDC Network configuration page again. (Just like you did in step 3 of this KB but you will be redirected to a new page for IP allocation)

    In case your customer uses site-to-site (IPSEC) VPN connections on Hyper-v you must establish a new VPN connection with the VMware Edge gateway. More detailed setup instruction for IPSEC VPN connections in VMware can be found in guide:

  5. Contact 2tCloud Support

    Now all the prerequisites have been completed we must prepare for migration. The 2tCloud Support team offers migration support free of charge to do the Hyper-V VM export, conversion and import to the new vCloud Director data center. Please create a support ticket asking for Hyper-V to VMware migration assistance.

    Our support team prepared a customized VMware Integration tool driver installation package that allows deployment on Hyper-V VM's. Please request the integration drivers when you open a migration support case.

    You need to prepare your Hyper-V VM's for migration. To make sure you VM can boot, connect to the network and is accessible by Console, you will need to install VMware integration drivers while your VM is still running on Hyper-V.

  6. Plan for Migration

    Now schedule a time frame for the migration with our support team and the customer. Your VM's will be shutdown on hyper-V, Exported to a convertor server, Converted to VMware format and than imported to the VMware virtual data center of your new subscription.

    Expected downtime for the conversion is about 1 hour for every 100GB of storage assigned to your virtual machine hard disks.

  7. Finalize VMware setup after migration

    Once your VM's are available within the VMware virtual data center you will need to link the network adapters to your prepared edge gateway and set the preferred IP address configuration. The technical migration is completed at this point.

    Please don't forget that DNS records that point to your server now need to be updated with the new external IP address of your edge gateway.

Request a callback
Send Request