@florent It's been quiet since I supplied the json logs for the failed backup jobs. I understand this is a low priority case, and for myself I can continue having these failed backups, since I use other methods (especially for the Linux machines) to back up modified files of importance.
Has there been any progress in tracking what's happening here ?
Two different kind of failures since I reported:
Got a "failure" (but success) in other jobs.. To explain the "success" part of it, I can select the job when doing a restore, and the "transfer" is green but the "remote" is marked red.
[image: 1741003478991-xcp-ng-backup-fail-or-ok-admin-ubuntu.png]
... and the remote is OK ...
[image: 1741003521687-xcp-ng-backup-fail-or-ok-admin-ubuntu-remote-ok.png]
Restoring from this backup seems to be possible:
[image: 1741004632183-xcp-ng-backup-fail-or-ok-admin-ubuntu-restore-available.png]
The same happens with the previously mentioned "Win 10 22H2 new", backup gets a red blob on "remote", but green on "transfer" and restore is available from that point in time. This is against another remote, that get "full success" on other VMs.
Another example, against the same remote (as in the images above) with five jobs at the approximate same time (machines belongs to a backup sequence)
[image: 1741004104739-backup-2025-03-03-2x-success-followed-by-3x-failure-followed-by-1x-success.png]
The failures are identical:
[image: 1741004215619-backup-2025-03-03-failure-example.png]
If there is anything I can do to provide you with more details, explain what I should do to obtain the data you need, and if this problem is rare enough to never have happened (or will happen) to a real customer, then just close the case.
