I think that's why he says right at the beginning:
This device is that cheap because it cuts
several corners. That's okay for them. But
for general purpose this creates problems.
I want to share my concerns just to show you,
that you can't compare this to a X4540 device.As to speed, nothing you do is going to reduce a disk's low latency so talking about bandwidth is mostly a waste of time. Device bandwidth is rarely the limitation once you start to scale, because you can add devices to your network faster than you can build a better network.
If you believed their spin presumably you would buy from a proper enterprise company like IBM or EDC - not some failed workstation vendor.
That said, it's still really expensive if you're willing to go that extra mile and design your own system for your needs. And it's really not that hard.
They just got 'cheap', reliable comes at the expense of using multiple of these units and fast looks like it is going to be impossible without striping across multiple setups like this.
Interesting for an extremely narrow use case (long tail storage, think backup services, video sites, photo sites).
Outside of that maybe useable with some adaptation but not 'as is', besides that it is not as though their machines are up for sale, the figures they quote are mostly after all the r&d is already factored out, if you had to do this for a one-off, just cutting and folding that case would cost a pretty penny.
I'm fairly sure there is a market for a device that is a more robust version of this.
Probably at a 50% or so premium compared to the one they showed you could get a wider spectrum of uses and a bit more robust construction.
I would have bought one three months ago, now I had to settle for 20T or so in one 4U box, for a price a little over half of what they quoted in the article.
How do you know when I'll need my backup?
Replication is what it is all about.
Right upto the point where they are sold to a database company that isn't interested in selling disks.
the nice thing about the blaze is that if seagate decide to double their prices or much you to a new expensive platform - you just buy toshiba instead.
I see Backblaze will learn a lot from building their storage systems and future versions may be much better, but this one cuts too many corners for me to feel confident it will have the same kind of reliability I would recommend.
What amazes me most is the use of desktop-grade hard drives. Not because they are sloppily built, but because their performance requirements are so different from a server environment.
This makes for some nice reading: http://cacm.acm.org/magazines/2009/6/28493-hard-disk-drives-...
Me, I would add more cache at the same time. SATA tends to be really good for sequential, but be really, really bad for random. multiple sequential streams hitting the same disk start to look an awful lot like random access after a while.
No, it probably means that they get their reliability at a different level, such as simply storing the data on a number of machines. Systems like glusterfs make this completely transparant.
Agreed, but I do know a few situations where it is being used, the 'stack' has been undressed to the minimum and tested to the hilt before deployment.
Still, I would not risk my company on it. I've been a big fan of their architecture from pretty much day 1, but so far they seem to be feature oriented and not stability oriented.
From the numbers he cited I got the impression that the drives they are using would fail 3+ times more often than enterprise drives (lower MTTF + speced at low temps). The cost of replacing the drives (even if they are 1/2 the price) would make the system uneconomical.
Also: because of their case design (non-hot-swappable) the cost of human replacement is higher too.
Thus they must have a low usage rate to have a low failure rate for their system to make business sense.
They're primarily write-only, only when a customer retrieves their data does stuff get read.
If they spin down the drives when the volume is not being accessed the mttf for a single drive goes up a lot, possibly beyond the point where it matters.
That, and the fact that the company seems to be struggling to get sales.
But you will have to manage the cycles for redundancy, lifetime and power savings. The software to do it must be really clever.
He's concentrating on disk-to-board throughput, but this being network attached storage on a LAN, using the motherboards' single ethernet port the amount of data read or written to those drives per second will never exceed 1 Gbit/second anyway.
I agree with the reliability analysis though, backblaze seems to be on fairly thin ice there.
Still, it seems to work for backblaze, I'm taking it as read that they've lived through a bunch of drive failures by now and they seem to still be in business.