Skip to main content
  • EN

Hi Guys,

 

There a workaround this error, I am running a replication from version 8.0 host to version 7.0.3 host?

 

Client source HOST is on: 

On VM:ESXi 8.0 and later (Version 20)

On Host:ESXi 8.0 and later (Version 20)

 

Destination HOST is on:

 

Hypervisor:VMware ESXi, 7.0.3, 19898904

 

09:55:59    Queued for processing at 2025/07/14 09:55:59     
09:55:59    Required backup infrastructure resources have been assigned     29:46
10:25:46    No available proxies are running on ESXi management interface subnet. Using proxies from a different subnet, performance may be impacted     
10:25:48    VM processing started at 2025/07/14 10:25:48     
10:25:48    VM size: 300 GB     
10:25:51    Discovering replica VM     00:00
10:25:53    Resetting CBT per job settings for active fulls     00:15
10:26:08    Getting VM info from vSphere     00:09
10:26:17    Creating VM snapshot     00:08
10:26:31    Processing configuration Error: VM hardware version 20 is not supported by destination host (version 7.0.3.0)     00:05
10:26:36    Removing VM snapshot     00:10
10:26:51    Error: VM hardware version 20 is not supported by destination host (version 7.0.3.0)     
10:26:51    Processing finished with errors at 2025/07/14 10:26:51     
 

The error message says it all: VM hardware version 20 is not supported on an ESXi host running v7, as this hardware version was introduced with vSphere 8 (and ESXi 😎.

Source: https://knowledge.broadcom.com/external/article/315655/virtual-machine-hardware-versions.html

Hi,

 

A VM Hardware Version is tied to the minimum supported ESXi/Workstation version required to run the VM, this permits functionalities only available within newer ESXi/Workstation builds. You should look to downgrading your VM Hardware Version on your VM to a 7.0.3 compatible version if you plan to replicate this VM.

Hi ​@Cajon 

You can shut down the VM with the new virtual hardware and disconnect the disks.
Create a new VM with VHardware supported by 7. 
Version: 7.0.3 (Build 19898904)
Supported Virtual Hardware Version: oSpecify the version: “Version 19”]
Reschedule the replication.

 

As mentioned above, it’s related to your destinations Hypervisor Version...

Why not planning to upgrade this Host/Destination to a new *and also* supported Version? If it’s only a replication target, this shouldn’t be a problem, because no other workloads are running on it. If it’s a Cluster, then you can easily migrate your running workloads to other Hosts in this cluster…

Hope it’s not a problem regards to licensing with Broadcom :-)

A general thing to remember: your Replication Site has to be in every infrastructure at the same level then your source - or even newer. Keep this in mind, also when it comes to updates/upgrades  - first take a look at your DR/Target/Replica site, then your source...

​@Dynamic yes this have to do with Broadcom licencing, the replication site currently has Version 7 and other clients are still running on Version 7 on the Replication site.

Only this new client is running a mix mode of V6 and V8 and the target VM is sitting on V8 and their other hosts doesn't have enough resource to migrate the VM to older version.

​@Link State ​@MattM ​@MicoolPaul Thank you guys i will try to recreate the VM again with V7 compatibility.

Comment


Terms & Conditions