@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

@Pilow Agree.... have to be sure that garbage collection is completed or it'll never catch up if backups continue to be run without the coalesce completing.

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

@dinhngtu You rock - thank you!

@cobordism said: yum update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates It's currently in testing and will move to updates if everything (not only nut) is ok: yum install --disablerepo=* \ --enablerepo=xcp-ng-base,xcp-ng-updates,xcp-ng-testing nut

@Bastien-Nollet I'm running c1e5f btw

Thank you for your feedback @kratos !

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

@simonp patched tonight, a job who took 3 hours yesterday took only 1 tonight. so, big improvment ! need to re up concurrency to 2 or 4 on some jobs to see if I can squeeze more time on the backup window

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

But thank you for your time all the same.