We’ve been evaluating Duplicati for about 6 months and have run into an issue that hopefully a developer can answer. This issue is a duplicate of this question: Database disk image is malformed
After about 20-25 successful backups, Duplicati errors out with a SQLite constraint violation on BlockHashSize.
We removed the index and attempted to recreated it, but SQLite errors out with the same constraint violation. If we add VolumeID to the BlockHashSize index, or we just drop the index entirely, then backups seem to finish with no errors. However, without knowing what the logic behind the index was supposed to do, we are just guessing. We are hoping that a developer with knowledge of this index can chime in and help.
Should the VolumeID in the block table also be included in the index? It seems to me that if the VolumeID is the same thing as a backup set, then maybe for uniqueness, it should be added to the BlockSizeHash index. Can anyone confirm this?