how hard is it to build a server?

[Matt]

I've built quite a few computes in my time from generic office desktops to
fast gaming systems and even high end video editing systems, but I have
never tried a server. My boss has been given a generic quote for one and
wants to see if I can build it for less money than this company. Their
generic quote lists the following hardware:

2.13GHZ ZEON CPU
2GB RD RAM
DVD R/W
4-146 GB SCSI Hard Drives
PERC RAID controller
DRAC controller

On the hardware side of things is there anything really different from
building a server vs. a desktop pc? I'd be responsible for getting it up and
running with OS and all drivers loaded then the company will come in and
install their software and configure the system.

Also unless they need some sort of specific config, could I get away with
SATA drives in place of the SCSI? I'm planning to ask their tech guys what
the drives are going to be used for and how they want the drives configed...
but I wanted another opinion.

 

[Rarius]

Having built both user PCs and server machines, I can tell you with some
confidence that there is precious little difference.

You don't specify what use the server will be put to. Is it going to be
a webserver, fileserver or application server, or some combination of
the three. I am going to assume the latter and that your company is
small/medium sized (up to 200 users).

The Zeon processors are marginally better, but personally I do not think
that outweighs the increased cost of CPU and mobo. A top end Core2Quad
(Q9550 etc) or i7 processor will perform quite adequatly and cost less.

2GB of RAM is a little stingey. Personally I would go wityh 4GB if you
are installing a 32bit OS or 8GB on a 64bit OS. Yes I know, 32bit OSs
can only give you 3.25Gb actual usable RAM, a server will usually use
all the available RAM!

4x146GB SCSI HDs... Hmmm... Overpriced and undersized! SCSI was the
sensible choice for servers in days gone by, but good SATA drives are
easily fast enough for most server applications nowadays. Depending on
the use they are going to be put too, I would have a pair of Samsung F1s
in a mirror RAID, but with ALL important info backed up every night. I
tend to use external eSATA or USB drives for backup. They are faster and
more robust than any tape system yet invented... and cheaper in the long
run!

DRAC is a "nice to have" but should not be considered a neccessity
unless the server is going to be physically inaccessible. I also think
it is DELL only!

BTW don't ask the company what they want in the way of HDDs... ask them
what their data requirements are and then tell them what you'll do to
meet that requirement. If you ask them, they'll ask for the moon!

Rarius

 

[Matt]

From the way the original is worded it sounds like there may be some
hardware and OS issues related to possibly a new application being
acquired.

If this is true, and there is to be ongoing support from outside, I
would generally suggest that you go with the suggested hardware from the
suggested supplier. It cuts down on the "finger pointing" syndrome when
things go "bump". Support staffs are more comfortable with known
hardware configurations.

I've built a few servers for situations like this and found that
software support people mostly don't understand how hardware works.

That may actually be the route we take.. I know I can save some money
building my own system vs. letting the company provide the hardware (I think
they just order a system from Dell) but it would cut down on any issues I
may have with their tech support.

The system will run a warehouse management and point of sale software
package for a business with 2 locations. There will be a server at each
location and they'll be linked together to share data as well.

I did ask how they wanted the drives configured and they said 3 are in a
RAID5 and one is a hot swap backup drive.

 

[Matt]

So you've already done this?

<http://www.google.com/#hl=en&q=How+to+build+a+server?&aq=f&oq=&aqi=g10&fp=-
Pw1cEIpNGU>

What kind of server did you plan on building?

I did google buidling a server and skimmed over a few articles and didn't
really see any major differences in building one vs. a desktop... at least
in terms of hardware. And that's why I asked in here... I wanted to get the
advice of people with a little more knowledge of building just to make sure.

 

[Man-wai Chang to The Door (+MS=32B)]

I've built quite a few computes in my time from generic office desktops to

fast gaming systems and even high end video editing systems, but I have
never tried a server. My boss has been given a generic quote for one and
wants to see if I can build it for less money than this company. Their
generic quote lists the following hardware:

1. You should just *HONESTLY* tell your boss that you are not quite
qualified to comment on IT stuff. Because you were good in this
server stuff, you would not have asked us here.

