says that, as of this run, you have two backups. The 73 RetryAttempts are concerning because you might have an upload problem, but it might be as simple as a timeout (see linked topic) needing setting of longer http-operation-timeout than the default 1:40. You uploaded 87281938315 bytes in about 16 hours (possibly having gaps, so math may be off), which means about 12 Mbits/second. Any idea what speed you expect?
Remote volume size looks like you left it at the default 50 MByte, which “should” finish well under 1:40, but maybe sometimes it doesn’t. Regardless, you might need to set up some logging to see what retries were.
About --> Show log --> Live --> Retry can see them (click error for details), or if that’s too tiring (intermittent issue), then log-file=<path> and log-file-log-level=retry will show them, with the exact reason detailed there.
Viewing the Duplicati Server Logs describes the live log, and also the Stored log where your error might be. Viewing the log files of a backup job often skips backup results log when backup fails, so check both spots. Possible you’ll find your “Could not find file” error there. If so, maybe you’ll find SpillCollectorProcess below. Setting it up again to watch with live log or log file is too much to ask at this time, but maybe log now exists.
Sorry to be so nosy about your Internet connection, but if it’s asymmetrical (many are faster on download), then that gives us more leeway to try things such as a database Recreate from the destination files, which typically is not a whole download but in bad cases it can be, depending on the condition of the backup files.
You’ve definitely got a database problem (internal consistency check failed), seem to have flaky uploading, and I’m not sure of a great way to tell the condition of the backup unless you want to approximate it using a Direct restore from backup files (which you can do from the same Duplicati by retyping some information), which might show whether you have a backup with timestamp of your last backup start. I suppose you can also just look at OneDrive, especially if you sort by date. Near its end should be a
dlist file with UTC date.