Bioteam why you should never build a backblaze pod q mart gas station


The backblaze pod is essentially a stripped down 4U storage server with internal space for 45 internal disk drives (and a single OS disk). At 3TB per drive you can get 135 terabytes of raw capacity into a single storage “pod”. gas in oil Backblaze says their hardware costs are a little over $7,000 for this configuration but as we will show in a future post this is not exactly realistic for others who wish to follow in their footsteps. As a low-volume customer, our actual cost for building a single 135TB pod was roughly $12,000 USD.

Backblaze has apparently realized, however, that the actual “secret sauce” in their infrastructure is not the hardware … it’s the internally developed “cloud storage” software layer they use to tie all their pods into a highly-available and easy to manage system. You will note that Backblaze does not speak in detail about their software practices! Why you should never build a backblaze pod

Simply put this box has no “highly available” features and any sort of significant maintenance on it will almost certainly require the system to be taken offline and possibly even powered down. electricity use estimator You also need to mount this unit on extremely heavy-duty rack rails OR put it on a shelf and leave about 12 inches of top clearance free if you want to easily be able to pop the top cover off to get at the drives.

Short answer: They solve all reliability, availability and operational concerns by operating a bunch of pods simultaneously with a proprietary cloud software layer that handles data movement and multi-pod data replication. To them, a storage pod is a single FRU (field replaceable unit) and they don’t really need to spend significant amount of time and attention on any single pod.

• Backblaze does not care about operational burden. electricity generation in usa Via their custom software and use of many pods at once Backblaze has built an infrastructure that requires very little effort in the datacenter. gaz 67 It looks like a few days a week are spent deploying new pods and I’m guessing that failing pods are “drained” of data and then pulled out to be totally rebuilt or refreshed. Backblaze does not have to dink around trying to debug single-drive failures within individual pods.

Great posts. gas oil ratio for weed eater We just built one of these (by built I mean bought from Protocase and filled it with drives) because the cost of enterprise SAN storage is ridiculous. For comparison the cost to build 4 of these filled with drives is still less than the chassis alone with some other vendors (not named on purpose) before you even get into drives and licensing.

Other things of note – this is really meant to be filled up with disks upon building. As mentioned there are a bunch of screws and a cover to remove before you can get at the drives so you really don’t want to “add drives to it later” if you can avoid it. Also as mentioned you will probably want to add another NIC in the chassis for link aggregation or at the very least to separate management from storage interfaces.

These are great when used appropriately but in a business environment it is really difficult to justify some of the short comings – especially the drive accessibility – unless you are doing what backblaze did which is to build so many of these that no single entity is critical. That is not to say the concept is wrong – I just mean that spending extra money on a Supermicro chassis (like this one with accessible drive bays and redundant power may get you more bang for your buck in the long run.

Overall this is a great project if, as others have stated, you have the right use case for it. 9gag instagram I would recommend this for home/personal use (think media library) and for non-production business use cases – or at least non-critical applications like archive storage. In business production I would want at least redundant power supplies and accessible drive bays.