Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server loading and architecture

Status
Not open for further replies.

myopic

IS-IT--Management
Feb 22, 2002
12
US
I am planning the implementation of a Win 2K client/server system for a small-medium sized service company. The system will have approx 35 clients with the following applications:
1.) A semi-custom CRM package
2.) MS office
3.) e-mail
4.) internet connectivity
5.) other general office apps ie. small databases, mktg graphics etc.

The system is new and will have CAT 5e and 10/100 base-T switches along with 1000 base-T uplinks from the switches to the server. A hardware based router will interface to the ISDN or DSL internet connection. On the same network, a 3 Com voice over IP telephone system will be used. Several remote sessions (from remote locations could also connect at one time).

I plan on a Dell based server with approx 2- 1 Ghz or better processors, 1 Gig Ram, and 4 36 Gig ultra SCSI-3 HD's with tape backup.

Win 2K services needed are: AD with integrated DNS and DHCP (using private IP's for the clients) RRAS, file sharing, backup and application server.

My initial plan was to have all of these on one server yet in reading some of the posts it is recommended by many to partition out the functions to 2 or more servers. Since this is a relatively small network how do you size the server, partition the functions etc? Are there any good rules of thumb or more precise guidelines? What are your thoughts on this?
 
It's all personal preference and experience at this point IMO. I would recommend getting the network services you need down to the bare minimum.

Here's what you listed as requirements:
>AD with integrated DNS and DHCP (using private IP's for >the clients)

With 35 clients, is DHCP really necessary?

>RRAS, file sharing, backup and application server.

This should be the big server you buy. Lot's of disk and memory, extra processing power is helpful but probably overkill. I would put all the tofu (as it were) on this box, the CRM app (and supposed CRM DB), File storage, printing, Email etc.

Build a second small server as the DC, doing DNS.... "Nuclear war can ruin your whole compile."
-- Karl Lehenbauer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top