Windows 2000 Server and Server to Server Replication

Hi there,
  I am looking for some suggestions on software that I could use in a corporate environment to have 2 Windows 2000 server's duplicate themselves completely!  What the corporation wants to experience is the ability to have complete fail-over on the SERVER.  To the point of, one SERVER dies, and in a matter of seconds the 2nd one takes over and from the user's point of view there was no change and they are still up and running while the 1st SERVER is corrected.  I would greately apprecate any experiences or maybe some links to software that can provide this solution.  

Thank you in advance!
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

oBdAConnect With a Mentor Commented:
Roughly spoken, a two node cluster as example: In a cluster, you can create (virtual) resources (IP addresses, names, file shares, services ...) that can be accessed by the clients. Only one of the machines actually owns the resource and offers it to the network, while the other monitors the first server (the situation of an active/passive cluster). The other nodes might as well offer other services, and be in turn monitored by the first (an active/active cluster). In case one node goes down, the resources are switched over to the other node, and the rest of the network can (mostly) move on and won't even notice it.
Whether you need external storage depends on your needs. In W2k3, you can theoretically do without (using the Majority Node Set feature for the quorum); but as soon as you want to have a clustered file server, there's no way around it. Your corporation won't get a working and reliable failover solution for the price of two standard servers.
The cheapest solution to test if this is what you're actually looking for is to download the evaluation copy of Virtual Server 2005; with this, you can setup two virtual machines as cluster nodes, without having to invest in hardware just for testing (assuming you have a machine with enough memory for Virtual Server).

Microsoft Virtual Server 2005

Available Features in Windows Server 2003 Clusters

Quorum Drive Configuration Information

Network-Attached Storage and Server Cluster Support

TechNet Support WebCast: Majority Node Set support in Microsoft Windows Server 2003 clusters

Cluster Service Startup Options
Depending on which services the "duplicate servers" should offer, Microsoft Clustering might be what you're looking for. Prepare to spend quite a bit of money for that, though.
Clustering Services
KrocodileAuthor Commented:
I have looked at clustering before in the past, however, from what I have gathered clustering ususally requires an additional storage device that is somehow connected into the clustering environment in order for it to work correctly (i.e. like a NAS).  To be more specific about software I'm interested in.  I would like for the software to work directly on each SERVER, and not require any soft of additional hardware in between.  oBdA, maybe you could correct me if I'm mistaken about my understanding of clustering?

Thank you for your comment!
The new generation of project management tools

With’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

I have three clusters, and indeed, there is a need for shared storage between them.  We don't have a SAN (I don't think NAS would work), so we used direct-attached SCSI on a shared bus.  IBM makes some great stuff, and a file server with 1.2TB usable formatted space only cost me ~$25k...

IBM x345 servers
IBM 6M ServeRAID cards
IBM EXP400 external storage cabinet
throw in your drives..

For this, you get Ultra320 SCSI shared storage, and the servers failover immediately..  A complete failover/service start takes appriximately 90 seconds.

You may also want to do some homework on Windows 2003 clustering, since it allows the user of a local quorum drive (you must have at LEAST a quroum drive so that when one server takes over for the other it knows what's going on)..  Not sure, never tried it, but it might allow you to build a cluster without shared storage..

KrocodileAuthor Commented:
Thanks everybody for the wonderful suggestions and information!  I am going to do some reading from the provided links and definitely consider Clustering as being an option.  
One additional hint: The shared storage in the Virtual Server is based on a shared SCSI bus. You can of course do that in "real life" as well, but depending on your failsafe needs, this might not be enough. Shared SCSI has the big disadvantage (compared to a proper fibrechannel solution) that you won't be able to completely (physically) shut down one of the nodes while the other keeps up his business, as the SCSI bus won't be terminated anymore.
obda - I don't know where you got this idea from, but you most certainly CAN COMPLETELY shut down one of the nodes..  I have posted the hardware that I use above, and I have had to completely down a node on more than one occassion..

I've read that in some Microsoft document some time ago (that I can't find at the moment), where the setup of a shared SCSI bus for a cluster was described. They explained in detail that you should boot the other node and enter the BIOS or let it wait in the boot menu (especially during setup, when only one of them is running), instead of just turning it off. So unless the hardware tech who installs the stuff gives you a written statement that the SCSI bus is correctly terminated even if one node is completely taken off the power, I wouldn't trust it.
I don't doubt that it worked for you, but can you really guarantee, with a clear conscience, that for any given hardware setup, you "most certainly CAN COMPLETELY shutdown one of the nodes"?
I don't know about "any given hardware setup", but I know for 100% certain that I can guarantee it with a clear conscience for the hardware that I use.

And, the problem you describe, and the resolution (booting to BIOS), AFAIK, is not to remedy the SCSI termination issue (since SCSI busses have been self-terminating for quite some time now), it is to remedy the situation caused when the heartbeat cable thinks it's been unplugged.  You don't want this to happen for a prolonged period of time.  Not only that, but during the cluster build process, you can't have both machines connected to the SCSI device at the same time without corrupting the disk (before the cluster is initialized), but you need to be able to communicate with the other node during the setup..  The solution?  You guessed it, boot to the BIOS so the other network card shows as alive..

However, with the IBM servers I have (and I'm sure a lot of other models as well), the server doesn't even have to be on, it just has to have power, and the NIC will be active...

The article referenced specifically the SCSI termination; I'm not making this up.
The unloading of the TCP/IP stack when the network cable is unplugged can be prevented in W2k, btw.:
How to disable Media Sense for TCP/IP in Windows
This is not necessary anymore in a W2k3 cluster; check the 278007 KB article from the links above.
Not to mention that crossover cables usually work, but the crossover function is no part of 802.3.
All Courses

From novice to tech pro — start learning today.