Professional Documents
Culture Documents
The following figure shows a Resource Monitor and resource dynamic-link library (DLL)
working with Database Manager, Node Manager, and Failover Manager. Resource Monitors and
resource DLLs support applications that are cluster-aware, that is, applications designed to work
in a coordinated way with cluster components. The resource DLL for each such application is
responsible for monitoring and controlling that application. For example, the resource DLL saves
and retrieves application properties in the cluster database, brings the resource online and takes it
offline, and checks the health of the resource. When failover is necessary, the resource DLL
works with a Resource Monitor and Failover Manager to ensure that the failover happens
smoothly.
Resource Monitor and Resource DLL with a Cluster-Aware Application
Checkpoint Manager handles application-specific configuration data that is stored in the registry
on the local server somewhat differently from configuration data stored using cryptographic keys
on the local server. The difference is as follows:
• For applications that store configuration data in the registry on the local server,
Checkpoint Manager monitors the data while the application is online. When changes
occur, Checkpoint Manager updates the quorum resource with the current configuration
data.
• For applications that use cryptographic keys on the local server, Checkpoint Manager
copies the cryptographic container to the quorum resource only once, when you configure
the checkpoint. If changes are made to the cryptographic container, the checkpoint must
be removed and re-associated with the resource.
Before a resource configured to use checkpointing is brought online (for example, for failover),
Checkpoint Manager brings the locally-stored application data up-to-date from the quorum
resource. This helps make sure that the Cluster service can recreate the appropriate application
environment before bringing the application online on any node.
Note
• When configuring a Generic Application resource or Generic Service resource, you
specify the application-specific configuration data that Checkpoint Manager monitors and
copies. When determining which configuration information must be marked for
checkpointing, focus on the information that must be available when the application
starts.
Checkpoint Manager also supports resources that have application-specific registry trees (not just
individual keys) that exist on the cluster node where the resource comes online. Checkpoint
Manager watches for changes made to these registry trees when the resource is online (not when
it is offline). When the resource is online and Checkpoint Manager detects that changes have
been made, it creates a copy of the registry tree on the owner node of the resource and then sends
a message to the owner node of the quorum resource, telling it to copy the file to the quorum
resource. Checkpoint Manager performs this function in batches so that frequent changes to
registry trees do not place too heavy a load on the Cluster service.
Diagram and Description of Log Manager (for Quorum Logging)
The following figure shows how Log Manager works with other components when quorum
logging is enabled (when a node is down).
Log Manager and Other Components Supporting Quorum Logging
When a node is down, quorum logging is enabled, which means Log Manager receives
configuration changes collected by other components (such as Database Manager) and logs the
changes to the quorum resource. The configuration changes logged on the quorum resource are
then available if the entire cluster goes down and must be formed again. On the first node
coming online after the entire cluster goes down, Log Manager works with Database Manager to
make sure that the local copy of the configuration database is updated with information from the
quorum resource. This is also true in a cluster forming for the first time — on the first node, Log
Manager works with Database Manager to make sure that the local copy of the configuration
database is the same as the information from the quorum resource.
Diagram and Description of Event Log Replication Manager
Event Log Replication Manager, part of the Cluster service, works with the operating system’s
Event Log service to copy event log entries to all cluster nodes. These events are marked to show
which node the event occurred on.
The following figure shows how Event Log Replication Manager copies event log entries to
other cluster nodes.
How Event Log Entries Are Copied from One Node to Another
The following interfaces and protocols are used together to queue, send, and receive events at the
nodes:
• The Cluster API
• Local remote procedure calls (LRPC)
• Remote procedure calls (RPC)
• A private API in the Event Log service
Events that are logged on one node are queued, consolidated, and sent through Event Log
Replication Manager, which broadcasts them to the other active nodes. If few events are logged
over a period of time, each event might be broadcast individually, but if many are logged in a
short period of time, they are batched together before broadcast. Events are labeled to show
which node they occurred on. Each of the other nodes receives the events and records them in the
local log. Replication of events is not guaranteed by Event Log Replication Manager — if a
problem prevents an event from being copied, Event Log Replication Manager does not obtain
notification of the problem and does not copy the event again.
Diagram and Description of Backup and Restore Capabilities in Failover Manager
The Backup and Restore capabilities in Failover Manager coordinate with other Cluster service
components when a cluster node is backed up or restored, so that cluster configuration
information from the quorum resource, and not just information from the local node, is included
in the backup. The following figure shows how the Backup and Restore capabilities in Failover
Manager work to ensure that important cluster configuration information is captured during a
backup.
Backup Request on a Node That Does Not Own the Quorum Resource
DLLs Used by Core Resource Types
A number of DLLs that are used by core resource types are included with server clusters in
Windows Server 2003. The resource DLL defines and manages the resource. The extension DLL
(where applicable) defines the resource’s interaction with Cluster Administrator.
Core Resource Types and Their Associated DLLs
File Description
Cladmwiz.dll Cluster Administrator Wizard
Clcfgsrv.dll DLL file for Add Nodes Wizard and New Server Cluster Wizard
Clcfgsrv.inf Setup information file for Add Nodes Wizard and New Server Cluster Wizard
Clnetres.dll Resource DLL for the DHCP and WINS services
Clnetrex.dll Extension DLL for the DHCP and WINS services
Cluadmex.dll Extension DLL for core resource types
Cluadmin.exe Cluster Administrator
Cluadmmc.dll Cluster Administrator MMC extension
Clusres.dll Cluster resource DLL for core resource types
Clussvc.exe Cluster service
Debugex.dll Cluster Administrator debug extension
Mqclus.dll Resource DLL for Message Queuing
Resrcmon.exe Cluster Resource Monitor
Vsstask.dll Resource DLL for Volume Shadow Copy Service Task
Vsstskex.dll Extension DLL for Volume Shadow Copy Service Task
Wshclus.dll Winsock helper for the Cluster Network Driver
The following table lists log files for server clusters.
Log Files for Server Clusters
Community Content