DataTransfer.SyncDisk

[fafa24]

Dear All,

Support case is: 02263392

We are using the free Windows Agent 2.0 to back up a Windows Server 2008 R2 to Veeam 9.5 repository. It worked well in the past for a long time. But now we are getting this error message.
The server has two partition C und D. The error message is for partition D.

31.07.2017 12:15:29 :: Error: Incorrect function. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Incorrect function. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [22953]. Failed to download disk.

Do you have an idea what this error message means? I tried to initiate an Active Full Backup with no luck. Backup failed with same message.

Thanks,

[Dima P.]

Hello fafa24,

Please keep working with our support team and do not forget to update this thread with the investigation results. Thanks in advance.

[stabak]

Support case is: 02263392
I have the same error. Can you help me with additional info on what to do?
Thanks.

[Vitaliy S.]

OPs case was resolved by fixing issues (bad blocks) on the RAID controller (according to the ticket notes).

[ByteBuster]

Same problem here ...

[Vitaliy S.]

Both cases were caused by bad blocks on the disk, so please analyse your storage hardware to resolve this issue.

[jurcacristian]

Hi Guys, i'm experiencing the same issue:

Code: Select all

Job finished with error at 8/1/2018 10:37 AM

    Error: The device is not ready.
    Asynchronous read operation failed
    Failed to upload disk.
    Agent failed to process method {DataTransfer.SyncDisk}.
    Exception from server: The device is not ready.
    Asynchronous read operation failed
    Unable to retrieve next block transmission command. Number of already processed blocks: [2].
    Failed to download disk.

This is performed from a Windows Veeam Backup agent using Cloud Connect as a repo.
Just want to confirm what was mentioned earlier, i alredy have a support case (03120797) but i would like to sort this more faster. Is this issue on the source side ? What can i recommend the tenant to fix this 'bad blocks' ?

thanks

[Dima P.]

Hello Cris,

Check the source disk for bad blocks via check disk with full scan option enabled. You are welcome to use any third party tools as well to identity the storage corruption as well.

[jay-r.alvarez]

I'm getting the same error message. any updates on how to resolve this issue?

I two new Server 2016 server 1 Physical and the other one is a VMware guest. I tried backing up the C drive and I keep getting this error message as well.

[Dima P.]

Hello Jay-r.

Most likely this error is related to the disk corruption. The recommendation would be to check the source disk for bad blocks. If required you can open a support case with our team and they can help you with troubleshooting process. Thanks.

[jurcacristian]

Hi guys, we kind of sorted this with a work around. We used a linux repository instead of CIFS in VBR, then asked the veeam agent user to use the new tenant/repo. It still working without any issues.
please check the KB bellow also:
https://www.veeam.com/kb1735

Cris