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 !

@panzersrmm I tried to snapshot and revert on a VM with Resource set + ACLs and they did not disappear... ?

@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.

@tc-atwork plus +++ on this one.
Tags in XO5 are so useful for smart backups, to filter everything.

in XO6 for now they seems to be just informational. we can't even filter the treeview by tag actually !

hope the benefits of XO5 tags will be ported to XO6

@acebmxer if possible for you, restart toolstack of the host being attached to this VM.
and check to see if this vdi still attached to dom0

sometimes a full reboot of the host is needed, and you get an orphaned snapshot instead of vdi attached to dom0

delete the orphaned snapshot and. backup will get in place like before.

@MajorP93 stress of VM migration XD

good luck with your V2Vs !

@MajorP93 in your screenshot, CA and CA_1 seems to be two disks on the original VM... ?

They're even different in size.

each are suffixed with -000001-delta, indicating one snapshot, on each disk

two vmdk on source gives you two vdis on destination, as intended

@olivierlambert I get you.

Same in veeam and synthetic fulls, it's only between the server/proxy and the repository.
but we get a progressing percentage while the job sits while doing the synthetic full.

would be cool to "see" the progress of merging.
why ? bad habits from previous technologies used I guess.

@florent i always check it, to avoid a merging process to be disrupted by another job.

so when the backup tranfer is done (we have a progress bar), the job just sits there.. .merging in background, without progress bar or percentage.
5 minutes later, the backup job finishes.

so your stats are flawed (used data over time) if time of merging is taken in account

see what I mean ?

@farokh one backup job should leave one snapshot.

this is the way. to differentiate from previous backup the data to be put in the delta, it has to refer to this snapshot.

delete it and you get a full backup ongoing.

if you have two snaps on your VM, either you have a manual one, or you have multiple backup jobs backuping this VM (check the backup tab of the VM ?)

@flakpyro thank you

@florent , would be nice to add this to XCP backup ? merge progress