server mirroring? 1

[pkirill]

What I'm looking for is a setup where I can have two identical servers that are consistently replicating to each other but the end user only sees one server. What I want to be able to do is take one down (or have one crash) and not take the entire network with it.

Can anyone give me some direction as to what I should be looking for? Virtual servers, mirroring, clustering?

I'm currently running Win2K3 server with about 40 users.

thank for any help!

 

[fs483]

Look for Windows Clustering.

http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx

 

[rvnguy]

pkirill,

If you attempt to do this leagally(and to have both live you must), you should look at the "cost/benefit" of doing so. W2K3 and 40 seats is pricey to just have as backup, add to this one must add the hardware costs.

As you have considered this type of expenditure one would assume that you have mission critical data that requires protection. And with a base of 40 clients you are most likely using a tower server and not a rack.

A common approach is to setup the OS on RAID 1 drives(mirror) and a RAID 5 Array for data. This provides for OS proection through an identical copy and data integrity from striping redundancy. The statistical probability of experiencing more than one drive failure in a small time window is beyond comprehension.

One could, with the savings from replicating the OS & seats, build a backup box less drives and using hotswap drive cages could be back up in the event of a mobo failure in record time.

What ever you decide, use "Quality" components i.e. All server grade: PSU, drives, cards etc. and provide top of the line power conditioning UPS backup. Provide a clean, cool home for the hardware. Doing these things will mediate most of the ills that can take a server down.

I echo the previous poster for doing what you initially asked.

rvnguy
"I know everything..I just can't remember it all

 

[pkirill]

Thanks to both for those responses!

rvnguy - what you outline seems to be a better "first step". We have two identical HP ML350 G3 servers (tower, not rack - good call) - a file server and an app servers (web, mail, ftp, print...). We have been having an issue with the file server spontaneously and mysteriously "hanging". I haven't found the cause, nor have "the pros" I've had come in to look at it. The common consensus was to rebuild the array from scratch and "see if that gets it". And if we're going to do that, then we might as well set up dual arrays as you noted.

In addition, I was looking at getting a NAS box that will mirror all the data files and in the event of a crash, could simply issue a modified logon script to point everyone to the NAS temporarily.

akwong - Thanks for the clustering link. We'll be looking into that as well.

Again - thanks to both for the assist. It is greatly appreciated!

 

[rvnguy]

pkrill,

Your system "hanging" is dismaying, and needs to be corrected. Dismaying that "the pros" can not correct this.

The "event logging" capabilities of MS servers should be a starting point to assertaining what service is faulting. Point; Insure that logging is enabled if it is not as this will provide some insight as to what is faulting.

If the FileServer provides only that service, and this is the unit hanging, before you expend $ to rebuild this you might consider alternatives. You have mentioned NAS, and this could provide all fileserver functions for a MidLevel enterprise. There are several providers but I have installed on two systems the Buffalo NAS and find it to be robust & Rock Solid in a Win environ.(See Link)

I realize that you have been experiencing problems and might have trepedation on relying on a single system(with good backup plan) but I would address correcting the "problem", over living with it and providing a redundant system in the event of failure.

Systems(soft/firm ware) should be stable and redundancy is provided for those things that are prone to fail (like drives) and not for a complete system. I suppose my attitude on this stems from the "Big Iron" days where one would, generally, not think of replicating a total system due to high cost. You just made it work.

You might find that this could provide all your "Fileserver" needs at a reasonable cost.
Buffalo Tera Station

http://www.buffalotech.com/products/product-detail.php?productid=100&categoryid=10

Please keep posting your progress, as it assists the community.

rvnguy
"I know everything..I just can't remember it all

 

[pkirill]

I totally aggree with fixing it rather than working around it. But I'm leaning towards fixing it AND providing a redundant system in the event of failure. The event logs are no help at all. They are logging events as they should - have even been "tuned" to be more sensative. Everything is going along fine and then suddenly that server starts to crawl, although the task manager (when you can get to it quickly enough) is active and shows between 10-20% utilization. Eventually it will lock up - you can move the mouse but not pick anything. No viruses, no spyware, no apparent issues at the server. All this leads me to believe it is a hardware problem. So I'm looking at all the options. I do think clustering is serious overkill for our size and that the NAS is the way to go.

I will let everyone know how it goes and if you have any ideas what might be the cause of the hanging as I've described it I'd be glad to hear them!

Thanks!

 

[PurdueTNT]

In looking at fixing the problem I would start with your HDD's. if the processor isn't being hammered they might be on the verge of locking up (ceasing 'sp').