Operational Defect Database

BugZero found this defect 2156 days ago.

Veeam | kb2678

Error: Backup proxy is missing C++ runtime components

Last update date:

9/11/2023

Affected products:

Veeam Backup & Replication

Affected releases:

11

Fixed releases:

No fixed releases provided.

Description:

Challenge

A backup job, replication job, or restore task for a VMware VM fails with the following error: Error: Backup proxy is missing C++ runtime components, download from http://vee.am/runtime

Cause

This error is displayed when the VDDK libraries on the VMware Backup Proxy fail to be loaded.

Solution

The VDDK libraries may fail to be loaded for the following reasons: Windows-based VMware Backup Proxy Specific The Windows OS may fail to load the VDDK libraries if the Veeam Transport Service is missing components. For example, the C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_7_0\ folder is empty.To resolve the issue, repair the Veeam Backup Transport package: Copy the VeeamTransport.msi installer to the proxy from the Veeam Backup Server. C:\Program Files\Veeam\Backup and Replication\Backup\Packages\VeeamTransport.msi Run the VeeamTransport.msi from an Administrative command prompt Select the Repair option. If the repair fails or the option is not available, instead, manually uninstall the Veeam Backup Transport package and reinstall it using the VeeamTransport.msi. The Windows OS may fail to load the VDDK libraries when security hardening using the registry value CWDIllegalInDllSearch is implemented. For more information, please review this thread on Veeam's RnD Forums. Linux-based VMware Backup Proxy Specific A VMware Backup Proxy running a Linux OS may fail to load the VDDK libraries if the Veeam Transport Service is missing components. For example, the /opt/veeam/transport/vddk_7_0/ folder is empty.To resolve the issue, follow the steps in KB4298: How to Reinstall the Veeam Transport Service on a Linux Server. Customers have reported that some RHEL (8/9) deployments may fail to load the VDDK libraries due to missing the dependency: libcrypt.so.1. For more information, review this thread on Veeam's RnD Forums.   If none of these scenarios applies to your situation, and you are running Veeam Backup & Replication 10 or newer, please collect logs and create a support case.

More Information

Edge Case Example The VM being backed up is located on an ESXi host running a vSphere version that is no longer supported by the installed version of Veeam Backup & Replication. [Veeam Backup & Replication Platform Support]For example, if a VM is located on an ESXi host running 5.1, the Veeam Backup & Replication software will attempt to load the VDDK libraries that used to be stored in C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_5_5\ but are no longer present, as support for vSphere 5.1 was dropped in Veeam Backup & Replication 10. In this specific case example, the Veeam Backup Server had recently been updated to Veeam Backup & Replication 12 from version 9.5 U4, and the entries for the old vCenter and ESXi hosts were still present in the configuration and jobs.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...