Beware if you are upgrading to v11.0.1.1261 and using DataDomain

[mrholm]

Hi
We just upgraded parts of our Veeam environment to v11.0.1.1261 and suddenly all of our secondary copies to DataDomain started to fail with:

2023-03-10 13:37:40 :: Failed to pre-process the job Error: Cannot transfer meta to the master extent. All failbacks failed.
read: An existing connection was forcibly closed by the remote host
--tr:Cannot read data from the socket. Requested data size: [4].
--tr:Failed to read data from throttled device.
--tr:Failed to upload item. Datasource: [D:\Veeam\TEMP\Veeam_7080d9d0-0102-4958-80b3-df427ffa6fa7.vbm]. Targe item type: [file]. Target path: [ddboost://xxxxxx:emea-veeam-repl-01@/xxxxx/swe006_copy_vm_st

We restarted all involved servers and DataDOmain still same error, we can access the files on DD from Veeam but the copies fail. Then we realized we had a case with support several months ago (05236920 ) and the outcome was a new DDboost library that have been working since then.

No we looked at the DDboost library from the v11 update and the version that Veeam installed now is 7.0.0.22 and the one we had in the fix is 7.7.1.0
So we just followed the instructions and replaced the DLL files and swish now all copies are working again.

This is the first time I've seen that Veeam missed adding newer working DLL's from a official fix into the new upgrade, this might be something for the Veeam development to look at?

So if you are having same error as we did please request https://storage.veeam.com/Fix_349005_15d733f041.zip

//Mats

[foggy]

Hi Mats, just to confirm I'm getting what happened correctly - do you mean you have the mentioned DDBoost 7.7 hotfix applied to a v11 installation and after upgrading to v11a (v11.0.1.1261) the DDBoost lib was overwritten back to the original 7.0 one?

[mrholm]

Sorry for late reply but that's exactly what happend

[foggy]

That's expected as v11a was shipped with the same DDBoost SDK version 7.0. We've switched to 7.7.1 LTS in v12.