Multiple errors leading to inability to backup (filesetentry and inconsistency)

Support
1

hi everyone,

I have recently updated to 2.3.0.0 and successfully ran one backup (at least, I think I did); on the next one, I encountered the same error from this thread: Detected 7 file(s) in FilesetEntry without corresponding FileLookup entry

After getting that error consistently, I tried to delete e recreate the backup database as suggested in the thread and that generated a new error (alas also removing the previous logs).

The new error is:

2026-04-29 14:32:58 +02 - [Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError]: Fatal error
DatabaseInconsistencyException: Found inconsistency in the following files while validating database: 
XXXX, actual size 0, dbsize 196, blocksetid: 51338
XXXX, actual size 0, dbsize 196, blocksetid: 51338
XXXX, actual size 0, dbsize 196, blocksetid: 51338
XXXX, actual size 0, dbsize 196, blocksetid: 51338
XXXX, actual size 0, dbsize 196, blocksetid: 51338
... and 7521 more. Run repair to fix it.

Trying to repair also does not work (same error) and I have deleted and recreated the database numerous time.

One interesting thing is that the first 5 files that visibile in the logs, are all 0B empty files locally, I’m not sure about the 7521 more as the logs do not show the rest of the paths.

I also tried to restore that same folder and I got a warning (Active uploads detected, but no cleanup was performed. Run the "repair" command to clean up the incomplete files) and these 4 errors:

2026-04-29 14:50:04 +02 - [Error-Duplicati.Library.Main.Operation.Restore.VolumeDownloader-DownloadError]: Error during download
FileMissingException: The specified blob does not exist.
RequestId:e451955b-001e-0072-01d6-d7d29c000000
Time:2026-04-29T12:50:04.7865264Z
Status: 404 (The specified blob does not exist.)
ErrorCode: BlobNotFound

Content:
<?xml version="1.0" encoding="utf-8"?><Error><Code>BlobNotFound</Code><Message>The specified blob does not exist.
RequestId:e451955b-001e-0072-01d6-d7d29c000000
Time:2026-04-29T12:50:04.7865264Z</Message></Error>

Headers:
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: xxxxx
x-ms-client-request-id: xxxxx
x-ms-version: 2025-05-05
x-ms-error-code: BlobNotFound
Date: Wed, 29 Apr 2026 12:50:04 GMT
Content-Length: 215
Content-Type: application/xml

---

2026-04-29 14:50:05 +02 - [Error-Duplicati.Library.Main.Operation.Restore.BlockManager-BlockCountError]: Block count in SleepableDictionarys block table is not zero: 5
First 10 blocks: 3925072, 3122187, 3122320, 3122381

---

2026-04-29 14:50:05 +02 - [Error-Duplicati.Library.Main.Operation.Restore.BlockManager-VolumeCountError]: Volume count in SleepableDictionarys volume table is not zero: 5
First 10 volumes: 1541, 10934

---

2026-04-29 14:50:05 +02 - [Error-Duplicati.Library.Main.Controller-FailedOperation]: The operation Restore has failed
FileMissingException: The specified blob does not exist.
RequestId:xxxxx
Time:2026-04-29T12:50:04.7865264Z
Status: 404 (The specified blob does not exist.)
ErrorCode: BlobNotFound

Content:
<?xml version="1.0" encoding="utf-8"?><Error><Code>BlobNotFound</Code><Message>The specified blob does not exist.
RequestId:xxxx
Time:2026-04-29T12:50:04.7865264Z</Message></Error>

Headers:
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: xxxx
x-ms-client-request-id: xxxx
x-ms-version: 2025-05-05
x-ms-error-code: BlobNotFound
Date: Wed, 29 Apr 2026 12:50:04 GMT
Content-Length: 215
Content-Type: application/xml

It may have to do with Azure Blob as backend not being able to manage empty objects, but it seemed to be working well until now.

Can you please help? I’m stuck and I feel quite unsafe not being able to backup anymore.

Thank you.

2

GitHub issue for reference: Empty files cause restore to fail from Azure Blob storage and fail all backups after db recreate · Issue #6877 · duplicati/duplicati · GitHub

3

Hi @unosd, welcome to the forum :waving_hand:

That one is caused by zero-byte files, and only occurs after rebuilding the database.
The fix was included in 2.3.0.1.

You need to recreate the database when running 2.3.0.1 and the error goes away.

4

thank you, @kenkendk ! that’s the only thing I have not tried :slight_smile: . I did repair on 2.3.0.0 and 2.3.0.1, delete and recreate several times on 2.3.0.0, but never delete and recreate on 2.3.0.1! you can tell I’m not a professional tester. I’ll run it now.

5

Hi @kenkendk, not sure if I should create a separate thread given it may be unrelated, but I’m now getting a different error recreating the DB on 2.3.0.1:

2026-05-03 08:45:55 +02 - [Error-Duplicati.Library.Main.Operation.RecreateDatabaseHandler-IndexFileProcessingFailed]: Failed to process index file: duplicati-i5a2d814826ac4146ae0a81fdb34c82d3.dindex.zip.aes
InvalidDataException: Invalid JSON, expected "PropertyName", but got EndObject,

Not realy sure how to proceed from here, could you please help? Thanks

6

That means the JSON inside the file is somehow corrupted.

If you can get that file and then decrypt it, I would be very interested in getting a copy so I can dissect it and maybe figure out how that can be possible.

I would also recommend running a RAM test on the machine just to rule out a potential faulty memory chip.

A quick-fix would be to move the file outside the folder and then running the repair command. It will, most likely, be slower as some data needs to be found with probing, but at least continue.

7

thank you so much for the help; I got the file and tried to decrypt with:

 < duplicati-i5a2d814826ac4146ae0a81fdb34c82d3.dindex.zip.aes | openssl enc -d -a -aes256 -pass "pass:<MY ENC PASSWD>"

I got “error reading input file”, can you please let me know how to decrypt it so I can share it?

also

openssl enc -d -aes-256 -k '<MY ENC PASSWD>' -in duplicati-i5a2d814826ac4146ae0a81fdb34c82d3.dindex.zip.aes -out un_encrypted.data

and got “bad magic number”

I’ll start the repair now and see how it goes. Thanks again.

8

You need to use AESCrypt, and Duplicati ships a version of it you can use:

Essentially:

duplicati-aescrypt d <password> <encrypted file> <plain-text file>
9

thank you for the explanation, so the manifest file contains:

{
  "Version": 2,
  "Created": "20260429T120745Z",
  "Encoding": "utf8",
  "Blocksize": 102400,
  "BlockHash": "SHA256",
  "FileHash": "SHA256",
  "AppVersion": "2.3.0.1"
}

The vol/duplicati-b35761f16031144ef85d750ece98ca62e.dblock.zip.aes file:

{"blocks":[]}

hope that helps.

I deleted that file from Azure Blob Storage, ran the repair and it worked, thank you so much!

I will do a RAM test and let you know if my memory is to blame for the corruption.