When you get these (you posted two examples), are they the 0-byte files you were getting before?
Duplicati depends on the storage not losing its backup. Lost dblock files mean a damaged backup.
Previously you had tried WebDAV, and attempted SMB to Bitrix24. Did these files see any of that?
Your error messages look like they’re from a log file. What log level? If warning, look for prior ones.
This might save you the trouble of having to check files by hand. Another way to scan seems to be
list-broken-files which seems able to be able to quickly compare files against the size in its records.
To be certain that a file is broken, get it and try to decrypt it. Also try a good one to test the method.
AES Crypt is GUI, and easier than Duplicati’s CLI SharpAESCrypt.exe. If file is empty, don’t bother.
“First” meaning the oldest one you can find in the Restore dropdown? That’s bad. Is this issue old?
For dblock files, the backup file is the only copy. Repair can fix missing dindex and dlist from DB info.
There’s no button, but you remove broken backup files, then purge broken source files from backup.
but really what you need is storage that works reliably, if the storage is still giving you corrupted files.
I “think” it seems to check size first. Regardless, I don’t think it continues on with further checking later.
There are other times when it’s just looking at a file size listing, and of course those can’t hash content.
I think by default there’s a file listing and check before the backup unless no-backend-verification is on.