@MathieuRA said: Hi, regarding your backups which do not appear on the XO5 restore page, I suggest you to open a new topic Forgot to include the link to the new topic https://xcp-ng.org/forum/topic/12040/restore-only-showing-1-vm

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

@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

@JSylvia007 Sorry, I'm really late to this thread, but note that backups can become problematic if the SR is something like 90% or more full. There needs to be some buffer for storage as part of the process. The fact you could copy/clone VMs means your SR is working OK, but backups are a different situation. If need be, you can always migrate VMs to other storage which is evidently what you ended up doing, which frees up extra disk space. Also backups are pretty intensive so make sure you have both enough CPU capacity and memory to handle the load. Finally. a defective SR will definitely cause issues if there are I/O errors, so watch your /var/log/SMlog for any such entries.

@Bastien-Nollet I'm running c1e5f btw

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

@User-cxs peut etre un clnflit IP ou la VM prenait l'IP du master... courage pour la suite !

Ping @Team-XO-Backend

@tsukraw No worries! Just glad that we can all help each other out!

@Pilow Thanks for the heads-up, you should be able to add back concurrency as it was before and get similar performance to before the refactoring.

@jerry1333 said: There is nothing else on that host and this is only host in pool but it's using 30% of cpu all the time? it's not using 30% of CPU, you see a graph of cumulated (switch is on) core consumption of your 32 cores. never switch this on. it adds up like that : 32x1%=32%, wrongfully letting you think you are at 30%ish CPU usage.

@Pilow open a dedicated topic on this . I will ping the relevant team there is it iscsi + CBT ?

@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

@Pilow perfect!

@TeddyAstie Attached is the output you requested xen-cpuid -p.txt

@dlgroep Thank you, we will take thin/thick token into account and use 'claims' part for other properties.

Come on everyone! Click Here to vote to support HP IPMI info in XO!

perhaps "in the context of a proceeding RPU, do not start halted VMs" ? or "boot only halted VMs that have HA enabled" ? but I can imagine corner cases where this is not wanted. some chicken & egg problem.