BugZero found this defect 3387 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/3/2024
Veeam Backup & Replication
8.0
No fixed releases provided.
When performing a write operation using Direct-SAN transport mode (e.g., Entire VM Restore, VM Hard Disk Restore, or initial run of a replication job) the task fails with the error: Unable to execute write operation using advanced transport, failing over to network mode... ERR |VDDK error: 16000 (One of the parameters supplied is invalid) (The error code may vary, but the informational message will be the same) Error as shown in logging: vdl | [vddk] VixDiskLib: VixDiskLib_Write: Write 2048 sectors to disk at 0 failed. Error 16000 (One of the parameters supplied is invalid) (DiskLib error 4096062: One of the parameters supplied is invalid) at 6901. cli | ERR |Command 'Write' has failed. cli | >> |--tr:Failed to write to a virtual disk. Start sector: 0, length: 2048 cli | >> |VDDK error: 16000 (One of the parameters supplied is invalid). Value: 0x0000000000003e80 cli | >> |An exception was thrown from thread [15316]. dsk | Disabling advanced transport modes. cli | ERR |Send thread (channel) has failed.
This error occurs when the LUNs presented to the Backup Proxy for DirectSAN access are read-only.
To confirm that these LUNs are presented in Read-only access, please refer to your SAN configuration interface. If the disk is presented as Read-only, you must either connect the volume with write access or use a different transport mode (i.e., Virtual Appliance or Network).
Limitations for the Direct SAN Access Mode