@andrewreid Not that this helps with your error, but my nightly S3 delta backups to Wasabi have been working just fine. I'm using XO source and keep mostly up to date with master.
S3 and NFS are different backup formats so NFS working does not mean S3 will work.
Sometimes Wasabi causes failures but not recently and not that last more than a few VMs in one night. The next backup run (manual restart or next nightly) seems to work correctly.
I force a full backup every 3 months just to make sure I have a good checkpoint in case undetected corruption creeps into the delta data. Plus I have replication and other backups.
I did have a problem once (not exactly yours) with a VM and just deleted the S3 backup data which forced a full backup again. Sucks because you don't have the weeks of deltas anymore.
Error #3 (date-time) is strange. May be a backblaze issue.
You could create a new S3 remote to backblaze (new bucket or directory) and test one failing VM backup to the new remote and see if it works (and works again for delta). You could set the retention low to test merge too. I have a setup like this with a local MinIO server for S3 testing and local backups.
@florent Looks like they're all during the transfer phase, usually it's this error:
EINVAL: invalid argument, open '/run/xo-proxy/mounts/fbd663b9-57f1-4610-ae32-3f1d69fea68d/xo-vm-backups/f92970cd-523f-3915-7254-5f0b4a37d713/vdis/1d5ddf64-2165-4d26-b05c-330546b48ee0/69786d14-81ea-446c-8870-e43dfedae766/20220622T050722Z.vhd'
I did have an HTTP time out last night for 8 / 12 VMs, but 4 backed up just fine which seems odd, the VM was up the whole time.
This is backing up over a proxy to a TrueNAS system local to the proxy, but my home backups also running over a proxy to an unRAID system are running fine.
I could be off the mark here, loving XCP-NG and XO so far though!