Welcome to the forum @sudorand
It hardly counts since it’s so rare for me (and networks do odd things sometimes) but
Log data:
2023-11-30 07:25:00 -05 - [Error-Duplicati.Library.Main.Operation.TestHandler-FailedToProcessFile]: Failed to process file duplicati-b3587c0b3b216416eb5749e3e2f3203bf.dblock.zip.aes
System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
at Duplicati.Library.Main.BackendManager.GetForTesting(String remotename, Int64 size, String hash)
at Duplicati.Library.Main.Operation.TestHandler.DoRun(Int64 samples, LocalTestDatabase db, BackendManager backend)
is in my Gmail, for “Received an unexpected EOF or 0 bytes from the transport stream.”
Searching for that in Google shows AI Overview of some possible causes and solutions.
Can’t totally agree.
compared to
I wouldn’t call it fine (it survived only by retries), but it did better than the run that failed.
number-of-retries (and related settings) can be changed, but it’s better to fix cause.
One statistic doesn’t break down retries on upload and download, and it doesn’t show distribution. To actually fail, one needs to exceed retries for a given operation (in a row).
Seeing exact non-fatal retry spots can be done, e.g. if you option up custom log-file.
It’s a sample, weighted towards files that were verified fewer times (so often new ones).
Advanced options backup-test-samples and backup-test-percentage set the size.
The TEST command can do manual runs. Easier than true CLI is in GUI Commandline.
In true CLI, you can use the below with destination URL from Export As Command-line.
BackendTool is good if you want full control to specify the operation and the file it uses.
BackendTester is good for an automated test. Modify the URL to test in an empty folder.