VDDK async operation errror: 2

[antman157]

Anyone found a resolution to this error? Or has anyone seen this error?

Code: Select all

4/9/2019 7:40:28 AM :: Processing DB02 Error: VDDK async operation error: 2. Value: 0x0000000000000002
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.

Ive been working with support, but I am still getting the error. Ive moved the VM to a different host, moved the storage, rebooted hosts, VMs, etc... Its been going on for about 3 weeks now. Sometimes, I will get a backup. Its only my 2 SQL servers, Ive got about 30+ other jobs and none of the other servers have this error.

Veeam Support - Case # 03490794

[PTide]

Hi,

It looks similar to this case. Nevertheless, please keep working with your support engineer.

Thanks!

[antman157]

Yeah I am on 6.5 and Veeam 9.4a

[rjtestabg]

This problem seems to happen only on VMs with multiple disks....

[antman157]

My SQL servers have multiple disks, but I also have other servers with 2-3 disks that do not have this issue. Its just SQL for some reason.

[tcolgin]

Case ID 03617623

Anyone ever come across this error? I came across this thread vmware-vsphere-f24/backup-issues-after- ... 55490.html which I feel may be a culprit.

I am setting up a new job for Exchange application aware enabled backups. Credentials works for testing application level backup. Other VMs backup fine. I have tested with support of turning off application aware option and it still fails. The backup starts writing to the repository and the just fails after a few GB on each drive (atleast 9 drives on the server).

Backup and Replication version 9.5.4a on a Windows 2012 R2 server (R730xd with local disk). No firewalls between backup server and Exchange servers.

[tommy.lidal]

i've got the same issue now after upgrading my vcenter to 6.7U3 (hosts still 6.5).. and upgraded the VeeamBackup&Replication_9.5.4.2866.Update4b cause i tought it was fixed.. gues not..
getting sick of haveing to open cases all the time to get fixes.. Veeam needs to be better in putting up "pottensial errors" in notifications on https://my.veeam.com/alerts.

Be aware: this is on both backup-jobs and copy-jobs

Case # 03853779
What..
(POSTING AN ERROR OR TECHNICAL ISSUE?
You must include support case ID, or your post will be removed (learn more) )

[Andreas Neufert]

Hi, VDDK errors are VMware internal errors when we as backup vendor use the VMware Software (VDDK) kit to transport data to the host.
In this case VMware introduced a faster way to process data over Network NBD mode (async processing). As this is a new technology for VMware there are more potential bugs. There are 2 ways to address this. Check that you hosts and vcenters are at latest build from VMware 6.7 U3 (my guess is that not all hosts are updated) or we can add a registry key in Veeam that disable the new VMware processing.

You can get the Key by our Support.

We are working with VMware on this continously on their software side.

[tommy.lidal]

I got the "regky fix" and it worked.. so error is still in Update 4b for Veeam Backup & Replication 9.5.

[Andreas Neufert]

The reg key just disable functionallity from VMware that is not working correctly. As I said we are working with VMware on this.

[tommy.lidal]

maybe update https://www.veeam.com/kb2970 ??
put a bulitin on it about the problem..

[dgongora]

Any fix on that? I got the same issue...

[Andreas Neufert]

Please check with our support dgongora

[sbk]

This is still a problem. I had several replica's with this issue all of a sudden (some jobs still worked fine - other failed). The registry key resolved the issue for me. If you are having the same problem try adding the key per support:

The key should be applied on the VBR server:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

VMwareDisableAsyncIo=1
• Type: REG_DWORD
• Default value: 0
• Description: 9.5 update 4 registry key.

No service restart is required after adding the key, just try running the job(s) again.

Case #03911115

[Andreas Neufert]

If you have a chance and have access to one of our engineers to get the v10 release candidate then you can test the new processing. There, we disable asyncronous processing only for the operations with the VMware own bug. No registry key needed.

[ortoscale]

I'm getting same error with v10.

[ortoscale]

after applying reg key it works. We deployed VBR v10 on new machine with restored config from vbr 9.5.

[Ollo]

After upgrading to VCenter 6.7U3 also get the error. Using VBR 10a. Is the "fix" removed from VBR v10 to v10a?

[Gostev]

It's very unlikely for any functionality to be removed in a minor update.