Hello

been running a homelab for many years working my way thru the various versions of vmware.. Currently had 2 Hp Elitedesk g5 sff desktops acting as hosts with 64gb memory and both local ssd and TrueNAs shared storage for the dozen or so VMs i have.. I have separate physical elitedesk running win 2025 which had Veeam for VM backup and restores.. All had been working pretty well but decided with Broadcom doing nobody any favours it was time to look elsewhere.. hence the switch to xcp ng. So moved all my vms to one host and decied to take the plunge and setup the other host with v 83 as a test bed and try importing some vms.. checking out the networking .. backups etc.
So a couple of weeks in now and have all my Vms across up n running nicely.. guest tools installed.. nfs remote setup to my veeam box on a shared folder with a dedicated interface /nic for the backups on a 1GB conenction....have a 10 gb direct link now to TrueNAs for shared storage. I'm going to let this bed in for now but i suspect that for me its bye bye to vmware. Once i'm happy i will get my now powered off vmware host back up with xcp ng installed and added to my pool to give me my resilience back.... and then give vmotion between the host a go

All in all a great product so far. Many Thanks

@nikade My 10gb nic are directly connected to my hosts.. i dont have a 10gb switch.. the mgmt is connected via switch ports...

@nikade i think the problem is its using the mgmt interface to do the backup..its not touching the 10GB nics.. when i set it under Pools/Adanced/Backup to use the 10gb nic as default the job fails... setting it back to none the job is successful with a speed of 80 MiB/s.. so using the 1GB mgmt nic... how do i get the backups to use the dedicated 10gb link then. ?

@olivierlambert

My hosts are Hp Elitedesk G5 SFF.. 64gb Mem Processor type is Intel Core i5 3.0Ghz i believe.. nics are showing connected @ 10GB

@olivierlambert

Continuous replication.... runs every 12 hrs...

@olivierlambert ok here's a bit from the log.. Start: 2025-09-03 12:00
End: 2025-09-03 12:00
Duration: a few seconds
Size: 624 MiB
Speed: 61.63 MiB/s

Start: 2025-09-03 12:00
End: 2025-09-03 12:00

so other jobs are sowing anywhere betwwen 25 to about 80. MiB/s

I have a dedicated 10gb link directly connected between hosts for backup and replication.. i noticed the speeds were pretty slow.. the hosts are using local SSD but i would have thought i would get higher speeds on this.. they are using isolated ip adds so they only talk to each other... Am i missing something or can tweak anything to get higher speeds or is it the SSD causing the problem

MAny Thanks

ran it thru chatgpt.. and got this.. Perfect — now we have the real error.

The crash is because libfuse.so.2 is missing. XO (specifically the fuse-native module) depends on the FUSE library, but Debian 13 only ships libfuse3, not the older libfuse2 that XO wants.

i did bump the mem up to 8 as well and the repliaction job is now running...

@olivierlambert 4gb mem on XO on debian VM.... host have 64 gb each... is it worth bumping it up and giving it a reboot and try again.. as i say was working great for the last few days....

@olivierlambert

{
  "data": {
    "mode": "delta",
    "reportWhen": "always"
  },
  "id": "1756806348037",
  "jobId": "184411ba-b5db-41b4-8915-9b35d731ac77",
  "jobName": "Replication to HOST147",
  "message": "backup",
  "scheduleId": "28eb38ca-41b4-403e-b34e-92015d51207c",
  "start": 1756806348037,
  "status": "failure",
  "end": 1756806348278,
  "result": {
    "message": "worker exited with code 1 and signal null",
    "name": "Error",
    "stack": "Error: worker exited with code 1 and signal null\n    at ChildProcess.<anonymous> (file:///opt/xo/xo-builds/xen-orchestra-202509011824/@xen-orchestra/backups/runBackupWorker.mjs:24:48)\n    at ChildProcess.emit (node:events:519:28)\n    at ChildProcess.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202509011824/@xen-orchestra/log/configure.js:52:17)\n    at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)\n    at Process.callbackTrampoline (node:internal/async_hooks:130:17)"
  }
}

Hi Have a 2 node cluster with local ssd storage and have one host as master the other is used as a replication host.. they are directlymconnected via 10gb nics.. has been working perfectly the last few days since setting it up but last night i'm getting the above error.... no idea how to troubleshoot this... i'm on Xen Orchestra, commit c3905...hosts did 29 patch updates last night...

cheers