Are there any plans to expand to other datacenters? What happens if there is a disaster there? Is everything gone? Does backblaze backup it's own data?
Say if I wanted to make sure my data was stored in 2 regions, and was OK with a slight increase in cost to accomplish that.
However, for my main dev computer, I would totally pay another $5USD to replicate it to another location. I don't think that needs to complicate the pricing that much. You're essentially just paying for another backup, except it's the same computer in a different location.
Another question, any plans for coming to Linux?
Even if Backblaze replicated your backup in different locations, that only protects against their data center being destroyed. You will still lose your data if the app silently stopped working or your account gets deleted across all data centers, etc.
If you really want multiple locations, then I think you should use a 2nd backup service entirely to remove that single point of failure (Backblaze itself).
While unlikely there are other threats. You could have a disgruntled or mentally unbalanced employee. All eggs in one basket (whatever the basket and how robust it is) is always a potential problem.
To me the way to deal with this threat would be to spread backups over two vendors even if backblaze decides to open other data centers as Yev has indicated in his comment.
The recent S3 outage was caused by a typo. You can plan around natural disasters and all sorts of things, but the vast majority of the time, data loss is caused by humans. Diversify where that data lives. We would never recommend that you should ONLY keep your backup in Backblaze. We should be part of your solution.
> We would never recommend that you should ONLY keep your backup in Backblaze
I am guessing (I haven't thoroughly checked so I could be wrong) that your marketing materials don't make this fact known in an obvious way. No issue with that but I think many non business users might not think of it this way.
As for the charging for geo-redundancy, it's something we've considered, but at least for now we like "clean" pricing where it's the same across the board. Might change in the future, but nothing to report now.
Too early to speak to the uptime or support, but I'm pretty optimistic given what I've seen thus far.
Each time a very thorough post with good set of data to generate statistics from.
I use Linux on all of my machines, so I couldn't use the personal backup setup that they have.
LOL, that is NOT the prevailing wisdom around the office :P We do have an integrations page, I just pulled the first one I could think of. More info here -> https://www.backblaze.com/b2/integrations.html
Just curious, was there any consideration given to existing storage solutions like Ceph when you were evaluating writing your own erasure encoding system?
It seems like it may have been a potential good fit at one point in time, and might have made it easier to expose an S3-like API if you wanted to down the road.
We already have -> https://www.backblaze.com/b2/cloud-storage.html! Vaults was one of the reasons why we could build out ourB2 Cloud Storage service. We considered a lot of of options, but rolling our own fit with our culture :)
I work on very-low-latency products (sub-sub-msec) and we have only been able to mitigate this, never fully solve it.