OPERATIONAL DEFECT DATABASE
...
...
A Backup or Replication job fails with an error containing 'VDDK error: 3' This most often occurs when forcing a VMware Backup Proxy to use 'Virtual Appliance' transport mode and disabling the 'Failover to network mode' option.
The most common scenario is that the disk(s) of the VM being processed cannot be attached to the VMware Backup Proxy, for example: The VM (Virtual Machine) being processed was added to the job through a standalone ESXi host (as opposed to through a vCenter Server), and the VM acting as VMware Backup Proxy is on a different ESXi host. The datastore containing the disks of the VM being processed is not accessible by the VMware Backup Proxy VM because the ESXi host the Proxy is running on cannot access that datastore. The VM being processed and the VMware Backup Proxy VM assigned to the task are in different vCenter Servers. The VM being processed and the VMware Backup Proxy VM assigned to the task are in different virtual data centers under the same vCenter Server.
When deviating from the default transport mode configuration (Automatic + Failover to Network), the requirements for the selected transport mode must be met. Review the requirements and make adjustments to the environment or configuration as necessary: Requirements for the Virtual Appliance mode Appliance Mode (Hotadd) Requirements and Troubleshooting
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