2. If you didn't be frank, you might end up being fired by your boss.

3. Does your company have an IT or computer department?

--
@~@ Might, Courage, Vision, SINCERITY.
/ v \ Simplicity is Beauty! May the Force and Farce be with you!
/( _ )\ (Ubuntu 9.04) Linux 2.6.30.4
^ ^ 21:21:01 up 4 days 47 min 2 users load average: 1.44 1.45 1.39
???! ???! ???! ???! ???! ???! ????? (CSSA):
http://www.swd.gov.hk/tc/index/site_pubsvc/page_socsecu/sub_addressesa

 

[Matt]

1. You should just *HONESTLY* tell your boss that you are not quite
qualified to comment on IT stuff. Because you were good in this
server stuff, you would not have asked us here.

2. If you didn't be frank, you might end up being fired by your boss.

3. Does your company have an IT or computer department?

--

I am the IT department We just don't have a server in the office. I
already manage all the computer repairs in the building as well as all
other tech repairs and out adhoc network. I'm not going to be managing the
software side of the server at all, but I have built enough computers in my
time to feel more than confident enough to build one if I'm not looking at
any major differences. I'm researching the minor differences now and it
looks fairly simple to me since I now know the specs of what they need out
of the server for performance. I just wanted to check in here to make sure
there wasn't anything out of the ordinary I might need to contend with on
the build.

Though, like someone else suggested, I may just let them put in a couple of
Dells just so I don't have to mess with it in the future. It's just that
knowing my boss, I'll have to be the one repairing everything anyways.

 

[James Harris]

I am the IT department We just don't have a server in the office. I
already manage all  the computer repairs in the building as well as all
other tech repairs and out adhoc network. I'm not going to be managing the
software side of the server at all, but I have built enough computers in my
time to feel more than confident enough to build one if I'm not looking at
any major differences. I'm researching the minor differences now and it
looks fairly simple to me since I now know the specs of what they need out
of the server for performance. I just wanted to check in here to make sure
there wasn't anything out of the ordinary I might need to contend with on
the build.

Though, like someone else suggested, I may just let them put in a couple of
Dells just so I don't have to mess with it in the future. It's just that
knowing my boss, I'll have to be the one repairing everything anyways.

You are well enough qualified. As you suspected a server differs from
a PC only in choice of specific components. As long as you pick
components to match or exceed the spec you'll be ok. The only things I
would add are

1. Ensure you have plenty of cooling and then add a bit more. Think of
airflow over all parts including disks.
2. Take backups and consider how you would rebuild.
3. Consider booting from a raid 1 disk pair.
4. Consider any needs for remote access from another office or from
home to carry out power cycling.
5. Consider buying spare parts rather than paying an annual
maintenance charge on hardware.

James

 

[Matt]

Ok. It's just the requirements for a file server are a bit different
from a web server which are a bit different from a print server, etc.
, etc.

From your other post it looks like your trying to build a store
controller ("The system will run a warehouse management and point of
sale software package for a business with 2 locations. There will be
a server at each location and they'll be linked together to share
data as well.")

Will the server/controller be running both locations in case of the
falure of one location? This will require a bit more hardware per
machine/location if so.

no, there will be an identical server at each location and they will be
linked... so basically I'll be building 2 of these.

 

[Rarius]

I did ask how they wanted the drives configured and they said 3 are in a
RAID5 and one is a hot swap backup drive.

I would query WHY they want RAID5...

Your suggested system will give you a single logical drive about twice
the physical size of each of the single drives. It will be tolerant of
one drive dying. Striped RAID systems (like RAID5) were much more useful
in the old days when hard drives were much smaller. With modern drives
reaching 1.5Tb and even 2Tb available. I wonder if you need a complex
RAID like RAID5.

I would suggest you look at putting the 3 drives in a RAID1 (mirror)
setup which would give you twice the fault tolerance. RAID1 is also much
easier to repair when a drive dies (as it inevitably will!)

I am not convinced about the hotswap drive... These tend to be
propriatory and expensive. A couple of eSATA or USB2 drives would be a
better investment for backup.

Rarius