Skip to main content
  • EN

Hi all,

We are currently facing an issue during the installation of CDP (Continuous Data Protection) in our vSphere 8.0.3 environment.

 Setup:

  • Hosts are updated exclusively using offline ISO images

  • ISO files are internally validated and approved via change control

  • Online depots are completely disabled

  • vLCM is configured with only our custom HPE ISO (VMware-ESXi-8.0.3-24674464-HPE-803.0.0.12.1.0.11-apr2025.iso)

  • vCenter version: 8.0.3

  • Hosts affected: esxi03.cloud.local (and others)

Problem:

When attempting to install CDP, remediation fails with the following error:

 

Host 'esxi03.cloud.local' was not processed, the reason: 'Failed to validate the checksum of VIB 'http://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qfle3/QLC_bootbank_qfle3_1.4.51.0-1OEM.700.1.0.15843807.vib', because the computed checksum differs from the expected one stored in metadata. Make sure the specified VIB is NOT corrupted and the expected checksum stored in metadata is correct.'

 Notes:

  • We are not using the online depot, but the error still refers to http://hostupdate.vmware.com/..., which is unexpected.

  • The affected VIB (qfle3) is already included in our ISO image, so we suspect it shouldn't be pulled or validated from any external source.

  • The same ISO was used on all hosts, but this issue seems isolated to certain nodes.

Questions:

  1. Why is vLCM or the CDP install referencing a VIB URL from the online depot when the depot is explicitly disabled?

  2. Is there a way to force VIB validation against the imported ISO only, and prevent any remote lookups?

  3. Could this be a CDP plugin or integration issue pulling outdated or cached metadata?

Any insights, experiences, or suggestions would be greatly appreciated!

Thanks,

This will be nothing anyone here can answer.  You will need to create a Support ticket with Veeam as I have never seen this one before.  You might even want to create a VMware ticket as well to coorindate the two.  Sorry wish I could give a better answer but this one will be way above everyone other than maybe some Veeam folks that are going to say the same thing.

Yep, agree with Chris on this. You're asking about how CDP works under the hood & only a Veeam Dev & Product Manager will be able to answer. You could post on the Forums but they'll want a Support Case #. So I'd just work with Veeam. 

Hi everyone,

Just to update you — the issue has been resolved with VMware support.
Our old VEEAM server had crashed, and we created a new VM using the same name, which caused confusion for vCenter.
VMware assisted us in cleaning up the cluster and everything is now back in order.

 

Great to hear. Thanks for the update and the solution ​@VEEAM_Legend 👍🏻

CDP deployment is always tricky. I haven't seen this exact error before, but in my experience most deployment issues were resolved by rebooting the ESXi host or restarting vCenter services (assume that metadata and checksum is good). DNS also common root cause in many CDP cases! 

You can also compare the qfle3 VIB file on a working ESXi host to verify the checksum. If there's a mismatch you can copy the VIB from the working host and install it manually on the affect

CDP deployment is always tricky. I haven't seen this exact error before, but in my experience most deployment issues were resolved by rebooting the ESXi host or restarting vCenter services (assume that metadata and checksum is good). DNS also common root cause in many CDP cases! 

You can also compare the qfle3 VIB file on a working ESXi host to verify the checksum. If there's a mismatch you can copy the VIB from the working host and install it manually on the affect

We have stopped using the online image. Everything now works through change control within the company, so only approved ISOs will be used for patching the ESXi hosts.

This behavior started occurring—I initially thought the VIB would be pushed from Veeam, but somehow it still attempts to connect online when I enable it. This seems to be just the default behavior.

​@VEEAM_Legend  VIB file are pushed to ESXi hosts from the VBR Server and it’s doesn't required internet connectivity 

Alternatively you can manually grab the VIB files from the VBR server and install it manually in ESXi hosts. You can find the VIB offline files here “C:\Program Files\Veeam\Backup and Replication\Backup\Packages” and copy the appropriate version and install in each host 

 

 

Great to hear you resolved it ​@VEEAM_Legend 

I have run through that cleanup process myself and it is a pain at times.  😂 

Great to hear you resolved it ​@VEEAM_Legend 

I have run through that cleanup process myself and it is a pain at times.  😂 

the vMware engineer didnt want to share the script with me, was a magicall one. 

Great to hear you resolved it ​@VEEAM_Legend 

I have run through that cleanup process myself and it is a pain at times.  😂 

the vMware engineer didnt want to share the script with me, was a magicall one. 

Magical ✨ 😂 

Terms & ConditionsAccessibility statement