tl;dr - Backblaze announced at one point they’ve stopped backing up files associated with sync services like OneDrive. The author discovered they also don’t back up
.gitfolders.Which, yeah - the second your backup solution starts getting picky with what to backup, it’s time to move on. Shame, I had heard a lot of good things about them.
Not backing up
.gitfolders is criminal. Backblaze should know better. That’s literally the most valuable data in the folder!Nothing wrong wth BackBlaze as a storage solution. Just switch backup programs.
I use Duplicati with BackBlaze B2. Works very well for me.
Seems like a good workaround to me!
it’s time to move on
Anybody has any suggestions for an alternative?
I’m using restic and targeting Wasabi S3 for the backend. It’s not super user friendly, but it’s cheap.
I’ve been using restic as well, but with Backblaze B2. So technically this issue doesn’t affect me, but they’re on thin ice so I might switch to another S3 provider. What made you go with Wasabi?
I was looking for off-site back options and S3 seemed to play nice with restic (I had been backing up to my NAS).
Wasabi was interesting because they charged a flat fee pert TB and don’t charge for egress (when I have to restore).
They’ve been rock solid for a few years now, in addition to restic backups, I’m using them for my terraform state file storage and a static site hosting https://stronk.bond/.
I’m setting my homepage to stronk.bond
I wonder if the file pointers instead of actual files is a technical hurdle. (OneDrive/dropbox).
But it really needs to be communicated to users, not just “hopefully you notice at some point, also we put it on our blog”.
Especially git. That’s not a lot of data.
I have never trusted when I had to use both backup software and backup storage from the same company. I always thought it would lead to abuses like this.
So I use a third-party backup software - I have had great success with Duplicati - and back that up to BackBlaze B2.


