Basic knowledge: cluster formation and operations

Once the cluster service is installed and run on the server, the server can be added to the cluster. Cluster-based operations can reduce the number of spof and achieve high availability of cluster-based resources. The following sections briefly describe the node behavior in cluster creation and cluster operations.
Note: For information on installing a cluster server, see the help and deployment guide for the Windows Server 2003 product family.
Create a cluster
In
The server cluster product contains a cluster installation utility used to install cluster software on the server and create a new cluster. When creating a new cluster, run the utility on the computer that is selected as the first member of the cluster.
. The first step is to determine the cluster name and create the cluster database and the initial cluster member list to define the new cluster. Windows Server 2003
The cluster adds a cluster management setting wizard and the cluster creation (including remote creation) function using the cluster.exe command line interface.
The second step of creating a cluster is to add a shared data storage device that can be used by all cluster members. In this way, the new cluster will have a node, its local data storage device, and the Cluster's shared resources-usually disk or data storage and connection media resources.
The last step to create a cluster is to run the installation utility on each computer that will become a member of the cluster. Each time a new node is added to a cluster, the new node automatically obtains a copy of the existing cluster database from the original members of the cluster. When a node joins or forms a cluster, the cluster service updates the private configuration database copy of the node.
Form a cluster
If the server runs the cluster service and cannot find other nodes in the cluster, it can form a cluster by itself. To form a cluster, the node must be able to obtain the exclusive right to the arbitration resources.
When a cluster is initially formed, the first node in the cluster includes the cluster configuration database. Each time a new node joins a cluster, the new node obtains and maintains a copy of the cluster configuration database locally. The latest version of the configuration database is stored in the form of recovery logs for arbitration resources (including cluster configuration and status data irrelevant to the same node.
During cluster running, the cluster Service uses the arbitration recovery log to perform the following operations:
Ensure that only a group of active and communicating nodes can form a cluster.
A node is allowed to form a cluster only when it has control over the arbitration resource.
A node is allowed to join or stay in an existing cluster only when it can communicate with the node that controls the arbitration resources.
From the perspective of other nodes in the cluster and the cluster service management interface, when a cluster is formed, each node in the cluster may be in one of three different states. The event processor records these statuses, and the event log manager copies these statuses to other nodes in the cluster. The cluster service status includes:
Offline. The node is not a fully valid cluster member. The node and its cluster server may be running or not.
Online. The node is a fully valid cluster member. It complies with the updates of the cluster database, imposes its own impact on the arbitration algorithm, maintains heartbeat communication, and can own and run resource groups.
Pause. The node is a fully valid cluster member. It follows the updates of the cluster database, imposes its own impact on the arbitration algorithm, and maintains heartbeat communication. However, it cannot accept resource groups. It supports only the resource groups it currently has. The pause status is provided to allow some maintenance. Most server cluster components deem online and paused as equivalent.
Join a cluster
If a server is to join an existing cluster, it must run the cluster service and be able to locate other nodes in the cluster. After finding other nodes, the added server must undergo cluster membership verification and obtain a copy of the cluster configuration database.
Add
The process of entering an existing cluster starts with Windows Server 2003 or Windows 2000 Service Control Manager.
When the cluster service is started on the node. During startup, the cluster service configures and loads the local data devices of the node. It does not try to bring the shared cluster data device online as a node, because the existing cluster may
These devices are in use.
To find other nodes,
Starts a discovery process. When a node discovers any cluster member, it performs an authentication sequence. The first cluster member will authenticate the new entrant and return success after the new server is successfully verified.
Status. If the verification fails (the cluster member to be added to the node cannot be identified, or it uses an invalid account password), the request to join the cluster will be rejected.
After successful verification, the online cluster node checks the configuration database copy added to the node. If the copy is out of date, the cluster node that verifies the addition of the server sends an update copy of the database to the added server. Nodes that have just joined the cluster can use the copied database to search for shared resources and bring them online as needed.
Detaching from a cluster
When the node is closed or the cluster service is stopped, the node may be detached from the cluster. However, when a node does not perform cluster operations (for example, it does not submit updates to the cluster configuration database), the node may also be forced out of (evicted) The cluster.
For example
If the node leaves the cluster as planned, it will send the clusterexit message to all other node members,
Notify them that it will be out of the cluster. The node immediately closes the connection between resources and all clusters without waiting for any response. Because the other nodes receive the Exit message, they will not be executed on the node accidentally or
The regrouping process that occurs when network communication is stopped to re-establish the cluster membership.