Slashdot Mirror


Ask Slashdot: How To Evacuate a Network

First time accepted submitter gpowers writes "I am the IT Manager for Shambhala Mountain Center, near Red Feather Lakes, Colorado. We are in the pre-evacuation area for the High Park Fire. What is the best way to load 50+ workstations, 6 servers, IP phones, networking gear, printers and wireless equipment into a 17-foot U-Haul? We have limited packing supplies. We also need to spend as much time as possible working with the fire crew on fire risk mitigation."

23 of 331 comments (clear)

  1. Uh... by memoreks · · Score: 5, Funny

    Quickly?

    1. Re:Uh... by Anonymous Coward · · Score: 5, Insightful

      Offsite backup at the very least. Save your data and your people, and let the insurance company take care of the hardware. Loss of productivity is a problem, but you're going to have that anyway.

    2. Re:Uh... by arth1 · · Score: 5, Informative

      Offsite backup at the very least. Save your data and your people, and let the insurance company take care of the hardware. Loss of productivity is a problem, but you're going to have that anyway.

      Mod parent AC up, please. Spending time on emptying buildings of hardware which should be insured anyhow is in the best case stupid, and could even be hazardous - if it holds up evacuating the area of humans as much as a minute, it's criminal sabotage of an evacuation.
      You're not even supposed to grab your coat when a building is evacuated. Much less hardware.

    3. Re:Uh... by Anonymous Coward · · Score: 5, Insightful

      Wow, way to plan for disaster. You should already have had the systems transfered either to a clowd or to your remote site. If you do not you've failed.

      So what this gentleman says is correct. If you've not labeled everything including cables and have detailed drawings of the installations wiring you've failed.

      So what you do is get out your label maker and tools, shut it all down and label everything. Then pack it as best you can in the truck. You can expect 30-40 percent startup failure when you get them installed and attempt a startup.

      You might just want to consider building your next IT center in a shipping container that can be detached and loaded on to a semi. Done properly your UPS and AC systems would keep them alive until you could get to an alternate location with power and network which you should already have contracted for in advance.

    4. Re:Uh... by Joce640k · · Score: 5, Informative

      You're not even supposed to grab your coat when a building is evacuated. Much less hardware.

      That's when it's an emergency.

      This is more like: "There'll be an emergency a couple of hours from now..."

      --
      No sig today...
    5. Re:Uh... by TemplePilot · · Score: 5, Insightful

      You might just want to consider building your next IT center in a shipping container that can be detached and loaded on to a semi. Done properly your UPS and AC systems would keep them alive until you could get to an alternate location with power and network which you should already have contracted for in advance.

      Nods, and seconded... motion to carry.

      --
      This strange comment at the bottom of the message is illogical.
    6. Re:Uh... by fuzzyfuzzyfungus · · Score: 5, Funny

      Surely the firewall should hold out longer than that?

    7. Re:Uh... by FatdogHaiku · · Score: 5, Insightful

      You're not even supposed to grab your coat when a building is evacuated. Much less hardware.

      That's exactly correct. I've known people that literally got out naked (having been asleep), but they got out of a fire alive. If you know the fire is a risk and you can't replace the hardware for lack of insurance then the move should already be happening now...
      "We moved all the stuff for no reason" beats "We lost everything because we waited" every time in the Thoughts of Tomorrow game.

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    8. Re:Uh... by mysidia · · Score: 5, Informative

      Your insurance company will pay to replace anything that's damaged by the fire.

      Insurance does not cover any damage that should have been prevented or was caused as a result of culpable negligence, when the org intentionally passed up a reasonable opportunity to mitigate or prevent the damage.

      If you had an opportunity to mitigate or prevent the fire damage because there was sufficient warning, and you intentionally avoided mitigating the damage, that a reasonable person would have taken actions to prevent, then your reckless inaction likely means that the insurance company is not obligated to pay for the fire damage that resulted from your inaction.

    9. Re:Uh... by Anonymous Coward · · Score: 5, Insightful

      Mod parent and grandparent down, please, and tell both posters what doofuses they are. In hurricane country, do you think people are stupid for taking time to board up windows before leaving too? No. Spending time saving property when a natural disaster or like phenomenon is known to be on the way but remains hours or possibly days away from impacting you is, in fact, a DESIRABLE thing to do. Less property is destroyed. Less time and effort is spent replacing the property. Less time is spent filing insurance paperwork.

      Perhaps you're in California and have earthquakes on the brain. It's quite different. This is not "get out or we're all going to die" situation. This is a "be ready to leave town if we tell you to" situation. Sure, if the guys in charge of evacuation tell you "leave IMMEDIATELY omgfire" then you do, and save the people, and throw away the property. But it doesn't always come to that.

  2. Welll... by Dieppe · · Score: 5, Insightful

    Less posting to Slashdot would be step 1...

  3. Prioritize by Ravensfire · · Score: 5, Insightful

    Pack what's critical first. Servers. Critical networking gear. Workstations. Ignore the phones, printers and wireless gear unless you've got extra time. And good luck.

    --
    "But we decide which is right, and which is an illusion"
    1. Re:Prioritize by girlintraining · · Score: 5, Insightful

      Pack what's critical first. Servers. Critical networking gear. Workstations. Ignore the phones, printers and wireless gear unless you've got extra time. And good luck.

      Quick-disconnect hard drives. Everything else can be replaced by insurance, but your data can't. With what you've got listed above, I could hike out with your company in my backpack. The other thing is, consider the health and safety in your disaster recovery plan -- you should not expect, nor ask, your employees to stay until the last possible moment packing in equipment. Equipment can be replaced... lives cannot. Nobody should ever risk their life for an inanimate object in a business environment.

      The other thing is, you should have a disaster recovery plan that includes regular backups to an offsite facility. Any disaster plan should be able to cope with "and then a giant foot appeared above the building and squished it flat." Yours should be no different. It might not be a wild fire that threatens your servers... it could be a UPS that shorts out, or a tornado, flood, a failed fire suppression unit, or simple human incompetence (Yes, I've seen stupidity kill buildings).

      Any plan that relies on people staying in danger to save your business unethical, immoral, and probably illegal. So save what you can reasonably and without risk take, in descending order of importance... but recognize that there may be situations in which the only solution is to exit the building at a dead run and not look back.

      --
      #fuckbeta #iamslashdot #dicemustdie
  4. The site by Anonymous Coward · · Score: 5, Funny

    Nuke it from orbit. It's the only way to be sure.

  5. Um... by owenferguson · · Score: 5, Funny

    First thought is put half of them in your own car. Then put the other half in the truck and abandon it in the fire's path. Then eBay.

  6. Pictures by Anonymous Coward · · Score: 5, Interesting

    Take lots of pictures before you unplug your cables. It will save you time when you have to reconnect everything.

  7. You don't. by Anonymous Coward · · Score: 5, Insightful

    The "best" way to evacuate a data center is to already have off-site back-up for your data in place, drop a fresh copy to portable media, and walk out. The hardware should be insured. The life of your and your people (at least some of whom should probably be helping their families evacuate) are far more valuable than a few months of making your insurer pay for rented hardware until your new machines show up.

    1. Re:You don't. by Zenin · · Score: 5, Informative

      This. The parent is already +5 Insightful, but really needs to be +500.

      You don't evacuate a datacenter, you abandon it. Any other plan is a dozen different kinds of stupid.

      At best you trigger a self-destruct (software or better yet hardware) to whip all data so scavengers don't get to it while you're fleeing.

      Hardware can be replaced easily (insure it, duh). Lives and Data can not. So already have the data backed up offsite and let the lives flee as they can at the first sign of danger w/o being hindered by insanely stupid commandments like "save the copier!!!".

      --
      My /. uid is better then your /. uid
  8. YES! Save only hard drives by Anonymous Coward · · Score: 5, Insightful

    1. label all hard drives. Drive position, and server.
    2. place hard drives in anti-static bags
    3. pack drives in foam.
    4. get drives far, far away.

    Hard drives are both the most valuable, and the most fragile part. Do not load them in a stiff suspension vehicle like a truck, as this bounces the drives. Choose a soft-suspension normal car.

    Next take servers and network gear. Desktops are a maybe, as are phones. Ignore printers.

    Tape a piece of cardboard over the face of an LCD monitor to protect it from casual bumps.

    Above all, no data is worth a human life. No heroics. You're not paid for heroics.

  9. Triage and Labels by billstewart · · Score: 5, Informative

    Log off Slashdot before reading this :-)

    If you've got labeling stuff around, use it (not fancy label makers, just the basic "Hello My Name Is" and a Sharpie.)

    Grab the servers, grab the workstation bodies, grab the phones and anything else that's easily portable, and any backup media you've got. Unfortunately, rack-mounted equipment is usually harder to grab, but that's probably your most expensive and critical stuff. And it'll be your critical path, so start unbolting it first. All of that will fit, put it in first, braced as well as you can.

    Monitors and keyboards are nice, but they're just money, not data. Grab a few of them, but leave the rest for last. If you have packing material left, great, but if not you'll just have some breakage. If you've got any CRTs, leave them, they're heavy.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Triage and Labels by Anonymous Coward · · Score: 5, Insightful

      dont unbolt the parts it's time wasted and it will make transporting the lot easily while in rack with a buggy ..
      just unwire the rack and take it out as a whole .if the cat 5's are landed at punchhed patch panels
      you may be able to remove the cabling in large chunks without causing too much damage if any.

      computers ? same as above. just take the stations and put them in large bins..If you got an apple producer
      of similar large produce cases you may be able to fit all computers in one box which again is handy because
      it keeps things together and the screens in the second box . Dont waste time on kb's mice etc unless you have a
      lot of time on your hands..

      get the heck out and keep people safe is first
      hardware comes last.
      it's useless to dead people

      ric.

  10. been there done that by v1 · · Score: 5, Informative

    Two years ago we go a call telling us the levies might not hold and if they burst (1 block away) we'd have 8 ft of water. We didn't really have a battle plan and we had a lot less to deal with than it sounds like you did, but we learned some lessons.

    1) praise the lord we had good network documentation. Now is not the time to be writing down how the firewall and public and private LANs are plugged in together. Shut stuff down, and start placing network hardware in big plastic tubs. Have tubs handy for this, they nest nicely when not in use. Toss cables in a different tub. just wind them up best you can into loops and toss them in. there's probably not time for neatness, you can deal with that later. TAKE THE DOCUMENTATION WITH YOU. You'll feel mighty silly if that's left pinned on the wall. or I assume you have an electronic copy you can print when you get offsite. Make sure any servers with complex cable attachments (like to phone banks or security systems) have labels on the connectors.

    1b) got your phone system documented too? this is a whole 'nother can of worms that often is forgotten about. Does anyone have a diagram of where all those punched down wires go on each block? If you have phone switching hardware to pack, make sure the cables are labeled, they will all probably look the same with the giant connectors that attach to the blocks. "We'll just call Al, he does our phone stuff." Oh, you don't think Al is going to be BUSY helping everyone else that is returning? Nothing's as fun as a 2-3 day wait to get your phones back up and running huh?

    2) Label ac adapters. You need to know which unit wants 12vdc and which has 24vac, you don't want to fry stuff when you are trying to reassemble. every pack should have the model of the unit it goes to written on it. Gear WILL get separated from its pack during the evac.

    3) label staff's hardware. It's very annoying trying to figure out whose beige box is whose later. and they will probably fight over monitors and keyboards later. save yourself the headache. If you are already under the gun, run to the store and get a dozen rolls of masking tape and sharpies and have the staff label their equipment while you're packing things up, full initials or names, I bet you have duplicate first names you don't want to deal with later. Make sure you label the phones.

    4) have a plan for things you can't easily move. the corp office was also forecast to get 8ft of water and they were on the WRONG side of the dike so it was more of a "when" than "if". they had a very expensive multifunction printer that the service people told them they could have a tech out to take it apart (so it fit out the door) in three days, which obviously was silly. They rushed in a bunch of cinder blocks and lifted it up and set it on them 8.5' up. (I have no idea how they lifted it) In retrospect, the building got 14" of water and totaled it, they SHOULD have killed power to the building and took a saws all to a wall. OR at least watertight wrapped it before lifting. I've seen this done with entire cars when faced with an incoming flood or hurricane. Even if it doesn't keep out the water 100%, at least it will keep out the mud, which you may be very grateful later. Got a plan for your big server room ups's? those can be quite large and heavy, and are often hardwired into the AC, are you able and qualified to unhook it? Maybe you should call in an electrician now and change that armored cable to a dryer type plug? Have a place you can move big stuff that can't be evac'd to where it will be at least more likely to survive. Think of flood, fire, and tornado/hurricane, there's probably not one single place that will work best in all three cases. Smoke damage can be very destructive, simply having something wrapped in mover's visqueen may prevent unnecessary loss that the fire missed but the smoke got. Do you have a plan for that rack that's bolted down or won't even fit through the door?

    5) Document what's been left behind. A simple way to

    --
    I work for the Department of Redundancy Department.
  11. People first, data second by davidwr · · Score: 5, Insightful

    Save your data and your people

    but not in that order.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.