Flaky connection to Backblaze

Hi!

My daily kopia snapshot verify --verify-files-percent=1 failed today for one of my 8 repos. 4 repos are stored locally on a hard drive. The other 4 are on Backblaze.

The error happened for the Backblaze repo:

ERROR error processing kopia@kopia:/mnt/source@2024-07-12 20:36:14 CEST/Kamera/blahblah/IMG_1651.jpg: error reading object 81b395c424ead2bf01f00cbb97ac722a: unable to open object 81b395c424ead2bf01f00cbb97ac722a: unexpected content error: error getting cached content from blob "p2adfb903313698128cad134edb15efb3-s37cb845dd12e8de412a": failed to get blob with ID p2adfb903313698128cad134edb15efb3-s37cb845dd12e8de412a: unable to complete GetBlob(p2adfb903313698128cad134edb15efb3-s37cb845dd12e8de412a,14736024,2736641) despite 10 retries: DownloadFileRangeByName: internal_error: incident id bf14856d5f89-e8ddfca8f68da5db

All other checks were successful. I just ran a verification manually and it failed again for another file with the same error. Then I located that file in the web UI and successfully downloaded/restored it. So my guess is, nothing is broken or corrupted in the end. I guess the connection to Backblaze is just flaky. I never had these problems before since I built this backup solution (like 9 months ago).

Unfortunately my Backblaze account stores everything in the US because I misclicked when creating the account. I am living in Europe. I suspect it might contribute to the issue.

Did anyone have any of these problems? What would you suggest to do?

If you are using native B2 connectivity try to connect using S3. Or vice versa.

I’ll first wait for some days to see if the issue persists and then test your suggestion. Also this issue reminded me that the data is stored in the US. I might switch to Hetzner’s S3 storage once it’s released.

I think it was released yesterday.

From my experience S3 is the best option for kopia.

1 Like

Great, I just have applied for the beta :slight_smile:

Let us know how it works