Challenge
Virtual Appliance mode fails.
The error "VDDK error: 3.One of the parameters is invalid" :
[timestamp] <13> Info [AP] (Client) error: Failed to open VDDK disk [[datastore] VMname/VMname.vmdk] ( is read-only mode - [true] )
[timestamp] <13> Info [AP] (Client) error: --tr:{
[timestamp] <13> Info [AP] (Client) error: --tr:VDDK error: 3.One of the parameters was invalid
[timestamp] <13> Info [AP] (Client) error: --tr:Failed to create VM connection.
[timestamp] <13> Info [AP] (Client) error: Logon attempt with parameters [VC/ESX: [xxx.xx.x.xx];Port: 902;Login: [root];VMX Spec: [moref=736];Snapshot mor: [/vmfs/volumes/4798dc72-9bf20064-1900-001f295d88f0/VMname/VMname.vmx-snapshot-280];Transports: [hotadd]] failed because of the following errors:
[timestamp] <13> Info [AP] (Client) error: --tr:}
Cause
There are four situations that commonly cause this error:
- The Veeam VM is on a different host than the source VM, and the VM was added to the job through the host directly (as opposed to through the VC).
- Storage hosting disks of the source VM is not accessible by the ESX on which the Veeam VM is running
- The Veeam VM and the source VM are managed by different VC's.
- The Veeam VM and the source VM are managed by the same VC, but located in different DataCenters
Solution
In the first case above, add the affected VM to the job by the VC.
In the other situations, however, Hotadd/Virtual Appliance mode is not applicable or possible given the current VMWare architecture.