@Pilow Was already configured... [image: 1776435633046-screenshot-2026-04-17-102001.png] [image: 1776435658482-screenshot-2026-04-17-102051.png] Think this is the issue.... Network tab under pool. [image: 1776435710669-screenshot-2026-04-17-102135.png] Will run another delta once the current one finishes.

@MajorP93 I am not sure of which branch. can you switch to https://github.com/vatesfr/xen-orchestra/pull/9725 then when running this branch : wait for the memory to fill find the process running xo ( dist/cli.mjs ) send signal : kill -SIGUSR2 a file is created in `/tmp/xo-server-${process.pid}-${Date.now()}.heapsnapshot` Note that these exports can contain sensitive data. This will freeze you xo from a few seconds to 2 minutes, and the memory consumption after will be higher after, but this will be very usefull to identify exactly what is leaking The file will be a few hundred MB fbeauchamp opened this pull request in vatesfr/xen-orchestra open Fix(xo-server): TLSSocket memory leak — stoppable + http-server-plus incompatibility #9725

@McHenry said: Thanks. The old snapshots are being removed as the total never increases beyond 16, so when a new snapshot is added, the old one is removed. immediatly removed, yes, but then Garbage collection takes place. and perhaps with 19x16 GC to process it can't be done in one hour, and then next CR is launched, etc etc...

@Bytevenidos That's an interesting way of doing this, I'll have to remember it. I think the Fuel Ignition tool has a vhd output, it also produces both ignition and combustion parts for you. Worked pretty good on one test machine, but I need to go deeper into some of the other choices you can type in.

@stormi said: This is not exposed in Xen Orchestra yet. When will it likely be available in the GUI?

@ataxyanetwork I managed to install XOA (Current version: 6.2.2 - XOA build: 20251219) and did some more testing. I am experiencing the same issue when trying to restore from an existing backup. When I create a new backup job, I can perform a filelevel restore without any problems. However, when I rerun the job, I am no longer able to restore from the most recent backup. It only works with the initial backup. Can you also reproduce this ?