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!

General Networking Advice!?!

Status
Not open for further replies.

LeighW

Programmer
Jun 6, 2001
45
GB
We have a 20ish User Network with a single Windows 2000 Server. This Server currently does EVERYTHING! It is the Domain Controller, File Server, Mail Server, Print Server, Backup etc etc...

Recently it has become very unstable and seems to regularly crash...

I am after some advice on purchasing and setting up a new / second server, What would be the best setup & how would I share the tasks between the two servers... What sort of Spec Server would best suit the job?

I know this is a very vauge question - I am just after some advice on how to implement a second server onto our domain.

Thanks in advance

Leigh
 
As far as the Spec's, how many users will the server be supporting? How much data is stored? Are there any high RAM utilizing programs running?

For the implementation of the second server, I would say that you'll need to have the "new" server as the main DC, and the old as the secondary. If the old server is as unstable as you say, it's only a matter of time before it crashes entirely.
 
Thanks,

We have around 20 users...

We use alot of Access Databases with the backends stored on the server, Sage Line 50, and many office Documents (Around 10gb in total)

Sorry I am quite new to all this... so the if the "New" server is the Main DC, what would the old server do as the secondary?

Would I benefit in using the old Server as a just a File Server - To store all the files/data on?
 
If the old server is as unstable as you think, would you want the files to be sitting there? I personally wouldn't.

If you have the "old" server as the secondary, all it would do is sit there until the "new" server is down, or too busy to answer a request for login. As the server is kind of unstable, I would say this is the best solution.

Now, for your "new" server needs....I would suggest either a high end PC or a server (I'm vendor neutral, but I have my favorites) with a dual processor (databases love processors), and at least 2GB of RAM (Databases love RAM). For the disk size, I would suggest that you get something you know you'll be able to grow into. This is the catching point for a lot of people, not planning ahead for the future. I know I've done it, and every once in a while, it catches me again.
 
Excellent - Thanks for your help!

So am I right in thinking that any changes made on either server, Primary or secondary DC - will be automatically replicated to each other... The Primary Domain server (the new one) will handle everything - until it goes down or gets to busy when the Secondary will take over and users will not notice any change?!?!

Does this mean the two servers need to have the same size and number of Hard Drives to enable them to replicate between each other?
 
You will not need to have the same specs on different DC's.

Yes, all changes made on one will be replicated to the other as long as the 2 are communicating correctly.

No, the users will not see any difference between the 2 DC's.

Hope it helps....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top