Thanks everyone for the precise feedback, it was really helpful! And thanks @florent for the fix

@AlexD2006 thanks for signaling this, we just merged a fix, that fix it on our labs can you test it on your side ? https://github.com/vatesfr/xen-orchestra/pull/9202 fbeauchamp opened this pull request in vatesfr/xen-orchestra closed fix(backups): getOldEntries must accept entries without id or timestamp #9202

@Bastien-Nollet Hi, here is the feedback : having two sequences for two schedules keeps the chain continuity and is to be considered working as two enabled schedules on one backup job. [image: 1762957808514-997d8a65-c99f-43de-94a2-60626c90abc1-49bee6ce-d965-46b4-b686-3fd5a07e24e9.png] Todays backup was indeed a delta, and did the healthcheck as intended. Question is answered !

@Bastien-Nollet I'm not a big fan of the way it is implemented right now : when you make a mirror copy, it first duplicate all the points then prune to the desired retention but if you keep this way of handling mirror copies, it has the advantage of not needing to handle incomplete chains ?

@Bastien-Nollet nice !

@MajorP93 the config should be in ~/.config/xo-server/ of the user running xo-server It is noted

@florent turning off CBT removed the "fall back" message but my Delta backup is still doing full backups.

\o/

@planedrop yes

@florent They are set to 30GB, but thinned provisioned, so they might be a less than that.

I worked around this issue by changing my full backup job to "delta backup" and enabling "force full backup" in the schedule options. Delta backup seems more reliable as of now. Looking forward to a fix as Zstd compression is an appealing feature of the full backup method.

I had to disable Purge snapshot data when using CBT. Backups are not longer defaulting to full backups.

Just connect your XOA to your dedicated network and it will flow to it.

@olivierlambert Host started and issue resolved.

Question for @pierrebrunet I assume

@olivierlambert Thanks that worked. Kind of obvious approach, still didn't try that

Are you sure the job isn't already running, as per the error message?

Backup job still failing. I have open a support ticket - Ticket#7746281