@Pilow Yeah i was looking over his script to see how he worked around it but just states that. I knew there would be limitations with it so i didnt add it to the main branch yet.

@florent In my case I have 4 backup jobs. 1 full, 2 delta (1 onsite, 1 offsite), 1 mirror. 106 VMs are being backed up by these jobs. In my case that setup clearly shows the RAM issue. I do not know if it can be replicated in a very small setup. Sometimes multiple backup jobs run at the same time. It appears that backup jobs running in parallel make the issue occur faster. @mathieura Thanks for the hint! I can imagine that this could possibly change something in this regard as I did not have any issues with this exact backup job configuration some time ago. The issues started to appear somewhere in december so it could be related to the XO6 release. I will try what you suggested and report back.

@DustinB The issue is lack of pool resources to have all prod machines up, if i can't join the new host withou update, i'll have to schedule some downtime.

@MichaelCropper Truenas on bare metal just as storage, XCP-NG is also bare metal on 3 hosts to make a pool. That's the minimum if you want to enable High Availability, it also works really well as a "normal" pool which is what I have. Rolling Pool functions are great, click the button and the system moves the VMS off of the host that need updates, reboots, moves VMs off of the next host, repeat. Only works with Shared storage.

If they can get Doom to run on a female healthcare product, I think we should work to get XCP-ng to work on said same product.... https://www.youtube.com/watch?v=V1gcoyo5Ssk haha...

said in Commit 109e376 Implications: we are currently drafting a procedure to make it the easiest possible. FYI: https://github.com/vatesfr/xen-orchestra/pull/9525 More details to come in upcoming weekS thomas-dkmt opened this pull request in vatesfr/xen-orchestra open docs(sdn_controller.md): document openssl 3 + sdn upgrade path #9525

@Danp alright, thanks. I'll give that a try.