I’ve been struggling with a corrupt backup for 3 months. The backup sets are go back several years, so I would like to keep those if I can instead of deleting and starting over from scratch.
About 3 months ago I got an errors on my backups that several files were missing from an older backup version. I tried repair database, rebuild files, recreate database, etc., but nothing worked. Ultimately, I deleted that backup version. Backups still failed with missing files on a different version. Same thing: repair, rebuild, recreate, ultimately delete.
BTW, the missing file errors are all similar to:
Remote file referenced as duplicati-bbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb5.dblock.zip.aes by duplicati-ixxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd0.dindex.zip.aes, but not found in list, registering a missing remote file
Again, same thing, missing files on yet a third backup. Repair, rebuild, try to delete. However, when I try to delete this version, I get the error: “Database file does not exist: /config/.config/Duplicati/68##################.sqlite”.
My databases are actually in /config/ (this errant backup is /config/AMxxxxxxxx.sqlite). However, when I run my delete command, it creates /config/.config/Duplicati/dbconfig.json, in which it sets Path to AM… and DatabasePath to 68…
What’s going on? Where did this numbered database originate? My databases are all letters, not all numbers. Most importantly, how do I salvage this backup? I don’t want to loose the previous years worth of backups because of some missing files from a few months ago, but I haven’t been able to backup for months because of the missing file errors. Why can’t Duplicati ignore these errors and continue new backups? If something is missing, fine, backup the existing files, but don’t fail all future backups because of 4 missing files from old backups. I don’t understand. Help!