Cluster servers or servers performing seperate tasks, which is better? 1

[Newmc]

We have one Microsoft Small Business server on our network that does it all. It is the domain controller, email server, file server, etc. etc. etc. We want to build in some redundancy, so we are considering clustering two servers that do it all just the way our one server is set up now.

Do you think that this is the best way to go, or would it be better to have seperate servers for email, files, domain controller etc?

I really value everyone's thoughts on this...Thanks

 

[InfrArch]

Ofcourse, cheaper to have a separate servers. (ofcourse the cost primarily depends on SAN's cost) Anyway, from MS and my point of view, your current conf isn't good. You have a single point of failure... but.. you know it !
In your case, cluster or separate servers conf. depends firstly from the amount of current users in your company, budget and so on... I need more info. But anyway one of the best solutions , possible, : File servers - separate servers; Mail services - in cluster; DC: - it is already redundant system in case of W2k/NT (ofcourse if you have more that one DC)

Victor
MCSE+I;MCSE(w2k);CNE(5.1&6);CIWSP;CIWSA
destiny2002@list.ru

 

[Newmc]

Thanks Victor,

Your reply was very helpful. I should have mentioned the number of users in my first post. It is a small business with 30 users on the network. We do want to keep our costs down.

Also, we make extensive use of Foxpro through the network. Foxpro is also tied to the production line so if the file server goes down we miss the capture of a lot of data from the line.

Does this info change your suggestions any?

Chris

 

[InfrArch]

oh, the situation becomes more understandable ... ))
So, as I understand FoxPro availability 24x7x365 is the primary goal? OK! Can tell you the CHEAPEST solution EVER possible: (from my BIG experience )
1.DC's ,as I wrote, are redundant by design (have MORE than 1 DC. Recommended amount - 3) In case of failure there is NO problem to get the system back online.
2. E-mail server - separate cheap server (you have just 30 users!) + MAKE regular backups + MAKE an image from this server every month for example. in case of failure: recover from last image - 40min + recover a backup~ xx min
3. file server - it is better to have separate server... but in case of 30 users you can use mail server as file server also. (it is not good, but if money is an issue..)
4. FoxPro - 2 separate servers! 1 - working ,fully configured server. Second - THE SAME HARDWARE,THE SAME CONFIGURATION, (you can do it by imaging workind server and then restore the image to 2 - backup FoxPro server) so, in case of failure of 1 server you simply take the failed one out from the net and plug the second one - that has the same hardware and software settings. (for this purposes use GHOST + backups REGULARILY)

hope my advices will be useful.


Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.

 

[InfrArch]

OH , sorry, I forget , that you have SBS... as I remember all the components from the SBS MUST be installed on the SAME server... In this case - just cluster solution helps you. - but it's not so cheap. Regarding FoxPro - advice the same as in previous letter.

Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.

 

[gurner]

Message to VictorKozlov

I have been reading your advice with interest, i am in a similar situation, and have come up with the same conclusion.

Thing is i need advice on how?

The SBS4.5 server was recently upgraded by me to SBS2000 and promoted, and after the exchange 5.5 went pop, got it working again.

But we want to split the overloaded SBS2000 machine down the middle and get two clean 2000AdvSvrs sharing responsibility.

One being the PDC with AD and Exchange2000 and other gubbins, the other one being the BDC or Replication partner with SQL Server, IIS and more gubbins.

Most of this we (Me) can do but i'm Very Very vary of the Exchange server, i do not want to break it again.

It is currently 5.5, what should i do? Upgrade it on the SBS machine? (i can safely do that) but how do i move it onto a new one? (exactly please)

I have some sort of vague idea, but need ideally some more advise

 

[InfrArch]

Hello Girth!

In your situation it is better to migrate SBS4.5 to SBS2000. By this migration you will update all the SBS4.5 components and will get new ones. You will get Exch2k fully configured for your environment - it is very important in your case. But currently - upgrade your Exch5.5 to Exch2000 on your SBS2k. Why you would like to use W2kAS? You need cluster in future? It's much costly to use W2kAS... use simply W2kS.
The you can start to build your new infrastructure. If you have no problem regarding IT budget I will NOT recomment you to setup Exch2k,SQL and IIS on the same AD (DC) servers.. use Member servers for this purposes.
You can easy migrate your existing exch2k (on SBS2k) to the new one. Use MS articles to find a step-by-step guides. I just (now) can remember 2 migration variants:
1. exch2k(new one) must have the same config as old one. then you can simply restore a backup that was maded from the old one to the new Exch2k.
2. create the same conf on the new exch2k. Migrate each mailbox from the old one to the new one .


Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.