I know the post is talking about their personal backup product but it's the same company and so if they sneak in a reduction of service like this, as others have already commented, it erodes difficult-to-earn trust.
Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
71–80 of 716 posts
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#72Earlier quoted context omitted.
+1 Firefox users: press F9 or C-A-R
F9 doesn't seem to do anything for me on Linux... Neither on the posted page nor on HN. What is it supposed to do? There is no mention of F9 on this support page either: https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perf... Am I missing something?
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#73I guess the problem with Backblaze's business model with respect to Backblaze Personal is that it is "unlimited". They specifically exclude linux users because, well, we're nerds, r/datahoarders exists, and we have different ideas about what "unlimited" means. [1] This is another example in disguise of two people disagreeing about what "unlimited" means in the context of backup, even if they do claim to have "no rest…
Always prefer businesses who are upfront and honest about what they can offer their users, in a sustainable way.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#74That is the exact path to my Dropbox folder, and I presume if I move my Dropbox folder this xml file will be updated to point to the new location. The top of the xml file states "Mandatory Exclusions: editing this file DOES NOT DO ANYTHING".
.git files seem to still be backing up on my machine, although they are hidden by default in the web restore (you must open Filters and enable Show Hidden Files). I don't see an option to show hidden files/folders in the Backblaze Restore app.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#75On the topic of backing up data from cloud platforms such as Onedrive, I suspect this is stop the client machine from actively downloading 'files on demand' which are just pointers in explorer until you go to open them. If you've got huge amounts of files in Onedrive and the backup client starts downloading everyone of them (before it can reupload them again) you're going to run into problems. But ideally, they'd giv…
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#76Earlier quoted context omitted.
What are you using now? Asking for a friend
I have used Arq for way over a decade. It does incremental encrypted backups and supports a lot of storage providers. Also supports S3 object lock (to protect against ransomware). It’s awesome!
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#77Ironically drop box and one drive folders I can still somewhat understand as they are "backuped" in other ways (but potentially not reliable so I also understand why people do not like that). But .git? It does not mean you have it synced to GitHub or anything reliable? If you do anything then only backup the .git folder and not the checkout. But backing up the checkout and not the .git folder is crazy.
No they are not. This is explicitly addressed in the article itself.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#78Meanwhile, Backblaze still happily backups up the 100TB+ I have on various hard drives with my Mac Pro.
Does it? How do you know? If they start excluding random content (eg: .git) without effective notice, maybe they AREN'T backing up everything you think they are.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#79Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#80> My first troubling discovery was in 2025, when I made several errors then did a push -f to GitHub and blew away the git history for a half decade old repo. No data was lost, but the log of changes was. I know this is besides the point somewhat, but: Learn your tools people. The commit history could probably have been easily restored without involving any backup. The commits are not just instantly gone.
Indeed, the commits and blobs might even have still been available on the GitHub remote, I'm not sure they clean them on some interval or something, but bunch of stuff you "delete" from git still stays in the remote regardless of what you push.