@Pilow Yes NFS on vm storage and on backup storage. All vms are now on qcow2 except for the windows vm what was vhd. However i just mirgrated it over to qcow2. the Nics in all systems are the intel 10gb either x520 or x540

@gregbinsd let us know. If you do use my script. It pulls nodejs from NodeSource so it may not install the latest 24.15.0 tls. If you specific 24.15.0 it will install that version. If you need to change node version with my script use the rebuild option.

@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

@Pilow I did check this and it definitely completes within the hour. I am testing a lesser value for CR retention to see if this resolves it.

@abudef I don't know. I forwarded the question.

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