Index files missing after backup

Support
1

Hi

Just tried the latest 2.0.4.16, and is having a strange issue

After a backup to jottacloud with 4 threads async upload, all looks good, but when running the backup again (without any change to the fileset) I get this in my log:

it looks to my list the backup uploads all the dblocks, but does not create index files, until next run.

trying the backup for a 3th time it runs without having to recreate any index files. only after new data have been uploaded to the jottacloud.

    1. mar 2019 13:58: Re-creating missing index file for duplicati-b3b85f0ed72ea4acc9cfa7112237476c1.dblock.zip.aes
    1. mar 2019 13:58: Backend event: Put - Started: duplicati-i16914fe34a9443ffb0beea6148160bb9.dindex.zip.aes (35,14 KB)
    1. mar 2019 13:58: Backend event: Put - Completed: duplicati-i28da47a4bd7649ec9be67c9e2e036e31.dindex.zip.aes (35,12 KB)
    1. mar 2019 13:58: Re-creating missing index file for duplicati-bda7bf59b4d7c470cb6f83ba67b98fafe.dblock.zip.aes
    1. mar 2019 13:58: Backend event: Put - Started: duplicati-i28da47a4bd7649ec9be67c9e2e036e31.dindex.zip.aes (35,12 KB)
    1. mar 2019 13:57: Re-creating missing index file for duplicati-bd4254e5fc1614e45ad2999fa6cfb171e.dblock.zip.aes
    1. mar 2019 13:57: Re-creating missing index file for duplicati-bd9ce4095c7fb4387942c146589e16978.dblock.zip.aes
    1. mar 2019 13:57: Backend event: List - Completed: (54 bytes)
    1. mar 2019 13:57: Backend event: List - Started: ()
2

Just reverted back to .15, and here it uploads 1 dblock and 1 index file.

where .16 did upload many dblock and only 1 index file

3

I am unable to reproduce this using version 2.0.4.16 with 4 upload threads. After an initial backup, I see multiple dblock, dlist, and dindex files in Jottacloud. Same thing after subsequent backups.

Was this a new or existing backup? Do you have any other advanced options configured?

4

Hi

Just upgraded again to check, and I still get this missing index files.

Backup jobs are new.

ADV settings:
–send-mail-to=“dahl@XXX.dk”
–send-mail-from=“dahl@XXX.dk”
–send-mail-url=smtps://smtp.gmail.com:465
–send-mail-username=“vera.alert@XXX.dk”
–send-mail-password=“XXX”
–send-mail-level=“Warning,Error,Fatal”
–thread-priority=normal
–asynchronous-upload-limit=4
–use-block-cache=true
–asynchronous-concurrent-upload-limit=4
–synchronous-upload=false
–dblock-size=100MB
–send-http-url=https://www.duplicati-monitoring.com/log/XXX
–disable-module=console-password-input
–exclude="/@Recycle*/"
–exclude="/.streams*/"
–exclude=“NoBackup/”
–exclude="**/@Recently-Snapshot*/"

5

Hi

Just testet on my workstation Windows 10, ADV setting only for SMTP reports, nothing else, and no problem with missing index files, with small files in backup (added like 5mb to backup), but after backing up an 350mb file, then I got missing index files on next backup.

Please try to recreate by backing up a 350+MB file, and doing a second backup afterwords.

6

I’ll try and reproduce later when I have a chance.

Are you able to see if the index files actually exist on Jottacloud? I believe the change to the Jottacloud backend code only affects the downloads, and not the uploads. It’s possible that Duplicati thinks that the files aren’t there, when they actually are.

7

Hi, got the same problem here…

8

Ok, I was able to reproduce this with the larger source file. I created a GitHub issue below. Thanks for reporting this.

9

I just noticed that my biggest backup set (movie collection) has been running for the past 6 days now, “re-creating missing index” over and over, and none of my other backup jobs have run during that time. I’m still on the 2.0.4.16 canary. Is there a way to gracefully recover here?