Slashdot Mirror
Escape from Data Alcatraz
nihilist_1137 writes "Zdnet is reporting on a new information facility that is built to surive the worst.Triangular in shape, two of the sides house offices while the third, a large rectangular block if taken in isolation, contains two data centres, as well as the infrastructure to ensure that Web sites continue to function come fire, flood, natural catastrophy or foreign invasion."
"Remember thealamo.com!"
Seriously, though... you're saying they can stand up to repeated shelling by artillery? Or infantry-placed demo charges? Or anything else an invading force is likely to have?
WHY????
If you're being invaded, you've got more important things to worry about than if your company's web site will stay up!
The other half of this is: What if the invasion is an invasion of illegal immigrant workers? Can this thing survive having a janitor who's been slipped a hundred bucks (three weeks pay) to pull out a wire here and there?
If we all die from nuclear fallout who will reboot the NT servers?
Remember that you are unique, just like everybody else.
Never Underestimate The Power Of Human Stupidity.
Trapped in Time... Surrounded by Evil... Low on Gas.
At first this seems almost like a joke. Who would invest this much time and energy into such a fortress just to house data? Well... banks for one. Imagine banks from around the world storing their data here in a highly encrypted form, updated at least daily. it would require alot of bandwith to say the least, but wouldn't that security be worth it to investors?
Less crucial information that needn't be updated regularly could find a home here at a discounted price. Take for example, building plans. Every city, county, and State in America has a plan somewhere for every building its ever built that lists (among other things) the locations of all wiring and plumbing. This isn't terribly confidential information (though it very well may become so for large buildings with a realistic threat of terrorist attacks) and could be modestly encrypted with read access only granted to the owner.
Copyright owners might be interested in it as a way of saving back-ups of their paper-work that cannot be destroyed by some freak accident.
I for one don't like these ideas because they represent too many eggs in one basket. When information security is required, it is my personal belief that having it stored in a known location that every hacker in the world would drool over to get inside is a bad idea. History has shown, however, that not everyone (indeed few people) listen to me.
Slackware forever. Honestly, what else would you trust when it absolutely positively has to be stable, secure, and easy
Remember the Maginot Line? Impregnable? How easy was it to get around that? Data is useful in direct proportion to its accessibility - cut the connections into this place and it's toast. No frontal attack necessary.
:)
Also, the article says they can expand capacity 300%. Frankly, that sounds like pretty short-term planning to me. In my experience, it's a rare data store that doesn't double in size every year or two.
Still, it sounds like a cool place, and probably has a better climate than Sealand
This isn't as much "normalization" as it is "don't take so many drugs when you're designing tables."
By far, the cheapest and most effective method of redundant systems is to just safe your money and not buy fancy equipment for one place, but to spend it on cheap equipment is several places. That way, who cares if someone takes out an entire hosting center, leaving only a 100 ft dep crater. You still have servers running in California and Asia.
The Domain Name System doesn't rely on a huge Fort Knox-like system. It simply has 13 (?) different places throughout the world where amazingly cheap (for its importance) equipment resides. Even if North America sinks to the bottom of the Ocean, DNS should still happily resolve.
Expensive (but impressive) measures are not the answer to reliability. Geographic diversity of cheap systems is the answer most most applications. Today, we have incremental transfer protocols such as rsync that will even transfer massive databases back and forth by only sending the changes. It's largely marketing, unwarrented by technical considerations, that make companies spend so much money on these extra sigmas of reliability.
Simple way to take down the site....
3 Letters.... E M P
Haha!!...
> I actually prefer Missile silos for ulitmate security.
Assuming you mean reusing old missle silos, it's a bad idea, for several reasons.
1.) The old silos were not designed to handle the electrical load that a datacenter requires.
2.) Missile silos are designed to protect against nuclear strike, but not much else. Foot soldiers would make short work of such facilities. Think heavier-than-air tear gas or burning jet fuel if you don't know why.
3.) Missile silos are generally full of asbestos and other nasty stuff that would be very costly to remove.
4.) Most missile silos have water leakage problems. This wasn't much of an issue when the only thing that got wet was the tail of the rocket booster, but computers are understandably less durable in such circumstances.
5.) Data connectivity was a non-concern then (they only needed a telephone, and then only until nuclear war began), so getting them wired would be prohibitive. Just about the only answer is satellite link, but that's not secure from destruction from the air.
6.) Missile silos were not siege-ready; that is, they didn't have weeks of supplies in case they were locked in. The assumption was that by the time they had a problem with supplies, the missile would have already launched.
Virg