Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

67 TB for 7867 USD - poor man's nearline storage ???

I wouldn't mind making two of these for storage...one mirror the other....
Although the drives being seagate...I worry a bit after the last article I read on them and the amount of issues I've had with them...so might change only that little bit...
 
I just had my main burly raid system crash after updating a few apps such as QT. Now my backup is giving me error -36 when I try to copy files. HD's suck.
 
Does anybody else here think that Gibson is spamming this board?

See his other post...
http://reduser.net/forum/showthread.php?t=35032

I can't help but note that he has earrings, bracelets and jewelry, but no rig specs or website. Maybe I'm wrong but I can't help but wonder why one would explain what a HDD is, in its most basic form on this board.

BTW, these systems are very heavy in size, but how about redundancy and speed? I don't see any mention of a hardware RAID controller which is certainly the faster way to go. I must admit I haven't looked much into port multipliers though. Read this... "to store or retrieve data with a Backblaze Storage Pod, it is always through HTTPS. There is no iSCSI, no NFS, no SQL, no Fibre Channel. " Thats why they're so cheap. Good for offline archiving but remember, you'd need two of them, in different locations and HTTP takes FOREVER to dump in the PetaByte range. I wouldn't mind one though ;)
 
As a service Backblaze wouldn't be very good for the amount of content that the average Red shooter can create.

As for the BB Pod Basically, you have 9 SATA ports that do not aggregate by themselves. You would have to very carefully carve out software RAID volumes such that the disks within a RAID set are on different controllers. The software RAID issue is not an issue here because the CPU in this server is dedicated to file serving and will easily have the bandwidth to do the job. I read somewhere that they get 25Gb/s of throughput, which is pretty good. Trouble is that you have to build it yourself, then you have to set up your network to be able to use it, mixing Linux into whatever OS you are doing now. Probably not a bad solution if you are a busy post production house, but a bit overkill for a shooter or small post house.

A better solution for what we do is probably an ATTO based solution. For Apple or PC you can get an ExpressSAS R380 which is a RAID card that has 8 SAS channels @ 3Gb/s each. You can drop this directly into your workstation and connect it to an external chassis with up to 8 5 SATA to 1 SAS channel backplane adapters, for a total of 40 drives. If you want the network solution you can buy a server from Apple of any PC vendor and connect it up the same way and share the files on your network. It will cost a bit more, but you do not have to be an IT guru to make it work as the building blocks are much bigger.

Cool product though...

Bob
 
I don't see how the back blaze pod can be practical for post production. It is a very good amount of space for a very good price... but... how do you connect that thing into your editing environment at a decent transfer speed?... gigabit ethernet does not seem decent enough IMHO.... and editing on that thing directly should not even be an option to consider.
 
You must log in or register to reply here.
Back
Top