- vCenter Web Client: 6.5 or 6.7 (Use of HTML client is recommended with Chrome v.75 +)
- Clusters have ESXi 6.5U2+ and 6.7
- Single version of ESXi throughout the vCenter cluster
- ESXi in connected state in the vCenter
- ESXi able to communicate with vCenter
- Datastore should be VMFS, NFS, or NFSv3
- E1000E and VMXNet3 network adapters should be available in the on-premises vCenter
- DRS is enabled and HA should be enabled on the vCenter cluster
- Network speed: at least 1 Gbps (10 Gbps link is preferred)
- VM Network has connectivity to the cloud endpoint
- VM Network has access to ESXi
Network connectivity between on-premises and cloud environments
- Network Link: at least 1 Gbps
- Network Round Trip Time Latencies: less than 30 ms
- PrimaryIO Appliance (4 vCPU, 8 GB RAM, 144 GB disk)
- During HDM components deployment, more resources are required. Please check deployment planning section as per your cloud end-point.
- Currently, HDM only supports migration of one cluster per vCenter at a time. If VMs need to be migrated from multiple clusters, the process of deploy, migrate, and undeploy must be repeated for each of the clusters.
- VM Network (Management Network), HDM_Internal_Network (HDM Internal Network), Uplink_WAN_Network (WAN Network) and ESXi_Network (ESXi Network) can map to a single network or multiple networks. In the event that a single network provides all of this functionality, details would still need to be provided for each. In this case, the IP subnet can be divided into multiple ranges that can be mapped to each of the four networks.
Related document: For hardware requirements and system requirements refer to the VMware Hardware Compatibility List (HCL).
- The PrimaryIO Appliance should be deployed on the same vCenter and datacenter it will be managing. It is recommended to deploy on a cluster that will not be migrated.
- HDM components should be deployed on a shared datastore.
- Supported cloud endpoints:
- VMware Cloud on AWS
- IBM Cloud for VMware Solution
- VMware Cloud Foundation SDDC
- VMware Cloud Director (10.1, 10.2)
- Shared Datastore for HDM components.
- Cloud HDM components should have access to the WAN network.
- Cloud VCenter and ESXi should be accessible on-premises at port 443.
- E1000E and VMXNet3 network adapter should be available in the cloud vCenter.
- Network on which HDM components are deployed should have access to the cloud vCenter at port 443 and the cloud ESXi at port 443 and 902.
- Firewall rules for HDM cloud access:
- Port 22 - inbound and outbound
- Port 2379 - outbound
- Port 6000-6010 - inbound and outbound
- Port 7000-7010 - inbound and outbound
- Port 8000-8010 - inbound and outbound
- Post 32820 - inbound and outbound
Network connectivity between on-premises and the cloud
- Network Link >= 1 Gbps
- Network Round Trip Time Latencies: < 30 ms
- For HDM component requirements, check the deployment planning section as per your cloud end-point.
OS Support (TBC/Warm Migration)
Cold migration is semantically equivalent to an OVF export/import and is supported for all operating systems.
For warm migration and TBC
- VMware Hardware version 7 - 14 is supported.
- UEFI Secure boot is not supported for any Operating System.
HDM supports the warm migration of the following versions of Windows with an MBR boot loader. The migration of Windows with a UEFI boot loader is not supported. Use cold migration instead.
|Windows Server 2012 R2 (64 bit)
|Windows Server 2016 (64 bit)
|Windows Server 2019 (64 bit)
- Red Hat Enterprise Linux
- SUSE Linux Enterprise Server
- Ubuntu Server
For details of the versions qualified and the migration modes which are supported please refer
the appendix for the list of all qualified and supported Operating Systems.