How to investigate multiple recurring warnings

Support
1

I keep getting warnings on nearly every backup. When I do a repair I get warnings, and when I delete and repair I get warnings.

How can I investigate this to find the root cause?

I am running Duplicati 2.2.0.3 stable on Kubuntu 25.10.

The most common warning I get is: Found 1 faulty index files, repairing now

I also got warnings after a repair that it didn’t delete an empty index file because it was too large.

And after a delete and repair I got these warnings:

  • 2026-01-10 08:38:24 +00 - [Warning-Duplicati.Library.Main.Operation.RecreateDatabaseHandler-MissingFileDetected]: Remote file referenced as duplicati-be44e6f3412884e53b338830489b452c5.dblock.zip.aes by duplicati-idaaef6c402f64ee6ba6e54267bc6c21b.dindex.zip.aes, but not found in list, registering a missing remote file

  • 2026-01-10 08:39:01 +00 - [Warning-Duplicati.Library.Main.Operation.RecreateDatabaseHandler-MissingFileDetected]: Remote file referenced as duplicati-bca560c1d693548bc92e29df1b8f7ad29.dblock.zip.aes by duplicati-ie9c6de8005c44100891e4f9afee58a3e.dindex.zip.aes, but not found in list, registering a missing remote file

  • 2026-01-10 08:40:01 +00 - [Warning-Duplicati.Library.Main.Database.LocalRecreateDatabase-MissingVolumesDetected]: Replaced blocks for 2 missing volumes; there are now 2 missing volumes

  • 2026-01-10 11:47:40 +00 - [Warning-Duplicati.Library.Main.Database.LocalRecreateDatabase-MissingVolumesDetected]: Replaced blocks for 2 missing volumes; there are now 0 missing volumes

Where should l look for index files and what tests should I run to find out what keeps tripping up Duplicati?

2

Are you talking about code cause? Are you a developer?

Even for those, it’s usually a long tough analysis journey.

Other times, it’s a new message added. GitHub can help.
Start with message, find the code change, find the notes.

Far easier is error search, e.g. search tool in forum found:

2.1.1.100 > Found 1 faulty index files, repairing now

I’m not sure I like the “fixed over time” recurring warnings.

I’m also not completely convinced that slow fixing gets all.
File test is sampled, so new files can reduce old file fixes.
.
Read further in above topic for how one can force full test.
The fix is done by the test, but you have to test all dindex.

Recording the actual message can help in your searches.
Forum can’t do phrase search, but Google and others do.
Sometimes one gets many hits, so lots to read. I’ll stop at:

Release: 2.1.0.119 (Canary) 2025-05-29

which explains the situation, links to the change, suggests improvement.
I don’t know the developer’s thinking, but you can look inside the dindex.

Decrypt with AES Crypt or duplicati-aescrypt, then describe content.
Proper content should be a manifest and vol folder with dblock name.
There’s not actually a dblock there, but that’s the index for the dblock file.

If the dblock that a dindex claims to index doesn’t exist, you get warnings
like in your delete and repair. Such dindex are probably not helping things
and can be deleted (or relocated, to be extra careful), however it’s always
possible that a dblock went missing, so I guess a note of it may be useful.

In backup. The file names contains dindex. There are also dblock.

I think I addressed everything. The test command is the most automatic fix.
Looking inside dindex files to check content and broken references is manual.

There are several things that the developer could consider changing in all this.
One cleanup causes recurring warnings and delays getting to fast DB recreate.
Another cleanup seems conservative (maybe rightly so) with large dindex case.
Third cleanup needs manual dindex removal when dblock for dindex is missing.