Duplicati Database Recreate running for a week

What is the position? I would guess it’s at bad news last 10% where it’s hard to notice tiny motion.

What does the message around the numbers say? The final three 10% on progress bar are below:

If it’s the last of the three blocklist volume steps (please check), it’s going to look at all not yet read.
This doesn’t guarantee that missing data it’s searching hard for will be found, but one never knows.

I wrote a Python script that looks at dlist (says which blocks are needed) and dindex (location) files, attempting to forecast gaps that would cause dblock file search. As files are encrypted, decrypt first, however decrypting dblock files is only needed if we get more ambitious in investigating block issue.

This won’t directly solve the recreate, but it might give a clue as to the situation in a fairly small time. Attempting to look at things that go wrong is also a useful step towards changes meant to avoid that.

This does need a successful database recreate. If you just wanted restore, some other options exist.