How Have You Equipped a Tiny Server Closet? 81
BenEnglishAtHome asks: "One of our remote offices will soon be gutted/rebuilt and our local IT staff managed to fumble the political ball. Our server closet is being reduced to 45 square feet and there will be no more unused desk space that can be occupied by visiting techs. Result? That 45 square feet must house 3 desktop-size servers; 3 UPSs; a fully-adjustable user workstation that includes separate adjustments for work surface height, keyboard height, and keyboard angle as well as a big ergo chair; an area suitable for workstation diagnostics; a good KVM switch; 2 monitors, keyboards, mice, and laptop docking stations that must be simultaneously available; and some amount of small item storage, while still having enough room for a door to swing into the roughly square room. The only bright side is that I can have all the A/C, power, and LAN drops I want. Has anyone managed to find and deploy a freestanding server rack/workstation/furniture system (probably something L-shaped) that can perform this many tasks in such a small space?"
Right... (Score:5, Interesting)
Yes, it's called a rack and a desk. You can find both of them available from retailers the world over. Seriously, this question is... trivial. It's all up to how you want to arrange things. As others have suggested, you could buy a seriously powerful multicore system with plenty of RAID storage that takes up under 4U for a few thousand dollars. Ok, so put it in the rack with the UPSs on the bottom (wait, do you need them all anymore?), a shelf with a monitor and KVM (because you only need it for emergencies, since you should connect in normally by remote) and we just used up under 12 square feet. That's a lot of room left for a desk and chair! Even if you don't want to buy a new server, then buy a few more shelves for your rack and stick them in it standing up.
I have five machines, one of which runs five other VMs, several UPSs an LTO-3 backup system, two ancient mini-fridge sized servers and a KVM all taking up less than 25 square feet. Half of that is the two ancient servers I'm about to get rid of. It's not that hard...
Try not doing it... (Score:4, Interesting)
This clearly isn't the advice you asked for. Personally, I'd make effective use of shelves (and or cabinets), and use the longest table that will fit on the longet dimention. Get the next longest table for the other dimension. There should just be room for the door to open, and the chair to be out of the way when someone is sitting in there. You can stack desktops and tower cases underneath. Have a working surface for repairs on top. Hook the laptop dock into the KVM, and put the dock up high (I once packed 10 computers into a room that was 6.5x9.5 or so at a small startup, oh and that was also my office). Now, that I've given you the token advice you've asked for. Let me try giving you my real advice:
I've been reasonable effective with the passive aggressive stance, of not supporting something so stupid. I'm not sure I can visualize just how dumb this is (I'm not good with descriptions of space). If this is truly a political issue, put in everything you can fit in with a reasonable about of space. The rest of it became "do without". I've seen 60 person offices run of development offices run off 3 machines in a server room that run all of the IT infrastructure for the company. It's stupid, but it can be done. A decent desk and an LCD monitor are all that's needed. It'll easily fit within a 7x7 room (a square room roughly of the right size).
You'll be shocked and amazed at the types of results you get from, "I've done everything I can with the resources I have. This project will continue to be a nightmare and always behind the eightball until we decide to do it right. I'll continue to do my best to support it as it is, but it'll take more time, and cost a lot more money then just having done this properly the first time. It will continue to cost us money, and I can give you estimates of the amount of time it will take for resolving this properly will become profitable".
Generally speaking, no sane boss will argue against that. I've come dreadfully close to being fired on several occasions because for this. However, I was kept around as "the guy who got stuff done". Generally letting people suffer the consequences of their stupidity is the single most effective and convincing way to get them to see the error.
I used to work with a woman who everytime you asked her to test things you developed for her to automated a business process she was in charge of that "it was so broken, that I'll just do it by hand". No matter how far or near you were to the mark, if it didn't work perfectly the first time she would refuse to work towards fixing it. Wouldn't explain what she needed or what was wrong. She used to do that to everyone. And everyone worked really hard to coax her into discussing it like a rational person. I found the most effective way to deal with her was to walk out. Wait 3 months until she was completely overwhelmed by the problem you were in the middle of automated. Dust off the old code, work with her for a day and finish up the automation. No one every understood that, all she wanted was the attention of how much crap she had to do, and all the crap she did by hand for you. Most importantly, she liked working harder, not smarter. So automating it before it was absolutely necessary ruined her mind set. Generally speaking, letting someone suffer the consequences of their decision is the ultimate way of convincing them that they were wrong.
Ironically, I did get laid off about 2 months after explaining to my boss that he needed to find a way to make backups. He could make me repsonsible for them, and I'd do them. He could motivate the lazy piece of crap who hadn't gotten them made in the 9 months he'd worked there (even more irritating, he dismantled the old backups that worked). Since I was the one who'd get to spend 96 straight hours in the office rebuilding our network due to no backups, I had a bit more vested interest in seeing them work. I worked really hard to be ahead of the game in everything I did, and I'd be responsible for cle
Re:Memos, Memos and more Memos (Score:3, Interesting)
[ It's kind of like asking questions that start with, "I know this guy with herpes..." ]
A memo filled with finger pointing and blame throwing will be a fine document for the new IT guy to use to justify a new server room, but won't help Ben keep his job for another minute.
The moral of the story is "never throw stones at the crane operator in a quarry."
Lab A/C system as Wine Cooler (Score:3, Interesting)