Create an Account
username: password:
 
  MemeStreams Logo

What do Fire Chiefs need to know about Data Centers?

search

Rattle
Picture of Rattle
Rattle's Pics
My Blog
My Profile
My Audience
My Sources
Send Me a Message

sponsored links

Rattle's topics
Arts
  Literature
   Sci-Fi/Fantasy Literature
  Movies
  Music
Business
  Tech Industry
  Telecom Industry
Games
Health and Wellness
Holidays
Miscellaneous
  Humor
  MemeStreams
   Using MemeStreams
Current Events
  War on Terrorism
  Elections
Recreation
  Travel
Local Information
  SF Bay Area
   SF Bay Area News
Science
  Biology
  History
  Nano Tech
  Physics
  Space
Society
  Economics
  Futurism
  International Relations
  Politics and Law
   Civil Liberties
    Internet Civil Liberties
    Surveillance
   Intellectual Property
  Media
   Blogging
  Military
  Security
Sports
Technology
  Biotechnology
  Computers
   Computer Security
    Cryptography
   Cyber-Culture
   PC Hardware
   Computer Networking
   Macintosh
   Linux
   Software Development
    Open Source Development
    Perl Programming
    PHP Programming
   Spam
   Web Design
  Military Technology
  High Tech Developments

support us

Get MemeStreams Stuff!


 
What do Fire Chiefs need to know about Data Centers?
Topic: Technology 7:15 pm EDT, Aug  9, 2005

flynn23 wrote:

Despite the fact that the inFlow DC was taken down because an *external* transformer to the building caught on fire is sufficient enough to worry about, but then I think to myself that it could've been worse - the sprinklers(!) inside the DC could've went off too!

I would love to get the full story behind the handling of this outage. Coming from the perspective of trade craft, I'm highly interested. From what I was able to figure out by talking to people, the IDC's backup systems all functioned after the transformer exploded, but the Nashville Fire Chief told them to pull the plug on the facility. The one fellow I spoke to at Inflow didn't want to give me any details, and I didn't really press him on it. After I got the information I required, I just wished him luck and told him I hope the rest of their day goes better.

I'm guessing that Inflow does not have much equipment/sq footage. In some cases, taking a machine room filled with equipment and pulling the plug is about the best way you could come up with to create a fire hazard. Computer, storage, and networking equipment, when tightly packed, have an amazing quality for holding energy in the form of heat. Once the air stops flowing, regardless of if the equipment is powered down, the temperature can rise rapidly. From what I've been told in my past DC experience, exceeding 120F isn't that unheard of. This has caused DCs to burn down before. This is the type of thing I wonder if the Fire Chief was aware of.

Do you know if their fire suppression system is water or gas? That matters when determining how/if to pull the plug. The equipment can sit and cool down if the environment is (or can be) flooded with gas. If its water, the best way to handle it is to kill the equipment and keep the cooling going, unless of course there is an actual fire within the facility.

I'm guessing Inflow's Disaster Plan does not connect with the city in the way it should. A transformer blowing up should not lead to a DC being shutdown unless its pouring smoke into the facility or something that poses a direct life safety threat.

The Fire Chief's job is to be paranoid, so I can understand the call he made. It just begs a larger question: What do Fire Chiefs need to know about Data-Centers when it comes to these types of decisions? If every time something goes wrong such as an external transformer blowing up, it requires the facility to be shut down, it would be impossible to build a carrier class facility capable of getting past 4 nines without its success grounded on luck rather than design..

While pondering that question, you could watch this music video of the Nashville FDP-EMS doing a training exercise.

What do Fire Chiefs need to know about Data Centers?



 
 
Powered By Industrial Memetics
RSS2.0