Beruflich Dokumente
Kultur Dokumente
Cluster
A cluster is a group of independent servers or nodes that are accessed and presented to the network as a single system.
Active / Passive
An active passive cluster is a cluster that has at least one note running a services and application group and additional notes the group can be hosted on but are currently in a waiting state. This is a typical configuration when only a single service and applications group is deployed on a failover cluster.
Node
A note is an individual server that is member of the cluster
Active Node
In active node is a node in the cluster that is currently running at least one services and application group. A services and application group can only be active on one note at a time and all other nodes that can host the group are considered passive for that particular group.
Passive Node
A passive node is a node in the cluster that is currently not running any services and application groups.
Cluster Quorum
The cluster quorum maintains the definitive cluster configuration data and the current state of each note, each services and application group, and each resource and network in the cluster. Furthermore, when each note reads the quorum data, depending on the information retrieved, the node determines if it should remain available, shut down the cluster, or to activate any particular services and application groups on the local node. To extend this even further, failover clusters can be configured to use one of four different cluster quorum models and essentially the quorum type chosen for the cluster defines the cluster. For example, a cluster that utilizes the note and disk majority quorum can be called a note and disk majority cluster.
Cluster Resource
A cluster resource is a service, application, IP address, disk, or network name defined in managed by the cluster. Within a cluster, cluster resources are grouped and managed together using cluster resource groups, now known as service and application groups.
Failover
Failover is the process of a services and applications group moving from the current active node to another available note in the cluster when a cluster resource fails. Failover occurs when a server becomes unavailable or when a resource in the cluster group fails and cannot recover within the failure threshold.
Failback
Failback is the process of a cluster group automatically moving back to a preferred node after the preferred node resumes operation. Fail back is a non-default configuration that can be enabled within the properties of a services and application group. The cluster group must have a preferred node defined and a failback threshold defined as well, for fail back to function. A preferred node is the node you would like your cluster group to be running or hosted on during regular cluster operations when all cluster nodes are available. When a group is scaling back, the cluster is performing the same failover operation but is triggered by the preferred node rejoining or resuming cluster operation instead of by a resource failure on the currently active node.