Fatal error message

1

When doing backup I do get follwoing error message:

Fatal error
Duplicati.Library.Interface.UserInformationException: Found 28 files that are missing from the remote storage, please run repair
  at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x001aa] in <ae134c5a9abb455eb7f06c134d211773>:0 
  at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify (Duplicati.Library.Main.BackendManager backend, System.String protectedfile) [0x00066] in <ae134c5a9abb455eb7f06c134d211773>:0

What can I do? Running repair doesnt help as proposed. Dupliciti runs on xubuntu (Linux *** 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS

Thanks, Matthias

2

Hi @Matthias_Muhler, welcome to the forum!

Thanks for letting us know your system information, but we’ll need a little more info to make it easier to help you out:

  • What version of Duplicati you are using?
  • What destination type (Google Drive, SFTP, etc.) are you using?
  • What do you mean by “running repair doesn’t help”? Does it do nothing or do something but not fix anything?

Note that the 28 missing files means files that Duplicati expects to exist at the destination can’t be found. This could be due to a few different things including because they are actually missing or maybe because the list of files provided by the destination is somehow getting corrupted before it gets to Duplicati.

(By the way, I edited your post by adding “~~~” before and after the error message to make it easier to read.)

3

Thanks for replying

I do use: You are currently running Duplicati - 2.0.3.3_beta_2018-04-02

I do use an ftp connection to Hidrive from strato

I did try to repair the stuff by using Advance… Database … repair AND also recreate… No effect

I use this destination only for backuping and never acess directly. From my point of view I shouldn’t anywa manipulated the data on the destination side. But nobody knows.

Thanks,
Matthias

4

Thanks for the details.

The 2.0.3.3 beta version is the most stable right now, so that’s a good one to be using.

Normally a Repair would fix most issues with missing files, so it’s odd that it’s not for you. When you say Repair and Recreate both had “No effect” do you mean they ran but you still get the 28 missing files error message when trying to run a backup?

While I agree you shouldn’t normally directly manipulate the files at the destination, could you FTP in to Hidrive to confirm the 28 files Duplicati is reporting missing really are not there?

If they’re not then that would at least let us know Duplicati is doing what it should (warning of missing files). If they ARE there, then there’s something wrong with either Duplicati or the communications from the destination.

5

Yes, it means that I can run repair etc. but when running the Backup afterwards I still get the message that 28 files are missed (e.g. 25. Jul. 2018 09:53: Message Missing file: duplicati-ba71bef3cb8294ec9a58a87f5ba7fdfc2.dblock.zip.gpg).

After having ftped the server I cant find the files there; they are missed.

Also switching to webdav doesnt help although test connection gave positive result for ftp and webdav. Server can do either protocols.

6

The “Test connection” step is more of a “can we actually log in” test then a full “can we do sustained reads / writes” test - so it’s possible the destination or network connection involved my be able to handle short connections but have an issue with longer data transfers under one or the other protocol.

Since the missing files include dblock files that means some of your backed up data is now gone. Because Duplicati only backups up changes to files it relies on the existing backups to be valid - since they’re not, by default it won’t let you add more backups on top of a possibly incomplete “base”.

At this point your options are to:

  • run the database “Recreate (delete and repair)” step (easy to start but potentially VERY long running)

  • use the list-broken-files and purge-broken-files commands to see what files are affected and remove them from your backups (see below - this is likely the fastest way to get things going, plus you’ll know what backup files / versions were affected)

  • add a parameter that lets you ignore the error (definitely NOT recommended as restores may not be viable)

Here’s a guide on how to list and purge broken files:

7

ok. did this although using it worked only after deleting all filters by hand and the commandline arguments /home/*

It worked really quick baout 30 sec. It’s about 190 GB source data and about 150GB saved data.

Got following messeage:

No broken filesets found in database, checking for missing remote files
Listing remote folder …
Marked 28 remote files for deletion

Found no broken filesets, but 0 missing remote files
Return code: 100

Message is confusing to me since I would have expected that purge deletes the files not only markes them.

8

result of --purge-broken-file

Finished!

No broken filesets found in database, checking for missing remote files
Listing remote folder …
Marked 28 remote files for deletion

Found no broken filesets, but 0 missing remote files
Return code: 100

9

running Recreate (delete and repair) gives also the message at the end that 28 files are missing

10

Somehow the dblock files went missing from your destination but the dlist files that reference those dblock files don’t know that.

When database Recreate (or even Repair) is done it will use the dlist files if they are found so you end up recreating the database in it’s incorrect state.

I think you were close to getting it right though - the purge-broken-files correctly found missing files and flagged them as deleted so a database REPAIR (not recreate) should have then deleted them. (The Recreate just ignore the local “deleted” flag and rebuilt the database solely from the still-incorrect remote files.)

If that doesn’t work, another option is to move all the dlist files to a subfolder and run a repair, which should rebuild the moved dlist files based on the local database.

11

second suggestion did not work

after moving the dlist files to a subfolder (ftp access with Filzilla) I let run repair

Fatal error
Duplicati.Library.Interface.UserInformationException: Found 28 files that are missing from the remote storage, please run repair
at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x001aa] in :0
at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify (Duplicati.Library.Main.BackendManager backend, System.String protectedfile) [0x00066] in :0

first suggestion

first purge.brocken-files

No broken filesets found in database, checking for missing remote files
Listing remote folder …
Marked 28 remote files for deletion

Found no broken filesets, but 0 missing remote files
Return code: 100

afterwards in commandline tool

repair
Listing remote folder …
Repair cannot acquire 511 required blocks for volume duplicati-b62335f19e6e04a0da821aed2415d3cec.dblock.zip.gpg, 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-b62335f19e6e04a0da821aed2415d3cec.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 535 required blocks for volume duplicati-bc429989f02b24b0899bbee6678747470.dblock.zip.gpg, 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-bc429989f02b24b0899bbee6678747470.dblock.zip.gpg, message: Repair not possible, missing 535 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 535 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 cannot acquire 511 required blocks for volume duplicati-b975baf912743452dbd610dc206c6b22b.dblock.zip.gpg, 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-b975baf912743452dbd610dc206c6b22b.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b074e65dd91f746d89620e903c621c01a.dblock.zip.gpg, 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-b074e65dd91f746d89620e903c621c01a.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b49bdd198fc2647038b437f194a7b94c3.dblock.zip.gpg, 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-b49bdd198fc2647038b437f194a7b94c3.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b697dc4d3f0c24a578d68ebfbd02f5449.dblock.zip.gpg, 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-b697dc4d3f0c24a578d68ebfbd02f5449.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 512 required blocks for volume duplicati-b4fba0e117bab4f6f924c4c0f1135da81.dblock.zip.gpg, 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-b4fba0e117bab4f6f924c4c0f1135da81.dblock.zip.gpg, message: Repair not possible, missing 512 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 512 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 cannot acquire 536 required blocks for volume duplicati-b484d5b967c144f7ebf4c9e5ee3ac74aa.dblock.zip.gpg, 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-b484d5b967c144f7ebf4c9e5ee3ac74aa.dblock.zip.gpg, message: Repair not possible, missing 536 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 536 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 cannot acquire 517 required blocks for volume duplicati-be81fc603ce4c4127b0d2af77cf17000a.dblock.zip.gpg, 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-be81fc603ce4c4127b0d2af77cf17000a.dblock.zip.gpg, message: Repair not possible, missing 517 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 517 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 cannot acquire 568 required blocks for volume duplicati-ba6d70d2cadc244f79bf101b26453dbb7.dblock.zip.gpg, 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-ba6d70d2cadc244f79bf101b26453dbb7.dblock.zip.gpg, message: Repair not possible, missing 568 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 568 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 cannot acquire 511 required blocks for volume duplicati-b63681a1b7bb24420a4e31164e34530bd.dblock.zip.gpg, 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-b63681a1b7bb24420a4e31164e34530bd.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b6b0a4fbf4ba042178322c4b55f6d93a3.dblock.zip.gpg, 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-b6b0a4fbf4ba042178322c4b55f6d93a3.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-ba71bef3cb8294ec9a58a87f5ba7fdfc2.dblock.zip.gpg, 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-ba71bef3cb8294ec9a58a87f5ba7fdfc2.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-bac7576f2445541f2ad7f218111981969.dblock.zip.gpg, 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-bac7576f2445541f2ad7f218111981969.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-ba31c787e9c944b4c9db2a064bec1cb4e.dblock.zip.gpg, 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-ba31c787e9c944b4c9db2a064bec1cb4e.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 527 required blocks for volume duplicati-babe73d571dc54b9f96dcd75f65877c77.dblock.zip.gpg, 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-babe73d571dc54b9f96dcd75f65877c77.dblock.zip.gpg, message: Repair not possible, missing 527 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 527 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 cannot acquire 536 required blocks for volume duplicati-b664de906f6c8404ea6bc07a118be15ec.dblock.zip.gpg, 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-b664de906f6c8404ea6bc07a118be15ec.dblock.zip.gpg, message: Repair not possible, missing 536 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 536 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 cannot acquire 535 required blocks for volume duplicati-be63482db34814378becb442a202b418e.dblock.zip.gpg, 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-be63482db34814378becb442a202b418e.dblock.zip.gpg, message: Repair not possible, missing 535 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 535 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 cannot acquire 511 required blocks for volume duplicati-b521fe42b971544bf95d25c5a27e9a0e2.dblock.zip.gpg, 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-b521fe42b971544bf95d25c5a27e9a0e2.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b0004f23a0b48438081c6101e7b818f91.dblock.zip.gpg, 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-b0004f23a0b48438081c6101e7b818f91.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 537 required blocks for volume duplicati-bdcb8ef18ff034bf2b51dc836e3485b97.dblock.zip.gpg, 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-bdcb8ef18ff034bf2b51dc836e3485b97.dblock.zip.gpg, message: Repair not possible, missing 537 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 537 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 cannot acquire 511 required blocks for volume duplicati-b6db46e11e4d748ee8cf3977e56974360.dblock.zip.gpg, 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-b6db46e11e4d748ee8cf3977e56974360.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b4dc22c397fd742c6b1859ad8ba151b34.dblock.zip.gpg, 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-b4dc22c397fd742c6b1859ad8ba151b34.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 521 required blocks for volume duplicati-b03503c9317e64c31b3171c552f931d17.dblock.zip.gpg, 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-b03503c9317e64c31b3171c552f931d17.dblock.zip.gpg, message: Repair not possible, missing 521 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 521 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 cannot acquire 658 required blocks for volume duplicati-bd0f87dcacd5745739d6928f4ec0f3900.dblock.zip.gpg, 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-bd0f87dcacd5745739d6928f4ec0f3900.dblock.zip.gpg, message: Repair not possible, missing 658 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 658 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 cannot acquire 511 required blocks for volume duplicati-b680533ba63da44ffb062b284be3afb7f.dblock.zip.gpg, 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-b680533ba63da44ffb062b284be3afb7f.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b04cd527fe2a0461eb9b9f8037a69ebaa.dblock.zip.gpg, 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-b04cd527fe2a0461eb9b9f8037a69ebaa.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 cannot acquire 511 required blocks for volume duplicati-b046a972b99584cec83d8f16f5a812e6e.dblock.zip.gpg, 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-b046a972b99584cec83d8f16f5a812e6e.dblock.zip.gpg, message: Repair not possible, missing 511 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 511 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 did run repair again but same error message. It is like a circular references.

afterwards repair from the webbrowser based GUI

Fatal error
Duplicati.Library.Interface.UserInformationException: Found 28 files that are missing from the remote storage, please run repair
at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x001aa] in :0
at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify (Duplicati.Library.Main.BackendManager backend, System.String protectedfile) [0x00066] in :0

What about deleting the local database an the dlist files and let run repair? I use Dupliciti on on my mother’s laptop to run backup (Win 10) and it works. It is saved to the same hidrive but another subfolder.

12

That should do the trick BUT Duplicati will end up downloading the entire backup so it can rebuild the dlist information from the raw dblock files. If that bandwidth and likely-long run time aren’t an issue for you, then that should work.

You might want to move the dlist files instead of deleting them - just in case… :wink: