Version 13.1 Port Conflict with Datadog

[ndaviscmm]

Veeam Support - Case # 08185172
Veeam Backup and Replication 13.1 on Windows

I am posting to hopefully save someone else from encountering issues. We have used Datadog for monitoring on our Veeam servers for many years without issues.
By default Datadog uses port 6162 for the process-agent.exe service. Veeam also uses this port for several things including the veeamtransportsvc.exe service.

Support was initially stumped, as we had been running version 13 without issues. The issue only occurred when we went to version 13.1.
I was able to change Datadog to use a different port to resolve the issue.

Example of failure from Veeam:
8/28/2026 12:55:25 PM Failed : Processing SERVERNAME Error: Failed to prepare VM for processing: TCP stream was closed Failed to invoke rpc command (0:00:03)

Datadog and Veeam have coexisted with this conflict since version 12 at least so I wanted to share incase this bites anyone else.

[david.domask]

Hi Nate,

Thank you for sharing the case number; the case is already with our Expert Support Team (Tier 3) and based on their most recent note, agreed it's a bit unusual as 6162 has been the default port for the Data Mover service for some time (link is to v11 archived User Guide, but afaik it was same port since I started with Veeam on v7)

Not sure what to tell here, but glad you were able to change the Datadog port; I aware of some unsupported hacks that would temporarily change the datamover default port, perhaps that was in place? Or maybe it's to do with Datadog's internal process communication -- I have not used Datadog, but based on the docs looks like it's only for intra-process communication, so maybe something changed there, unclear.

Regardless, sounds like the solution is the correct one.