just to #brag

Deploy of worker is okay (one big rocky linux with default settings 6vcpu, 6Gb RAM, 100Gb vdi)

first backup is fine, with decent speed ! (to a xcp hosted S3 minio)

will keep testing

I did stick to version: 1 in my working configuration

Had to rename my "Ethernet 2" nic name to Ethernet2 without the space

You have to put the exact template nic name for this to work.

@Forza I didn't try, as my default Graylog Input was UDP and worked with the hosts...

But guys, that was it. In TCP mode, it's working. Rapidly set up a TCP input, and voila.

@MK.ultra don't think so

it's working without for me.

@tmk hi !
Many thanks, your modified python file did the trick, my static IP address is now working as intented.

I can confirm this is working on Windows 2025 Server as well.

finally understood the network problem...

If you have a match of MAC ADDRESS in netplan

Veeam restores the VM with a NEW MAC ADDRESS

so either you delete the match, or get the good mac on the VIF...

ok, installed pws 7

and it's working

@florent okaaaay, I was taking it the wrong way.

I managed to have one proxy to see two remotes as intended, thanks to your advice.
Need to do some routing (DC1 and DC2 are on two distant datacenters, separate subnets) to make each proxy see the good route to each distant remote.

Thank you !

@olivierlambert when planning our infrastructure, Vates engineer told us to avoid Broadcom nics but to go Intel or nvidia/Mellanox.

we bought Mellanox

This is the way.

@MajorP93 stress of VM migration XD

good luck with your V2Vs !