Please Ignore this post. It was a storage backend issue.

Adding @team-storage in the conversation

@florent yes they are, I screenshoted earlier in the thread

still having initial issue, even on latest XOA or XO CE

Restarting tool stack on master host of remote pool cleared the stuck job and backup was able run failed vms. Support ticket still open fyi.

Great job, worked perfectly! Thank you very much for your fast support!

Because doing an update without rebooting doesn't reload the updated main programs, like XAPI. A host in only updated after a full reboot.

@Pilow error reporting is a feature in itself . Thanks

@Pilow I will take a look in deep later, but the key/delta and disk usage is set during backup, even if they are merged during LTR retention

@Bastien-Nollet Great, thanks!

@Forza you will have to switch to LATEST to profit from end month release STABLE is one version behind LATEST both are production ready.

okay weird. Let's see if there's other reports then

I hope someone will reply to my post here about how to check status on this but I believe I've resolved the main issue: I disabled and re-enabled the whole task itself yesterday and it ran this morning as scheduled.

@henri9813 yes thank you for correcting my message

@MajorP93 200gb free space was enough in my production system to cause this. The only thing I didn't try was filling it up until I found the point where it started working.

I confirm that this is the current behaviour, as @pilow reported here https://xcp-ng.org/forum/post/99446 We might change it in the future to make it better, but it won't be trivial to change.

Thanks @Bastien-Nollet and @olivierlambert . I'm going to do some tests and write the results. Thank you so much.

@MajorP93 aha, yea. Per disk concurrency is important too.