Windows Clustering/High Availability/Fault Tolerance, Exchange and PATHWORKS

www.bancu.com/Inprint

	*Servers: Windows NT Clusters Struggle to Scale* Despite the fact that clustering Microsoft Windows NT servers has been technically possible for quite some time, solutions are far from scalable and have difficulty growing as enterprise networks grow. And although Microsoft is addressing the issue of multinode clustering in an upcoming version of its Cluster Server software, it is unclear when the software will be available to network managers.
	Installing Microsoft Cluster Server Installing Microsoft Cluster Server (MSCS) software is straight forward and simple. Notice that I said the server software, not the cluster itself. Installing the cluster is a more difficult task because cluster is more than software: It's a carefully assembled collection of hardware and software that's part of your high-availability computing environment. This article will help you understand that the difficult part of installing MSCS is the preparation.
	*Servers: Cluster Conundrums* In the year since the two most prominent PC NOS vendors--Novell and Microsoft--began touting their clustering solutions, users have yet to see PC server clustering become easier. Moreover, there is a certain amount of ambiguity over what PC clustering really means. Complex solutions and ill-defined definitions make PC server clustering a confusing proposition.
	*Clustering: Add Clusters to the Bunch* Compaq is hoping to fill a void in the WinTel world in another area: clustering. The company is readying software add-ons to Microsoft Cluster Server that address several deficiencies in the much-hyped clustering application.



	*In Search of Continuous NT Computing* Implementing a data mirroring with fail over solution might be a better high-availability option for your environment than clustering. This article highlights MSCS differences and gives you a starting place to determine if data mirroring with failover is a viable solution for your environment.
	PATHWORKS and NT Ifyou run PATHWORKS, you're probably trying to decide whether to stick with PATHWORKS, integrate NT into your current system, or migrate to a strictly NT environment. Deciding what to do with your system is complex. You need to examine why your company began using PATHWORKS, what your company uses the software for today, and which solution will work best for your organization. If you run PATHWORKS for OpenVMS, this article will help you examine these issues and decide how to move to an NT environment.
	Planning for Microsoft Cluster Server Configuring your environment for MSCS takes a fair amount of network-related planning beyond hardware configuration and software installation issues. You have to address these issues before you have several thousand dollars of cluster parts sitting in a corner of your office and a CFO breathing down your neck. Here's how to prepare your network environment before you implement NTS/e and Microsoft Cluster Server.
	*Managing in Complex NT Environments* Deploying Windows NT in your already complex OS environment? Here's a look at the integration concerns facing IS leaders and technicians as they deploy Windows NT throughout a mixed-platform enterprise.