Note, I had a bit of a screwup and never got around trying to resolve it… so I had a backup job that was last updated Feb 2020, and then something happened, there was an error with the DB, and we all know that Duplicati doesn’t try to auto-repair those.
Cynicism aside, I (now) went to try and do a repair… no luck. So I went to do a rebuild. It takes about 6 days to do a rebuild (not 100% sure why, there’s 18 versions, ~180GB of backed up data, and some people have much larger backups/more versions and it runs faster).
Upon finishing rebuilding, and usually I come back to it simply telling me that database repair failed to complete. But after 3 more rebuild attempts, I finally caught it. VerifyConsistency
(called in the RecreateDatabaseHandler
) fails with “Found inconsistency in the following files while validating database: <file, actual size ##, dbsize ##, blocksetid: ##> (2 files). Run repair to fix it”.
I went to run repair and it failed with “Failed to repair, after repair 1 blocklisthashes were missing”.
I’ve tried to dive into the SQL and figure out why repair can’t repair the DB, but it’s over my head (never was very good with SQL). What is something I can do, hints on maybe what code I should try to poke, in an effort to repair this without spending another 6 day rebuild process that will end in failure. I’ve already looked at the code and saw that repair/rebuild functions have not been touched between the latest beta and the latest canary, so unless there’s something I missed, I don’t see anything improving by running something newer.
Ideas? I am capable of code changes to run temporarily-modified libraries, but am not good with SQL.
Windows 10 x64 (Version 1909)
ServerVersionName : - 2.0.5.1_beta_2020-01-18
BaseVersionName : 2.0.3.3_beta_2018-04-02
CLRVersion : 4.0.30319.42000
CLROSInfo : {“Platform”:“Win32NT”,“ServicePack”:"",“Version”:“10.0.18363.0”,“VersionString”:“Microsoft Windows NT 10.0.18363.0”}