Windows clustering and geographically separate sites

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q280743
Geographically dispersed (majority node set) server clusters are built on a networking and storage infrastructure with characteristics that are very different from a standard quorum device server cluster. Therefore, they are certified under a separate testing program. If you want to convert your existing server cluster to a geographically dispersed server cluster, work with your hardware vendor to obtain a geographically dispersed server cluster configuration that has been certified by Microsoft.

You can create many geographically distributed solutions by adding data-replication software and extended Local Area Network (LAN) hardware to existing certified configurations. However, these solutions radically change the nature of a precertified configuration, particularly with respect to timing and latency. Therefore, Microsoft requires that, for it to be supported by Microsoft, the hardware and software configuration of a geographically dispersed cluster be one that is certified and listed on the cluster Hardware Compatibility List (HCL).For additional information about the HCL and Windows Clustering, click the following article number to view the article in the Microsoft Knowledge Base:
309395 The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
Nonqualified software solutions on existing signed hardware are not supported.
You can use Windows Clustering to implement geographically dispersed clusters in scenarios where you can deploy the members of a single cluster on several different sites. Windows Clustering does not detect the extended nature of these types of clusters, and it is the responsibility of the network and storage architectures that are used to build these geographic clusters to preserve the semantics. In particular:
  • The private and public network connections between cluster nodes must appear as a single, non-routed LAN that uses technologies such as virtual LANs (VLANs). In these cases, the connections network must be able to provide a guaranteed, maximum round-trip latency between nodes of no more than 500 milliseconds. The Cluster Interconnect must appear as a standard LAN.
  • Any geographically replicated storage technologies must preserve single disk semantics, such as persistent arbitration of a LUN-to-Windows Clustering. The quorum disk must be replicated in real-time, synchronous mode across all sites.
Because of the complexity of geographically separated clusters, you must involve the hardware manufacturer in any issue. Frequently, the configuration includes third-party software and drivers that are required for the clusters to function. Microsoft Product Support Services may not be aware of how these components interact with Windows Clustering.

Configurations must be certified with a maximum supported distance between nodes for a particular site interconnect (such as a certified configuration with nodes that are one mile apart that uses fiber that is not supported if the nodes are deployed more than one mile apart or if the interconnect is copper).
For additional information, visit the following Microsoft Web site:
srdf stretch san switch emc swvr mscs powerpath powerpath.sys geocluster

Artikli ID: 280743 – viimati läbi vaadatud: 02/28/2007 22:00:21 – redaktsioon: 6.4

Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

  • kbclustering kbenv kbinfo KB280743