I’ve been using Duplicati version 2.1.0.5_stable_2025-03-04 for backing up my main desktop workstation since December and it’s worked fine. I have a server with a 2TB SCSI 0 pair, configured as a virtual backup folder in CasaOS, which is running Debian 13.2. I have my desktop running Samba and have been doing backups over the network.
The other day I was working when a kernel update for my desktop came through and completely messed up the file system. After I got it back working (by using fsck on the affected partition (my OS drive - of course!)), I installed and ran Timeshift. I do daily backups with both, using different configs. Timeshift has a bunch of folders it backs up (to a drive other than my OS drive), and I have Duplicati backing up other folders and data that Timeshift doesn’t.
Last night I took a look at my Duplicati backups and there were none that errored before the downtime, and every one since my desktop came back up errored. I also noticed that I had been keeping every backup since I installed and configured Duplicati, so I set it only keep the last 10 days. I also noticed that my Timeshift folder where I have it storing all my Timeshift data was in the backup, it was over 7 gigs, so I excluded it due to redundancy. Then did a backup with the new config, which ran for a while and it was late, so I let it go and went to sleep. Today I took a look at Duplicati and it had errored. Duplicati was complaining about the database needing repair.
I then went into the Database and selected repair, which failed quickly. Subsequent searches suggested I try delete database then repair, which I tried and it failed. The error message was: “Found 18 files at the remote storage, but none that could be parsed.” Then I went into the remote storage on the server and searched for any files not ending in dblock, dlist, or dindex. Actually I have them zipped, so the suffix is dblock.zip, etc. There were quite a few 1638 to be exact, but nothing out of the ordinary, so I tried to run list-broken-files with Commanline arguments as –full-result, and removed the exclude filters. This returned: “The operation ListBrokenFiles has failed with error: Cannot continue because the database is marked as being under repair, but does not have broken files. => Cannot continue because the database is marked as being under repair, but does not have broken files.“ Error code 100. I’m not sure where to go from here. I’m not sure where to go from here. Hopefully I just need to run a command line function with the proper arguments? I’m not opposed to deleting all the files I currently have in my Backups directory on the server, redoing my config and starting over, but I consider that a last alternative. Any help is greatly appreciated.