Article Applicability
The error message states that 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.
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Β
This error is displayed when the VDDK libraries on the VMware Backup Proxy fail to be loaded.
VDDK Component Package
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.
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 proceed through the wizard steps.
This change also means that after 12.1.2, if VDDK libraries need to be manually redeployed, they must redeployed using the dedicated VDDK packages found in 'C:\Program Files\Veeam\Backup and Replication\Backup\Packages' on the Veeam Backup Server.
The VDDK libraries may fail to be loaded for the following reasons:
**Note:**Prior to Veeam Backup & Replication 12.1.2, the VDDK libraries were included with the Veeam Transport package (VeeamTransport.msi).
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.
_
To resolve the issue, repair the VDDK library package:
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.
/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.
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.
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.
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 automatic aly install them on servers running Windows Server 2008; thus, it must be installed manually.
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
__
Swipe to show more of the table
__
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.
Vendor | Product | Version | CPE |
---|---|---|---|
veeam | veeam_backup_\&_replication | 12.2 | cpe:2.3:a:veeam:veeam_backup_\&_replication:12.2:*:*:*:*:*:*:* |
veeam | veeam_backup_\&_replication | 12.1 | cpe:2.3:a:veeam:veeam_backup_\&_replication:12.1:*:*:*:*:*:*:* |
veeam | veeam_backup_\&_replication | 12 | cpe:2.3:a:veeam:veeam_backup_\&_replication:12:*:*:*:*:*:*:* |
veeam | veeam_backup_\&_replication | 11 | cpe:2.3:a:veeam:veeam_backup_\&_replication:11:*:*:*:*:*:*:* |
veeam | veeam_backup_\&_replication | 10 | cpe:2.3:a:veeam:veeam_backup_\&_replication:10:*:*:*:*:*:*:* |
veeam | veeam_backup_\&_replication | 9.5 | cpe:2.3:a:veeam:veeam_backup_\&_replication:9.5:*:*:*:*:*:*:* |