Earlier quoted context omitted.
Any company that does the "unlimited*" shenanigans are automatically out from any selection process I had going, wherever they use it. It's a clear signal that the marketing/financial teams have taken over the businesses, and they'll be quick to offload you from the platform given the chance, and you'll have no recourse. Always prefer businesses who are upfront and honest about what they can offer their users, in a s…
Most home broadband providers offer unlimited network traffic.
Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
221–230 of 716 posts
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#222Exclusions are one thing, but I've had Backblaze _fail to restore a file_. I pay for unlimited history. I contacted the support asking WTF, "oh the file got deleted at some point, sorry for that", and they offered me 3 months of credits. I do not trust my Backblaze backups anymore.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#223Earlier quoted context omitted.
Git packs objects into pack-files on a regular basis. If it doesn't, check your configuration, or do it manually with 'git repack'.
I decided to look into this (git gc should also be doing this), and I think I figured out why it's such a consistent issue with git in particular. Running git gc does properly pack objects together and reduce inode count to something much more manageable. It's the same reason why the postgres autovacuum daemon tends to be borderline useless unless you retune it[0]: the defaults are barmy. git gc only runs if there's…
> git config --global gc.auto 1000
with the long option name, and no `=`.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#224Earlier quoted context omitted.
They offer "unlimited" where I live, not "unlimited*".
I mean, in this universe we live in everything is limited somehow. I do wish it was a word that had to be completely dropped from marketing/adverting. For example there is not unlimited storage, hell the visible universe has a storage limit. There is not unlimited upload and download speed, and what if when you start using more space they started exponentially slowing the speed you could access the storage? Unlimited…
Yes, indeed, most relevant in this case probably "time" and "bandwidth", put together, even if you saturate the line for a month, they won't throttle you, so for all intents and purposes, the "data cap" is unlimited (or more precise; there is no data cap).
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#225Earlier quoted context omitted.
This is a complexity that makes it harder, but not insurmountable. It would be reasonable to say that if you run the file sync in a mode that keeps everything locally, then Backblaze should be backing it up. Arguably they should even when not in that mode, but it'll churn files repeatedly as you stream files in and out of local storage with the cloud provider.
> Arguably they should even when not in that mode, but it'll churn files repeatedly as you stream files in and out of local storage with the cloud provider. When you have a couple terabytes of data in that drive, is it acceptable to cycle all that data and use all that bandwidth and wear down your SSD at the same time? Also, high number of small files is a problem for these services. I have a large font collection in…
I assume you don’t think that, so I’m curious, what would you propose positively?
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#226Earlier quoted context omitted.
Git packs objects into pack-files on a regular basis. If it doesn't, check your configuration, or do it manually with 'git repack'.
I decided to look into this (git gc should also be doing this), and I think I figured out why it's such a consistent issue with git in particular. Running git gc does properly pack objects together and reduce inode count to something much more manageable. It's the same reason why the postgres autovacuum daemon tends to be borderline useless unless you retune it[0]: the defaults are barmy. git gc only runs if there's…
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#227To the author: please use a darker font. Preferably black. I’m only in my 40’s, I don’t require glasses (yet) and I have to actively squint to read your site on mobile. Safari, iPhone. I’m pretty sure you’re under the permitted contrast levels under WCAG.
Re: Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others
#228I 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…
Why don't they charge by the Gigabyte