VDDK async operation error (multiple customer locations suddenly)

[dcolpitts]

I've not had an opportunity to open a ticket yet, but just wondering if any other MSPs / Veeam Partners are suddenly seeing multiple independent customer locations having their VMware replica jobs failing with "Failed : Error: VDDK async operation error: 16000. Value: 0x0000000000003e80 Failed to calculate disk digests."

I'm not talking about just one site or just one VM. I'm talking about almost every one of my clients using replication and every single VM at those sites, all within the past week or so.

dcc

[dcolpitts]

Interesting. Even my own replication job was failing to our off-prem location... I rebooted my remote hosts and the job appears to be running now... I guess I'm going to be doing some reboots shortly of other hosts.

[MarkBoothmaa]

Its not a disk stuck on a proxy is it if you're using Hot-Add

[Mildur]

Hello Dean,

I’m glad it works after a reboot.

For future reference (or if the issue occurs again): technical issues always require a support case. We can’t investigate such issues through a forum topic. Without a case number, such topics may eventually be deleted by moderators.

Best regards,
Fabian

[dcolpitts]

Mildur - I've been around here long enough - I wasn't asking anyone at Veeam to investigate it, so I'm not quite sure why you responded as you did. I was asking if anyone had seen this particular issue rather than initially tie the support team up. Is that not what these forums are for - peer self help?

And to MarkBoothmaa - no - I had already checked that, I just found it weird that I would suddenly see the same thing at multiple locations within days of each other when they had been on v13 since it came out and it hadn't occurred before.

[Mildur]

Hi Dean

I was asking if anyone had seen this particular issue rather than initially tie the support team up. Is that not what these forums are for - peer self help?

This forum is not the place to ask such questions. Other forums may allow bringing up technical issues with the community, to see if it can be solved, but our forum has a different purpose. Please review this forum’s purpose in our forum policy again. The link was also provided in red letters when you have created this topic.

Our forum policies have been discussed and argued multiple times in other topics. I may close this topic if this turns into another discussion about our forum policies.

So please stay on topic. Provide a case number if you want to discuss your technical issue, or this topic may be deleted.
Our Support Team will be able to tell you if other customers are currently facing similar issues or not. They have the "data" about what technical issues our customers have reported to us through cases.

Thank you,
Fabian

[dcolpitts]

Just close it. I'll go elsewhere in the future apparently.