Hi, I have a question that I believe is similar to dohraeme-san’s, at https://forum.duplicati.com/t/corrupt-database-unable-to-run-new-backup/14270; and my intention is to get a general answer that can be included in the tutorial in the future, because it seemed to me to be a serious fault of the tutorial to omit itself on the subject. The problem: In case of accidental shutdown, as it happened in my first backup, in fact, in the first 10 minutes of it, the backup was corrupted – obvious – But after that, the interface ( GUI, in Linux Mint 20 Una, and it was a backup of almost a Terabyte, but it had only run 1 Giga, approximately ) But after the corruption, the interface stopped working, and only provided a button to repair the corrupted files ( 4, according to the system, and I even opened the partition to check that it was the same ), there is no option to simply discard the copy, there was only the option to repair, but it didn’t perform the repair, and in the end, I had to discard everything and reconfigure the backup, almost I had to reinstall from scratch! This is normal ? Because it seemed to me to be a weakness that there is not a simple option to discard the current session, since it is a “banal failure”, as we say in my branch (audits), that is, a failure that, however unlikely it may be, sooner or later later will occur, given enough time and attempts. And banal failures require previous solutions (we call them “foreseen solutions”, something made for an unavoidable unforeseen event).
The serious problem in itself, is that Duplicati did not perform the repair of the corrupted files, and was in a limbo where it did not perform any more operations. It just kept repeating a warning that there were corrupted files, but it didn’t actually fix them (does this happen in case of initial copy corruption?), and there was no simple option to discard the whole set…