# Found XX files at the remote storage, but none that could be parsed

**URL:** <https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299>\
**Category:** Support\
**Created:** [April 19, 2026, 9:57am UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299 "2026-04-19T09:57:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![onurbi](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/o/b38774/32.png) [@onurbi](https://forum.duplicati.com/u/onurbi)\
**Post date:** [April 19, 2026, 9:57am UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/1 "2026-04-19T09:57:17Z")

</div>

Hi,  
after updating to [2.3.0.0 (Stable) 2026-04-14](https://forum.duplicati.com/t/release-2-3-0-0-stable-2026-04-14/22288) I am not able to backup anymore.

Trying to backup via my everytime successful cmd batch I got:

=\> The database was attempted repaired, but the repair did not complete. This database may be incomplete and the backup process cannot continue. You may delete the local database and attempt to repair it again.

Then I tried to repair and got the mentioned error message.

Then I added the option `--rebuild-missing-dblock-files=True` in my batch file.

Result:

> Backup started at 19.04.2026 12:13:58  
> Checking remote backup …  
> Listing remote folder …  
> Extra unknown file: duplicati-20260419T081923Z.dlist.zip  
> …
> 
> Missing file: duplicati-ba3eaf626292748efbf4e256093b1505b.dblock.zip  
> …
> 
> Die Operation Backup ist fehlgeschlagen =\> Found 8 remote files that are not recorded in local storage. This can be caused by having two backups sharing a destination folder which is not supported. It can also be caused by restoring an old database. If you are certain that only one backup uses the folder and you have the most updated version of the database, you can use repair to delete the unknown files.
> 
> ErrorID: ExtraRemoteFiles  
> Found 8 remote files that are not recorded in local storage. This can be caused by having two backups sharing a destination folder which is not supported. It can also be caused by restoring an old database. If you are certain that only one backup uses the folder and you have the most updated version of the database, you can use repair to delete the unknown files.

Reading similar postings did not help me.

My setup uses a local USB HDD.

Any ideas what next step helps?

Regards,

Onurbi

---

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [April 20, 2026, 1:49pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/2 "2026-04-20T13:49:15Z")

</div>

> [@onurbi](#):
>
> cmd batch

Do you specify `--dbpath` explicitly on the command? That makes it easier to

> [@onurbi](#):
>
> You may delete the local database and attempt to repair it again.
> 
> Then I tried to repair

So you didn’t delete local database first? If you need path, read [dbconfig.json](https://docs.duplicati.com/platform-specific-guides/using-duplicati-with-windows#using-the-cli).

> [@onurbi](#):
>
> Extra unknown file: duplicati-20260419T081923Z.dlist.zip

Some backup ran (time is UTC), but the database you’re in didn’t hear about it.

> [@onurbi](#):
>
> If you are certain that only one backup uses the folder

This is important. Are you certain of that? Did anything else change at upgrade?

---

<div class="post-metadata">

**Author:** ![onurbi](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/o/b38774/32.png) [@onurbi](https://forum.duplicati.com/u/onurbi)\
**Post date:** [April 20, 2026, 3:29pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/3 "2026-04-20T15:29:05Z")

</div>

> [@ts678](#):
>
> Do you specify `--dbpath` explicitly on the command?

Yes, I did.

> [@onurbi](#):
>
> You may delete the local database and attempt to repair it again.

I tried this with no success several times.

> [@ts678](#):
>
> So you didn’t delete local database first?

Yes I deleted it. Manually and via GUI.

> [@ts678](#):
>
> This is important. Are you certain of that?

Of course, and am sure.

To cut a long story short, I decided to discard the accumulated versions and started a new backup in a new directory. That worked.

But basically, the repair function should be able to regenerate a database on its own using just the existing ZIP files. Or did I overlook something?

---

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [April 20, 2026, 7:41pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/4 "2026-04-20T19:41:31Z")

</div>

> [@onurbi](#):
>
> But basically, the repair function should be able to regenerate a database on its own using just the existing ZIP files.

Not repair, but delete and repair should be able to do that from good destination.  
Destination can be broken (e.g. trash lots of files), so can have recreate failures.

Complaint about excess or missing files are comparison of DB to destination, so

> [@onurbi](#):
>
> Extra unknown file: duplicati-20260419T081923Z.dlist.zip

> [@onurbi](#):
>
> Missing file: duplicati-ba3eaf626292748efbf4e256093b1505b.dblock.zip

should not have been possible if the database had been deleted before a repair.

If problem is reproducible, one could look at file times and `dlist` UTC times to attempt to figure out what happened. Something touched DB or the Destination.

> [@onurbi](#):
>
> discard the accumulated versions and started a new backup in a new directory.

If that means the old backup was discarded, further research may be impossible.

In other oddities, the “none that could be parsed” message in title wasn’t detailed  
to say when it happened, but other output was puzzling enough. The source code

> <https://github.com/duplicati/duplicati/blob/a2b5721e6984ca6c5462fc597cb7c8de595b806e/Duplicati/Library/Main/Operation/RecreateDatabaseHandler.cs#L154-L188>

looks to me like it was looking at a folder without any of the usual duplicati files,  
all beginning with `duplicati`, then being `dblock`, `dindex`, or `dlist`, and at  
end being `.zip` and possibly `.aes` or `.gpg` after that. What it actually saw is  
recorded in the job database as a `list` entry, so possibly is still researchable.

The GUI is easiest way. Job → Log → Destination shows all the activities there.

> [@onurbi](#):
>
> My setup uses a local USB HDD.

These run the risk of drive letter assignment and maybe wrong files being seen.  
To me (maybe dev can say more), these are strange results, with little to look at.  
If you have enough left to try, we could, otherwise I’m just glad it’s running again.

---

<div class="post-metadata">

**Author:** ![onurbi](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/o/b38774/32.png) [@onurbi](https://forum.duplicati.com/u/onurbi)\
**Post date:** [April 20, 2026, 8:58pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/5 "2026-04-20T20:58:14Z")

</div>

> [@ts678](#):
>
> If that means the old backup was discarded, further research may be impossible

No, I saved the previous folder content. It is still available.

I could run some targeted tests using a new database name.

> [@ts678](#):
>
> These run the risk of drive letter assignment and maybe wrong files being seen

In principle, you’re right. In my case, however, the drive letter hasn’t changed.

> [@ts678](#):
>
> If you have enough left to try, we could

Yes if you have an idea how to approach the investigation.

---

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [April 20, 2026, 9:27pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/6 "2026-04-20T21:27:55Z")

</div>

> [@onurbi](#):
>
> Yes if you have an idea how to approach the investigation.

Try to make it fit the model. If it has knowledge of expected files, that strongly suggests there’s still a database around unless the code is tripping over itself.

`--log-file=<path>` and `--log-file-log-level=information` (or verbose, or even profiling which is huge) provide information showing destination files or more.

If an error comes up naming missing or extra a file, one could look over history of the file. If in GUI, you do that as I said for `list`, but an upload is a `put` operation, download is `get`, delete is `delete` and would be interesting for missing file error.

This can also be seen in the log, but if you don’t have one set up, database can do. Possibly it’s even in an old one you kept, but reproducing an issue might be easier.

Maybe the dev will show up at some point with further ideas on what went on there.

---

<div class="post-metadata">

**Author:** ![onurbi](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/o/b38774/32.png) [@onurbi](https://forum.duplicati.com/u/onurbi)\
**Post date:** [April 20, 2026, 10:03pm UTC](https://forum.duplicati.com/t/found-xx-files-at-the-remote-storage-but-none-that-could-be-parsed/22299/7 "2026-04-20T22:03:54Z")

</div>

I’ll give a try with the suggested log parameters tomorrow.
