Buy, don\’t build, enterprise servers

Steve sent me some questionable advice he found online–basically, someone advocating that you build your high-end servers rather than buying them, but admitting that it’s difficult for someone to build a $20,000 server and still be able to afford to maintain the thing.

There’s a solution: Buy it.This is the opposite of the best advice for desktops (although I increasingly tell people to just buy their computers because you don’t really save any money by building), but there are lots of very good reasons for it.

First and foremost is maintainability. The last time something went wrong with one of the HP servers at work, an LED on the front case came on before the problem became critical. Pop open the case, and an internal LED next to the failing component is lit up. Does your off-the-shelf motherboard have that feature? It may or it may not.

How does hot-spare memory sound? It’s kind of like RAID. You buy identical DIMMs to put in the system, but you buy one extra one, which goes into a specially designated slot. When a DIMM starts to fail, the system switches over to the hot spare. In the case of the mid-range HP servers, you can even open the case up, remove the failing module, and replace it, without powering down.

Of course you want your server to have RAID, and use hot-pluggable drives, so a failed disk doesn’t mean downtime. All but the very cheapest commercially-built servers have that feature from the factory.

But if you really have a budget of $20,000 per server, you shouldn’t even mess around with local storage. Buy some kind of a Storage Area Network instead. Basically, it’s a large bank of disks that connects to any number of servers. Some use a Fibre Channel connection, while others just use an Ethernet connection. Then you buy disks, slap them in the SAN, and configure the SAN to split the storage up between the servers. Ever run into a situation where you need 40 gigs of storage, and one server has 10 gigs free and one has 30 gigs free, but there isn’t much of anything you can move around to consolidate that free space? The SAN eliminates that. You can add one monster 300-gig disk to an array and split that storage up however you want. And one hot spare protects the entire array–no more need to buy one hot spare for every server on your network. On a big network (40 servers), that alone can pay for the SAN.

Finally, as far as spare parts go, a company ought to keep a couple of spare hard drives around for the times when a disk in a RAID array or SAN fails. But you put the servers on a maintenance agreement with someone like HP, IBM, or EDS, so that when anything else fails, that company comes out and replaces parts with its inventory. Outsource your server organ donor bank. You’ll save money, not just on the parts themselves, but also on physical storage space.

When I can get all of these features (except for the SAN) in an HP Proliant server that costs about $3,000, there’s no point in my employer wasting time building its own servers.

2 thoughts on “Buy, don\’t build, enterprise servers

  • February 7, 2004 at 12:33 pm
    Permalink

    Well. this may not earn me any popularity contests, but a certain writer of technical books has said this a couple of weeks ago. In fact, he nominated the brand as IBM (as opposed to Dell or HP). Dave, with regard to your relationship with/attitude towards that person, may I suggest that you publically regard him as a technically skilled person who deliberately (as in grandstanding) adopts such a contrarian view on non-technical matters that you do not care to discuss it, and leave it at that?

    • February 7, 2004 at 8:15 pm
      Permalink

      Well, in the midst of what I did at work this week, the only thing I did that was interesting to read about was finishing up work on an HP Proliant DL380. Meanwhile, the usual do-it-yourself crowd talks about building servers, just as it has been doing for the past few years, and as it will continue to do. And I remembered that, and thought about whether a DIY server would have been as easy to fix. In this case, there was no comparison.

      If somebody else recommends IBM and he has reason to recommend IBM (such as recent experience with a recent product), then great. When I last worked on an IBM server, it was good equipment. But that was 5 years ago.

      All of my dealings in the server room for the past five years, for one reason or another, have been with Compaq and HP equipment. Compaq’s server line became HP’s server line. So I’ve worked on a lot of HPs and haven’t had any bad experience with them–at least no bad experience that wasn’t quickly resolved. That’s why I recommend HP. Nothing against IBM or Dell. I just don’t know as much about their stuff.

Comments are closed.

%d bloggers like this:
WordPress Appliance - Powered by TurnKey Linux