B2_download_file_by_name did not return headers


#1

Hi,

I did setup a Backblaze account and tried to setup again my local repository. I did delete the old .duplicacy folder because it already had all settings and progress for an Onedrive account.

I did init the new Backblaze and started backing up. That’s when I started having some messages that are unclear to show me if my backup will be completed. Backblaze charges for traffic and this initial upload will take days. I would like to correct any issues before having to maybe reupload everything.

Please see output below:

Repository set to /mnt/sdc1
Storage set to b2://Home-Duplicacy-Backup
Reading the environment variable DUPLICACY_BACKBLAZE1_B2_ID
Reading the environment variable DUPLICACY_BACKBLAZE1_B2_KEY
Reading the environment variable DUPLICACY_BACKBLAZE1_B2_ID
Reading the environment variable DUPLICACY_BACKBLAZE1_B2_KEY
URL request ‘HEAD https://f001.backblazeb2.com/file/Home-Duplicacy-Backup/nesting’ returned status c
ode 404
b2_download_file_by_name did not return headers
Chunk read levels: [1], write level: 1
Compression level: 100
Average chunk size: 4194304
Maximum chunk size: 16777216
Minimum chunk size: 1048576
Chunk seed: 6475706c6963616379
top: /mnt/sdc1, quick: true, tag:
Downloading latest revision for snapshot home1
Listing revisions for snapshot home1
No previous backup found
Indexing /mnt/sdc1

Listing …

Failed to locate incomplete snapshot: open /mnt/sdc1/.duplicacy/incomplete: no such file or director
y
Listing all chunks
Listing chunks/
Packing aline/S8/20180717_163130.mp4
Use 10 uploading threads
URL request ‘HEAD https://f001.backblazeb2.com/file/Home-Duplicacy-Backup/chunks/e3/b5145aecc5f975a3
37fdcbfba8304233682d576beb2a29a77eb757e29edc0a’ returned status code 404
b2_download_file_by_name did not return headers

So, i am receiving many 404 because it seems that Duplicacy is having some issue invoking the Backblaze API. Just would like to know if this is normal due the verbosity that I enabled.

Many thanks,


#2

This is normal. It just checks whether the chunk is available before uploading it.

You don’t need to run with high verbose logging, unless you are triaging an issue.