PatrickVogeli Wrote:uuuuh the backblaze looks awesome. However, I've come across this: http://www.bioteam.net/2011/08/why-you-s...blaze-pod/
It's an interesting point of view.
Thanks for the link, that was an interesting read.
He recommends getting the thing from protocase, assembled, but the mark-up there is quiet a bit. Even on the backplanes, the markup is quite high. Obviously it wouldn't be a solution for me, over here - but even if I was living in North America, I would think twice about it.
Also, the makers of the backplanes also have a barebone system for a lot cheaper, if you don't have access to a fabricator and so forth.
The Cons:
Quote:The system uses a single disk for hosting the operating system
I was thinking of using a small SSD. A single disk is fine, in my instance, because I'll be using FlexRaid and on there you can't include the OS anyway.
Quote:The system requires 2 power supplies to operate, both must be active and there is no redundancy, spare or failover unit
I thought about that, the two power supply yoke. But I don't think I'd, as a home user, sanely be able to incorporate otherwise.
Quote:The system has no hardware RAID capability
For myself, and my media system going over 20TB now, I think a software one will suffice a lot better than the absence of anything (which I have now).
Quote:The system only has 2 GigE network interfaces
To access/replace a disk drive you need to remove 12 screws
To access/replace a disk drive you need to remove the top cover
If you build this yourself totally DIY you will be required to create custom wiring harnesses
Any monitoring or health status reporting tools will have to be built, installed and configured by hand
For a media server, I'm not sure most of the rest matters. The poster of that blog does indicate that:
Quote:Backblaze has an unusual duty cycle. A normal backblaze pod is only “active” for the first few weeks of it’s life as it slowly fills to capacity with customer backup data. After a pod is “full” the system sits essentially idle while it waits for (much less frequent) client restore requests.
I think that be similar to my duty cycle as well. At least as far as writing is concerned. Then it be idle until it's requested to be read.
Now I can't pretend I fully understand all the elements of this, I'm very much a novice. But I figure if I can get a machine going with at least 24 drives...I'll be happy. With 24 drives, I think I can come close to getting away with 1 nice PSU.
Of course, I'm easily likely to be wrong. When I actually get it together, I'll do some sort of post on it, so others can improve on my many mistakes and errors.
I think, this weekend, I'm going to go and maybe CAD up my own design based off a tower I have at my parent's, and take it to the man down the road and see if I can't just "double" it. See how much in steel v aluminium it costs me