@hannes Full backup interval (and Force full backup in the schedule settings) forces the job to do a full export of the disk and not a delta based on a previous one.

It is not impacted by the retention as XO will always makes sure every chain has at least a full export at the beginning so that all backups are viable.

Which means you will have multiple full backups, always one at the beginning, and, those that have been triggered by the settings above.

You should probably be able to fix this issue by installing the ntfs-3g package.

As you mentioned you're running it on a Synology, you can do that in DSM by opening Docker -> Container -> Select your container -> Details -> Terminal and enter the below in the console.

apk update apk add ntfs-3g

Let us know if it helped.

I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!

@olivierlambert i have created config.httpInactivityTimeout.toml in /opt/xen-orchestra/packages/xo-server with the content from above. Not sure how i can check if thats actually set.

BTW: this is not a CR Backup Problem, i also dont see Tasks running for my "normal" Backup Job. I cant check "how far" the actual Backup runs and if that differs.

https://github.com/vatesfr/xen-orchestra/pull/6315

Rajaa-BARHTAOUI created this issue in vatesfr/xen-orchestra closed fix(xo-web/tasks): tasks with no bound objects not displayed #6315

Since the update I have run full backup that have taken over an hour to complete due to their size and many smaller delta backups and the error has not come up again. I assume whatever was causing the error was fixed in the xo-server 5.84.2 update.

Sure, please keep us posted on your experiments 🙂 If it's a bug, we'll have more info to be able to work on it!

@nraynaud yes i use nfs today. But would love to send it to the cloud somewhere as well.

Answered on the XO forum, thank you 🙂