Slashdot Mirror

← Back to Stories (view on slashdot.org)

Large Scale Solid State Memory Storage?

Posted by Cliff on from the terabytes-and-petabytes dept.

spacechicken asks: "I am doing a theoretical study of an extremely secure large scale data storage concept. Due to the nature of the (theoretical) location of the (theoretical) warehouse some of our constraints include very few (if any) service visits, complete remote administration and no moving parts. Does anyone have any experience using or information on large scale (on the order of 10^12 - 10^15 bytes) deployment of solid state storage? And to preempt those who will say it - I have Googled."

1 of 76 comments (clear)

  1. Ok, what about other problems? by Klaruz · · Score: 5, Informative

    Using solid state drives you could probobly do it on the order of about a half billion dollars. Possible indeed. But there are other things you haven't thought of. You didn't say if you need to have this thing on 24/7, but I'm going to assume you do.

    1: Power. Solid state drives tend to forget stuff when shut off, so you'll need a UPS in the data center to handle it. No biggie, except when you realize that the batteries are going to need maintence. They do go bad after a while, I know of no batteries that don't. In theory you could do flash memory instead of volitile for about 3 times the cost (512meg ATA flash storage is $300 on pricewatch, add raid, san, etc, pricey but possible)

    2: Cooling. Massive amounts of solid state chips are going to generate massive amounts of heat. This means water chillers (most likely) and fans. Both involve moters. Moters go bad. You can build redundent, but eventually both cooling systems will go out.

    3: The hardware it's self. CPUs go bad, controllers blow up, ram chips go out, power supplies blow, etc. You can only leave a redundant system alone for so long until it's no longer redundant.

    4: Acts of god. Floods, fire, lack of fuel for power, emi. These things happen. You can build two data centers in seperate locations and write one off when something bad happens, but then you're back to no redundancy.

    5: Murphy's law. Don't forget, Murphy always wins.

    Having worked on a LARGE scale redundent system (Think uncle sam), I can tell you these things do require maintence. Building a system that large without bugs that creep up in a few years time is going to be next to impossible.

    That said, it sounds neat. Let me know when you guys need an engineer to build it, it'd be fun.