Discussions specific to the VMware vSphere hypervisor
Post Reply
jaychunlai
Lurker
Posts: 1
Liked: never
Joined: Feb 01, 2019 11:01 am
Full Name: Chun Lai
Contact:

VDDK error 14009

Post by jaychunlai » Feb 04, 2019 8:59 am

Hey guys,

I was hoping some of you guys could help me out, backup Veeam had been running good for some time, then I bumped in this error message:

Code: Select all

Error: VDDK error: 14009 (The server refused connection). Value: 0x00000000000036b9
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.  
A support case has been openend as well (03393772)

HannesK
Veeam Software
Posts: 2354
Liked: 283 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: VDDK error 14009

Post by HannesK » Feb 04, 2019 9:57 am

Hello,

please give support some time to work on your case, as you opened the case with evaluation support on Friday (evaluation tickets are not processed during weekend).

Best regards,
Hannes

L0g333
Novice
Posts: 4
Liked: never
Joined: May 10, 2017 9:36 am
Contact:

[MERGED] Backup Up VEEAM VM fails with Error 14009 - Failed to upload disk

Post by L0g333 » Feb 06, 2019 12:40 pm

Hi there :)

for some days i have a problem with backing up our VEEAM VM, that used to work like a charm for more then a year now. After ~19.5GB of transferred Data, the Backup of the VEEAM VM fails with the following error (All other VMs are backed up without any problem):

Code: Select all

06.02.2019 12:26:13 :: Error: VDDK async operation error: 14009. Value: 0x00000000000036b9
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: VDDK async operation error: 14009. Value: 0x00000000000036b9
Unable to retrieve next block transmission command. Number of already processed blocks: [62740].
Failed to download disk.
Some background information to the infrastructure:

VEEAM Backup Server (Windows Server 2016, VBR 9.5.4.2615) and Backup Target (QNAP NAS) are running in LAN A.
ESXi 6.7 Host (Build 11675023) and vCSA 6.7 (Build 11726888) are running in LAN B.

-> VMware and VEEAM are up-to-date.

LANs are seperated by Sophos Firewall. Any-Any FW Rule doesn't change the result.

VEEAM Backup Server is running as VM on the ESXi Host, and fails backup up its own VM. There's no seperate Backup Proxy in LAN B. VEEAM is connected to vCenter.

After hours of googling and reading, rebooting and updating, i am running out of ideas. Maybe someone here has an idea, what the cause of this could be.


I found this on that topic: https://vinfrastructure.it/2018/10/veea ... ror-14009/ But I am not sure if that can be the answer. We didn't touch the network and don't encounter other network problems.

Thanks a lot guys!

v.Eremin
Product Manager
Posts: 15807
Liked: 1252 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: VDDK error 14009

Post by v.Eremin » Feb 06, 2019 6:03 pm 1 person likes this post

Hello, what's the support ticket ID for this issue (as requested when you click New Topic) please? Thanks!

L0g333
Novice
Posts: 4
Liked: never
Joined: May 10, 2017 9:36 am
Contact:

Re: VDDK error 14009

Post by L0g333 » Feb 06, 2019 6:36 pm

Thank you for that hint @v.Eremin. I thought, I'd open a forum post instead of opening a ticket, since the problem isn't that severe. I'll catch up on this later, when i'm back in the office.

I actually wasn't clear about the fact i'd need a support ticket for technical issues. I must have overseen that little notice, when creating my forum post. Maybe it would be helpful to make the forum rules (veeam-backup-replication-f2/rules-of-po ... -t755.html) a sticky post.

Sorry for the inconvenience.

Andreas Neufert
Veeam Software
Posts: 3235
Liked: 564 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert Director of Product Management Global Alliances
Location: Germany
Contact:

Re: VDDK error 14009

Post by Andreas Neufert » Feb 07, 2019 10:31 am

Just to give some additional background. This forum is not a support forum and only some of the support members are part of the community because of personal interest. Main part of the forum is to interact with Veeam product management, R&D and systems engineers/architects.

m.novelli
Veeam ProPartner
Posts: 346
Liked: 40 times
Joined: Dec 29, 2009 12:48 pm
Full Name: Marco Novelli
Location: Asti - Italy
Contact:

Re: VDDK error 14009

Post by m.novelli » Feb 07, 2019 10:42 am

I have a customer that is experiencing this issue after update to B&R 9.4 Update 4

Case ID 03398738

After Veeam update he get a "DataTransfer.SyncDisk" error on a VM. Support asked to try to clone / Storage vMotion the VM

I'll let you know

Marco

v.Eremin
Product Manager
Posts: 15807
Liked: 1252 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: VDDK error 14009

Post by v.Eremin » Feb 07, 2019 12:37 pm

Kindly, keep working with our support team directly. Also, don't post log snippets here (it's against the forum rules). Thanks!

m.novelli
Veeam ProPartner
Posts: 346
Liked: 40 times
Joined: Dec 29, 2009 12:48 pm
Full Name: Marco Novelli
Location: Asti - Italy
Contact:

Re: VDDK error 14009

Post by m.novelli » Feb 11, 2019 8:48 am 2 people like this post

Hello, the issue with my customer was solved after a Storage vMotion of the affected VM

Cheers

ppcat
Lurker
Posts: 1
Liked: never
Joined: Sep 20, 2018 3:21 pm
Full Name: wendy zhou
Contact:

Re: VDDK error 14009

Post by ppcat » Feb 13, 2019 4:36 pm

We are having exactly same issue.
support case 03404281

on the target vm :
we did Filesystem checks -- come back clean
Disk checks in the OS --come back clean
Disk checks at the VMFS level-- come back clean
All snapshots have been removed to eliminate any potential issue with that
Nothing configuration wise has changed on that machine
Then :
re-run backup still failed with same error .
re-create a new job for the target vm , returns same error

Gostev
SVP, Product Management
Posts: 23654
Liked: 3127 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: VDDK error 14009

Post by Gostev » Feb 13, 2019 9:00 pm

Thanks everyone for including their support case IDs. The issue is not wide spread, so the more material we have we work on - the better!

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests