I don’t think you have presented enough information to reach any conclusion.
The test that occurs after backup samples files, trying to sample them evenly.
If it finds FaultyIndexFiles, it fixes those (we hope), but hasn’t seen any other.
You could make a log-file at information level to see if the same dindex
file is repeatedly deleted and reuploaded after a backup. That’d be wrong, but
dindex files are not critical. They’re small files that say where blocks are in the
dblock files. If a block is missing, dblock files are searched, so recreate slows.
Forum search in top right corner above has several developer comments, e.g.
2.1.1.100 > Found 1 faulty index files, repairing now
There is also a way there to deeply inspect all the dindex files, if you want that.