Backup traffic from Hyper-V to DataDomain

[gmajestix]

Hello,
we are using DataDomain added to Veeam as a deduplication appliance. After upgrade from 12 to 13 I noticed that all backup traffic from Hyper-V host goes through Veeam BR server to DataDomain. Before upgrade backup traffic from Hyper-V hosts went directly to DataDomain. Anyone else seeing this?

[foggy]

Data Domain traffic never goes directly to the array, there's always a gateway server in the loop, which may be a backup server itself or a dedicated server, depending on your setup.

[gmajestix]

This when Veeam was on version 12. HV01 is one of the Hyper-V hosts.
29. 01. 2026 22:00:41 Succeeded : Using gateway HV01 for repository DDVE50-1veeam01a

And this is from now when Veeam is on version 13.
23. 02. 2026 22:01:01 Succeeded : Using mount server XXXXX (Windows) as a gateway for repository DDVE50-1veeam01a

XXXXX is the Veeam server.

[foggy]

The gateway selection algorithm didn't change in v13. Most likely, the change is caused by environmental factors or specifics. Please review the gateway selection description, which may give you some hints.

[gmajestix]

I see the in the document that is says:

The gateway server can run on a Microsoft Windows or Linux machine or Microsoft Hyper-V host that is added to the backup infrastructure as a managed server. The machine must meet the system requirements.

and Hyper-V servers are added under managed servers. If go to edit one of the Hyper-V Server, Review under Component name are listed Veeam Data Mover service, Hyper-V Integration and Guest Interaction Proxy. If I check the same for the Veeam Server there is HPE StoreOnce Library and Dell Data Domain Library. I'm guessing the Hyper-V are missing Dell DataDomain Library.

[foggy]

Looks strange as it should be installed by default on any Windows server added to the infrastructure. Let me check internally.

[foggy]

So what happened was we removed these libraries from the common transport component (split them for security reasons) and missed the Hyper-V role in the list of hosts on which it should be installed. We will bring this capability back in the next version - thanks for the heads up!

[gmajestix]

Ok. Can I install it manually?

[foggy]

Yes, but this will not include the Hyper-V host in the scope of possible gateways, unfortunately. That was also my first workaround assumption that we tried internally.

[SteveK821]

Any idea when the next version will be released? Or could there be a hotfix for this issue? We have a customer wanting to move to V13 VSA and they have Hyper-V Hosts with DD Repositories. We may have to hold off on this until it's resolved, as otherwise we would need to deploy extra resources to compensate.
Does this also affect other Dedup appliances? I would assume StoreOnce since those components are also normally installed with DDboost when adding a new host.

[foggy]

Hi Stephen, it's around mid-year.

As a workaround, you can add the Hyper-V host as a managed Windows server (using IP, if it was added by FQDN and vice versa).

Yes, it affects HPE StoreOnce repositories as well.