1 / 5

Understanding Cluster-Aware Services in Windows 2000 Advanced Server

Learn about DFS, DHCP, and WINS services in Windows 2000 Server clustering, providing fault tolerance and scalability. See benefits of cluster-aware services and set up virtual servers for high availability.

marlenepatterson
Download Presentation

Understanding Cluster-Aware Services in Windows 2000 Advanced Server

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Services • DFS, DHCP, and WINS are cluster-aware.

  2. Services • Services, like applications, are either cluster-aware or cluster-unaware. You can also configure cluster-unaware services as generic resource types. You need to install a cluster-unaware service on both nodes and set it as active in the registry before you can configure it to run in the cluster. Cluster-aware and clusterunaware services have the same advantages and disadvantages as cluster-aware and cluster-unaware applications. • The following services included in Windows 2000 Advanced Server are clusteraware. • DFS • DHCP • WINS

  3. Distributed File System (DFS) • When you install DFS in a server cluster, the DFS root is fault tolerant. Having a DFS root that is fault tolerant will allow clients to access data that is stored on multiple systems though a \\VirtualServer\Share mapping that either of the nodes in the Windows 2000 server cluster can host. If the node that is currently hosting the DFS root fails, the other node will host the DFS root. Failover is a significant advantage when many enterprise clients need to continuously access data that DFS hosts. • Windows 2000 provides a domain DFS root that can provide fault tolerance by replicating the data to other computers in the domain. A nonclustered server running Windows 2000 can provide a stand-alone DFS root. However, if that server becomes inactive, the stand-alone DFS root cannot be accessed by clients. A Windows 2000 clustered DFS root provides a stand-alone DFS root with fault tolerance, making the DFS root available from a virtual server with failover capability.

  4. Dynamic Host Configuration Protocol (DHCP) • You can use the Windows 2000 (Advanced Server only) Cluster service for DHCP servers to provide higher availability, easier manageability, and greater scalability. • Windows Clustering allows you to install a DHCP server as a virtual server so that if one of the clustered nodes fails, the DHCP service is transferred to the second node. Failing over the DHCP service means clients can still receive and renew TCP/IP addresses from the virtual server. • Clustering uses IP addresses efficiently by removing the need to split scopes. A database stored on a remote disk tracks address assignment and other activity so that if the active cluster node goes down, the second node becomes the DHCP server, using the same database as the original node. Only one node at a time runs as a DHCP server, with the Windows 2000 clustering database providing transparent transition when needed.

  5. Windows Internet Name Service (WINS) • By maintaining and assigning secondary WINS servers for clients, you can reduce, if not fully eliminate, the effects of a single WINS server being offline. In addition, clustering can provide further fault tolerance. In an enterprise WINS environment, you can reduce the number of redundant WINS servers and rely on Microsoft Cluster service for fault tolerance. WINS running on a Microsoft Cluster service cluster will also eliminate any WINS replication traffic. • Note: You should not create static network name to IP address mappings for any cluster names in a WINS database. WINS is the only name resolution method that will cause problems when using static mappings, because WINS static mappings use the MAC address of the network card as part of the static mapping.

More Related