Is this behavior and its messages written up anywhere? I assume the issue isn’t on cancel but on restart. Ordinarily an interrupted backup is supposed to pick up where it left off, but maybe the initial is different…
How does Duplicati Resume After Interruption?
Irritating error message These two say what’s supposed to happen, and below proposes why it does not:
Warning Message after Backup describes a suspected bug with improper parameters fed in by the code.
Despite synthetic filelist failure, resume does often work. People confuse file scanning with a re-upload…
This is all somewhat past the original topic which wanted initial backup to be repairable, but didn’t discuss why a repair was necessary or why interruption happened. Ideally I’d think interruption should only be from things like having to take a laptop and go, and should just pick up where it left off when next backup starts.