- Veeam Support Knowledge Base
- Error: Backup proxy is missing C++ runtime components
Error: Backup proxy is missing C++ runtime components
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
The error message states that the C++ runtime components are missing, which may be inaccurate. The actual cause of the error is that the VDDK libraries cannot be loaded, which in older versions of Veeam Backup & Replication (9.5 and older) was caused by missing C++ runtimes.
This article has been updated to account for other (non-C++ runtime-related) reasons why the VDDK libraries may fail to be loaded in Veeam Backup & Replication 10 and newer.
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 VMware Virtual Disk Development Kit (VDDK) libraries on the VMware Backup Proxy fail to be loaded.
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 they are missing components.
For example, the C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_7_0\ folder is empty. - 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. - Customers have reported that some RHEL (8, 9, and 10) deployments may fail to load the VDDK libraries due to a missing dependency:
libcrypt.so.1. For more information, review this thread on Veeam's RnD Forums.
Solution
This article is written for Veeam Backup & Replication 12.1.2 and higher.
Starting with Veeam Backup & Replication (VBR) v12.1.2, the VDDK libraries are separated from the Veeam Transport package. This change ensures that the VDDK libraries are only installed on managed servers that need to interact directly with VMware ESXi.
Part 1: Check Known OS-level Issues
While rare, it is prudent to review the following potential known OS-level issues before proceeding with further troubleshooting.
Windows-based VMware Backup Proxy
- 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
- Customers have reported that some RHEL (8/9) deployments may fail to load the VDDK libraries due to a missing dependency: libcrypt.so.1. For more information, review this thread on Veeam's RnD Forums.
Part 2: Reinitialize the Packages on the VMware Backup Proxy
Having ruled out OS-level issues, perform the following steps to force Veeam Backup & Replication to check the proxy for missing packages:
- Switch to the Backup Infrastructure view.
- Select the Backup Proxies node in the navigation tree.
- Edit the VMware Backup Proxy that the job reported using prior to the error message.
- When the Edit VMware Proxy wizard opens, click Finish, and Veeam Backup & Replication will check the proxy for missing packages.
- Rerun the job to determine if the issue is resolved. If the job fails, proceed to the next section.
Part 3: Manually Reinstall VDDK Packages
If the error persists and reinitializing the proxy packages does not resolve the issue, the remaining option is to manually remove the VDDK package from the proxy and then perform the package reinitialization.
Windows-based VMware Backup Proxy
- Connect to the VMware Backup Proxy.
- Open the Installed Apps list.
- Locate and uninstall the VMware VDDK package.
- Follow the steps in Part 2: Reinitialize the Packages on the VMware Backup Proxy
Linux-based VMware Backup Proxy
- Connect to the VMware Backup Proxy via SSH.
- Execute the following command to uninstall the VDDK package:
sudo yum remove vmware-vddksudo apt purge vmware-vddksudo zypper remove vmware-vddk- Follow the steps in Part 2: Reinitialize the Packages on the VMware Backup Proxy
More Information
VDDK Component Package
The VDDK libraries component is deployed to a machine when it is added as a VMware Backup Proxy. If the VMware VDDK package is missing, you can force VBR to check for and deploy the package by editing the proxy entry under Backup Proxies in the Backup Infrastructure view and then proceeding through the wizard steps.
This change also means that after 12.1.2, if VDDK libraries need to be manually redeployed, they must be redeployed using the dedicated VDDK packages found in 'C:\Program Files\Veeam\Backup and Replication\Backup\Packages\' on the Veeam Backup Server.
- vmware-vddk.msi — VDDK libraries for Windows machines.
- vmware-vddk_*_amd64.deb — VDDK libraries for Debian-based distros.
- vmware-vddk-*.x86_64.rpm — VDDK libraries for Red Hat-based distros.
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.
Legacy Error Cause Information
When running Veeam Backup & Replication 9.5 or older, this error will occur when attempting to use a VMware Backup Proxy that is running Windows Server 2008. The VDDK libraries require Visual C++ run-time components, and Veeam Backup and Replication does not automatically install them on servers running Windows Server 2008; thus, they must be installed manually.
| Veeam Backup & Replication 9.5 and older C++ Requirements | |
| VMware vSphere version | Visual C++ Redistributable Packages version |
| 4.1. 5.0, 5.1 | not required |
| 5.5, 6.0 | Microsoft Visual C++ 2008 Redistributable Package (x64) |
| 6.5, 6.7 | Visual C++ Redistributable Packages for Visual Studio 2013 |
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.