Hello,
I know it is strictly related to selfhosting but I don't have a reddit account so please bear with me. I've been using a Blackblaze B2 bucket as the storage for my restic backup for my whole homelab for a while and recently when reading from that bucket it is so so so so so so slow and unreliable (a lot of unexpected EOF and interruption). I've tested this on several machines (including a VPS on Hetzer) and I can access other sites just fine. Their status page says nothing and I wonder is it just me or do some of you also experience the same thing ?
Also any alternative recommendation is welcome but I can not selfhost my S3 at the moment :(
Thank you very much!
Edit: this is the log for my restic check --read-data (something similar on Hetzner VPS).
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
Load(<data/ef0e80ecc6>, 541, 6322304) returned error, retrying after 508.096097ms: unexpected EOF
Load(<data/ef0e80ecc6>, 541, 6322304) operation successful after 1 retries
Load(<data/c10459132f>, 535, 14002087) returned error, retrying after 1.352882596s: unexpected EOF
Load(<data/c10459132f>, 535, 14002087) operation successful after 1 retries
Load(<data/44089c2105>, 536, 10041504) returned error, retrying after 1.094099947s: unexpected EOF
Load(<data/44089c2105>, 536, 10041504) operation successful after 1 retries
Load(<data/c10459132f>, 481, 3262415) returned error, retrying after 1.418694544s: unexpected EOF
Load(<data/927e700367>, 467, 7776453) returned error, retrying after 634.119689ms: unexpected EOF
Load(<data/927e700367>, 473, 7798234) returned error, retrying after 849.03055ms: unexpected EOF
Load(<data/927e700367>, 467, 7776453) returned error, retrying after 1.243622488s: unexpected EOF
Load(<data/653ef7abb0>, 523, 8280899) returned error, retrying after 578.669152ms: unexpected EOF
Load(<data/fd9edf4117>, 533, 485866) returned error, retrying after 823.382046ms: unexpected EOF
Load(<data/c10459132f>, 528, 3248055) returned error, retrying after 1.402372952s: unexpected EOF
Load(<data/c10459132f>, 524, 3175555) returned error, retrying after 1.425799941s: unexpected EOF
Load(<data/9b179c749d>, 534, 13802701) returned error, retrying after 1.234603672s: unexpected EOF
Load(<data/7b827c96f6>, 531, 8412866) returned error, retrying after 1.49579899s: unexpected EOF
Load(<data/ef0e80ecc6>, 530, 5093059) returned error, retrying after 1.405885227s: unexpected EOF
Load(<data/927e700367>, 409, 7763564) returned error, retrying after 798.04783ms: unexpected EOF
Load(<data/c10459132f>, 481, 3262415) returned error, retrying after 1.362966862s: unexpected EOF
Load(<data/653ef7abb0>, 523, 8280899) returned error, retrying after 2.966804822s: unexpected EOF
Load(<data/927e700367>, 467, 7776453) operation successful after 2 retries
Load(<data/fd9edf4117>, 533, 485866) operation successful after 1 retries
Load(<data/927e700367>, 409, 7763564) operation successful after 1 retries
Load(<data/9b179c749d>, 534, 13802701) operation successful after 1 retries
Load(<data/c10459132f>, 528, 3248055) operation successful after 1 retries
...
Edit: After a day my restic check --read-data finished with no data corruption but it took a lot of retrying, even 7 retries to read the correct data :/ So I guess it is a sign for me to move to somewhere else.
Thank you for your reply :D To be honest I am thinking about setting up a new bucket as well but I can not move the data out because it will takes forever
Did you reach out to support with this? If so what was the experience?
I also backup to Bb, not had issues so far.
I did but they said that no issue on their end :/ In my case backing up to B2 is good as well but checking the backup (re-read data from there) is so unreliable
I recently had a local issue where I could barely reach B2 as well. It turned out that one of their endpoints was on a DNS blocklist I use. Once I manually unblocked that everything started to work again. Not saying you're having the same issue but it could be a lot of things between you and B2, careful triage is needed to find the root cause.
I don't think it is my end tbh because I ran the exact same thing on a Hetzner VPS and had similar issue so ...