The purge operation writes this:
The operation PurgeBrokenFiles has started
No broken filesets found in database, checking for missing remote files
Backend event: List - Started: ()
Listing remote folder …
Backend event: List - Completed: (3.58 KB)
Marked 1 remote files for deletion
Found no broken filesets, but 1 missing remote files. Purging from database.
Return code: 0
But the backup still has the above error.
BTW when I run the list-broken-files command for the first time, it run for days but never game any output. The CPU was as 100 % for one thread.
I restarted duplicati and after that if finished in seconds.
There are different tools for different purposes, but a Repair can fix some missing files, or if not, can announce which specific files are missing. Different types are fixed differently. From experiment, you possibly are missing a dindex or dlist file, which Repair can often replace from database records.
Missing dblock files lose actual data from source files, so any loss means some broken source files.
suggests that it’s not a missing dblock file, because that breaks files and so needs purge-broken-files.
Thanks for the reply
I did try purge files many times:
List files:
Marked 1 remote files for deletion
Found no broken filesets, but 1 missing remote files. Run purge-broken-files.
Purge files:
Marked 1 remote files for deletion
Found no broken filesets, but 1 missing remote files. Purging from database.
Return code: 0
Repair:
Repair cannot acquire 1108 required blocks for volume duplicati-b0bd96452efdb4f01b4ec66669e6dc9ce.dblock.zip, which are required by the following filesets:
This may be fixed by deleting the filesets and running repair again
Failed to perform cleanup for missing file: duplicati-b0bd96452efdb4f01b4ec66669e6dc9ce.dblock.zip, message: Repair not possible, missing 1108 blocks. If you want to continue working with the database, you can use the "list-broken-files" and "purge-broken-files" commands to purge the missing data from the database and the remote storage. => Repair not possible, missing 1108 blocks. If you want to continue working with the database, you can use the "list-broken-files" and "purge-broken-files" commands to purge the missing data from the database and the remote storage.
Return code: 0
I guess that there should have been some filesets after “:”.
Not particularly big. Are you trying to figure out how to post it? Can you post a link, e.g. from some cloud storage service that you use, or if you have none, perhaps from a sharing service such as WeTransfer?
It looks like you have this option set in your Advanced options. It influences Repair behavior. You could turn it off to see if Repair behaves differently (probably) and if it can clean up an issue (not sure about it).
Having a dblock file that’s missing yet breaks no source file backups is weird. I can force a situation that shows these symptoms by dropping a dblock file from some other backup into a backup, then Recreate. There’s then an extraneous dblock file in the DB, and deleting it from the destination leads to your issues (more or less), however yours likely arose differently. By the way, what is history before the issue arose?
is how topic opened, but doesn’t say if initial backup worked, many backups worked for awhile, and so on.
If initial backup failed, it couldn’t fail this way. Easiest path is clear destination and database, try again, take notes if necessary. Consider starting with a small backup to establish a base backup, then add more data.
If it’s an existing backup with valuable history, you could try a Database Recreate, but remote file situation is unclear. If progress bar gets to the 90% spot, it’s doing an exhaustive download looking for missing info.
Watching About → Show log → Live → Verbose during Recreate will show you what it’s doing at the time.
Thanks for the reply.
I did not notice that Storj account had no space left, that’s why the strange error.
After increasing space, repair or purge didn’t work but recreate did.
