6 matches found
Failed to get guest OS path for newly attached disk there are 2 new disks with uuid
Challenge A backup job using a Linux-based VMware Backup Proxy fails with the error: Failed to get guest OS path for newly attached disk /.vmdk: there are 2 new disks with uuid Cause This error occurs when the Linux-based VMware Backup Proxy processing the virtual machine has multipath enabled...
Error: Backup proxy is missing C++ runtime components
Article Applicability 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...
Required Applications and Permissions for Multi-OS FLR and Repository Support for Linux
Purpose This document provides information about required applications that must exist on Linux machines to function with Veeam Backup and Replication. Solution Permissions Requirements Permissions are dependent on the intended role of the Linux server. For more information, review this page of t...
How to restore vCenter Server without a vCenter Server
Challenge The vCenter Server is not available and the vCenter Server VM needs to be restored. Solution To restore the vCenter Server, you will need to add one of the individual ESXi hosts to Veeam Backup & Replication, allowing you to target that host directly to restore the vCenter VM. Possible...
How to setup SAN access for use with Veeam Backup & Replication.
Purpose This article documents how to set up Direct SAN Access for use with Veeam Backup & Replication. The Direct SAN access transport mode is recommended for VMs whose disks are located on shared VMFS SAN LUNs that are connected to ESXi hosts over FC, FCoE, iSCSI, and on shared SAS storage. In...
VDDK Error 3 Troubleshooting
Challenge A Backup or Replication job fails with an error containing 'VDDK error: 3 ' This most often occurs when forcing aVMware Backup Proxy to use 'Virtual Appliance' transport mode and disabling the 'Failover to network mode' option. Cause The most common scenario is that the disks of the VM...