VM Backup and Copy failed

[Innuendo]

Hi everyone,

while trying veeam backup i went into trouble i cannot solve:
I have turned off all virtual machines in my esx 4 hosts and tried to copy all data to an external iscsi storage.
i tried agentless mode, i tried automode, but i always get this error:

5 of 5 files processed

Total VM size: 30,00 GB
Processed size: 921,61 MB
Processing rate: 3 MB/s
Backup mode: NBD with changed block tracking
Start time: 23.01.2010 09:08:29
End time: 23.01.2010 09:14:21
Duration: 0:05:52

Copying file "[Storage1] VM-VC/VM-VC-flat.vmdk"
Failed to get file 'vddk://<vddkConnSpec><viConn name="10.50.2.176" authdPort="902" vicPort="443" /><vmxPath vmRef="448" datacenterRef="ha-datacenter" datacenterInventoryPath="ha-datacenter" snapshotRef="448-snapshot-3" datastoreName="Storage1" path="VM-VC/VM-VC.vmx" /><vmdkPath datastoreName="Storage1" path="VM-VC/VM-VC.vmdk" /><transports seq="nbd" /><readBuffer size="2097152" /></vddkConnSpec>'
Client error: VDDK error: 1.Unknown error
Unable to read file block. File: [vddk://[Storage1] VM-VC/VM-VC.vmdk]. Offset: [1074790400]. Block granularity: [1048576].
Unable to retrieve next block transmission command. Number of already processed blocks: [1025].
Unable to receive file.

Server error: VDDK error: 1.Unknown error
Unable to read file block. File: [vddk://[Storage1] VM-VC/VM-VC.vmdk]. Offset: [1074790400]. Block granularity: [1048576].

any hint or help would be very nice

kindly regards
Innu

[Vitaliy S.]

Hello Innu,

I've deleted your post with the log quote. Try to download VMX and VMDK files using VMware Infrastructure Client Datastore Browser, can you perform this operation successfully? Please contact our support team directly, they will be able to assist you in troubleshooting the issue.

Thank you!

[ivanmantilla]

Veeam support ID: 00172885

trying to make a backup to the vcenter server vm, on vsphere 5.0, i got the error VDDK error: 1.Unknown error Unable to retrieve next block transmission command. all the other jobs with vms works perfectly.
I´m working with Veeam 6.5 patch 1

[stevenwells99]

I am also having this issue. Have you got any further with this?

[veremin]

Hi, Steven. According to the provided support ticket, the problem was at VMware side - it appeared that source .vmdk was corrupted.

The proposed solution was to clone the given VM and run off the clone.

In order to understand whether you have a similar issue you can exclude corresponding disk from VB&R job and see if the job finishes successfully.

Hope this helps.
Thanks.