Article number
Affected Versions
Source Hypervisor
Target Hypervisor

How to confirm VM hardware version compatibility for use with Zerto

Viewed 717 times


An administrator may want to know what VM Hardware versions are supported when replicating to a VMware product.

Note: The following conversions are done to a protected virtual machine when it is recovered in vCenter Server:
• Virtual machines are recovered in vCenter Server with the highest hardware version supported by the vCenter Server host version under which the virtual machine is recovered.
• A Generation 1 (Hyper-V) virtual machine is recovered in vCenter Server with BIOS with the highest supported hardware version.
• A Generation 2 (Hyper-V) virtual machine is recovered in vCenter Server with EUFI. The host in vCenter must support hardware version 8 or higher.


1. Review the following VMware KBs to determine the highest version of the vCenter/ESXi host version
ESXi/ESX hosts and compatible virtual machine hardware versions list (2007240)
Virtual machine hardware versions (1003746)

For example:
ESXi 6.5 supports is Version 13
ESXi 6.7 supports up to Version 14
ESXi 6.7 U2 supports up to Version 15

2. Review our Interoperability Matrix for All Zerto Software Versions (latest) to ensure Zerto supports the VM hardware version listed. Our Interoperability Matrix covering Zerto 6.5 through 7.5 can be found here

3. Depending on what the highest version reported on the VMware KB, upgrade Zerto to the minimum version of the supported VM hardware version.

For example:

ESXi 6.7 U2 supports up to VM Hardware version 15.
Our interoperability guide indicates that it is supported from Zerto 6.5U4P1 and Zerto 7.0U2P2 in their respective version families, therefore if below those versions, upgrade Zerto.

4. If the recovery hosts are at different ESXi versions and you receive an alert from Zerto and/or vCenter, then you can perform one of the following:

a. Upgrade the recovery host to a version that supports the protected virtual machine hardware version.
b. Change the recovery host to one that supports the protected virtual machine hardware version.