How To Move Cluster Resources In Windows 2012

Commencement published on MSDN on January 16, 2019
Over the years, we have been asked about what some of the Failover Cluster resources/resource types are and what they do. There are several resources that accept been asked almost on multiple occasions and we haven't actually had a good definition to point y'all to. Well, non anymore.

What I want to do with this blog is define what they are, what they practise, and when they were added (or removed). I am only going to encompass the in-box resources types that come up with Failover Clustering. Just showtime, I wanted to explain what a cluster "resource" and "resource types" are.

Cluster resources are physical or logical entities, such as a file share, disk, or IP Address managed by the Cluster Service. The operating system does not distinguish between cluster and local resource. Resources may provide a service to clients or be an integral part of the cluster. Examples of resources would be physical hardware devices such as disk drives, or logical items such as IP addresses, network names, applications, and services. They are the basic and smallest configurable unit managed by the Cluster Service. A resource tin only run on a single node in a cluster at a time.

Cluster resource types are dynamic library plug-ins. These Resource DLLs are responsible for conveying out most operations on cluster resources. A resource DLL is characterized as follows:

It contains the resource-specific code necessary to provide high availability for instances of i or more resource types.

It exposes this code through a standard interface consisting of a set up of entry bespeak functions .

It is registered with the Cluster service to associate one or more resource type names with the name of the DLL.

It is ever loaded into a Resource Monitor's process when in utilize.

When the Cluster service needs to perform an operation on a resource, it sends the request to the Resource Monitor assigned to the resource. If the Resources Monitor does not accept a DLL in its process that tin handle that blazon of resource, it uses the registration information to load the DLL associated with the resources blazon. Information technology then passes the Cluster service'south request to one of the DLL's entry point functions. The resources DLL handles the details of the functioning and then as to come across the specific needs of the resources.

You tin can define your own resources types to provide customized back up for cluster-unaware applications, enhanced support for cluster-aware applications, or specialized support for new kinds of devices. For more than information, see Creating Resource Types .

All resource types that are available in a Failover Cluster can be seen by correct-mouse clicking on the name of the Cluster, choosing Properties, and selecting the Resource Types tab ( shown beneath ).

You lot can too go a list from running the PowerShell control Get-ClusterResourceType . Please keep in mind that all resources types may not show upwardly or have access to. For instance, if the Hyper-5 role is non installed, the virtual machine resource types volition non exist bachelor.

Then enough virtually this, let's get to the resources types, when they were available and, for some, when they were last seen.

Since there are multiple versions of Windows Clustering, this blog will just focus on the ii latest versions (Windows Server 2016 and 2019).

Windows Server 2016 / 2019

Cloud Witness (clusres.dll): Cloud Witness is a quorum witness that leverages Microsoft Azure as the arbitration point. Information technology uses Azure Blob Storage to read/write a blob file which is then used as an arbitration bespeak in instance of split-brain resolution.

DFS Replicated Binder (dfsrclus.dll): Manages a Distributed File System (DFS) replicated binder. When creating a DFS, this resource type is configured to ensure proper replication occurs. For more than information regarding this, please refer to the 3-part web log serial on the topic.

DHCP Service (clnetres.dll): The DHCP Service resource type supports the Dynamic Host Configuration Protocol (DHCP) Service every bit a cluster resource. There can be only one case of a resources of this blazon in the cluster (that is, a cluster tin support but ane DHCP Service). Dynamic Host Configuration Protocol (DHCP) is a client/server protocol that automatically provides an Net Protocol (IP) host with its IP address and other related configuration information such as the subnet mask and default gateway. RFCs 2131 and 2132 define DHCP as an Cyberspace Engineering Task Force (IETF) standard based on Bootstrap Protocol (BOOTP), a protocol with which DHCP shares many implementation details. DHCP allows hosts to obtain required TCP/IP configuration information from a DHCP server.

Disjoint IPv4 Address (clusres.dll): IPv4 Resource type that can be used if setting up a site to site VPN Gateway. It can only be configured by PowerShell, non by the Failover Cluster Manager, the GUI tool on Windows Server. We added two IP addresses of this resources type, ane for the internal network and one for the external network.

The internal address is plumbed down for the cluster network that is identified by Routing Domain ID and VLAN number. Remember, we mapped them to the internal network adapters on the Hyper-5 hosts earlier. It should be noted that this address is the default gateway address for all machines on the internal network that demand to connect to Azure.

The external address is plumbed down for the cluster network that is identified by the network adapter proper noun. Recall, we renamed the external network adapter to "Internet" on both virtual machines.

Disjoint IPv6 Address (clusres.dll): IPv6 Resource type that tin be used if setting up a site to site VPN Gateway. It tin only exist configured past PowerShell, not by the Failover Cluster Manager, the GUI tool on Windows Server. We added two IP addresses of this resources type, one for the internal network and one for the external network.

The internal address is plumbed down for the cluster network that is identified past Routing Domain ID and VLAN number. Remember, we mapped them to the internal network adapters on the Hyper-5 hosts earlier. It should be noted that this accost is the default gateway accost for all machines on the internal network that demand to connect to Azure.

The external address is plumbed down for the cluster network that is identified by the network adapter name. Call up, we renamed the external network adapter to "Internet" on both virtual machines.

Ras Cluster Resource (rasclusterres.dll): This resources object specifies where the site-to-site VPN configuration is stored. The file share tin be anywhere the two virtual machines have read / write access to. It can only be configured past PowerShell, not by the Failover Cluster Manager, the GUI tool on Windows Server. This resources type is only available afterward installing the VPN Roles in Windows Server.

Distributed File Organisation (clusres2.dll): Manages a Distributed File System (DFS) every bit a cluster resources. When creating a DFS, this resource type is configured to ensure proper replication occurs. For more data regarding this, please refer to the three-role weblog series on the topic.

Distributed Transaction Coordinator (mtxclu.dll): The Distributed Transaction Coordinator (DTC) resource type supports the Microsoft Distributed Transaction Coordinator (MSDTC). MSDTC is a Windows service providing transaction infrastructure for distributed systems, such as SQL Server. In this case, a transaction ways a general way of structuring the interactions between autonomous agents in a distributed system.

File Server (clusres2.dll): Manages the shares that are created every bit highly available. A file share is a location on the network where clients connect to admission data, including documents, programs, images, etc.

File Share Witness (clusres.dll): A File Share Witness is a witness (quorum) resource and is simply a file share created on a completely split server from the cluster for necktie-breaker scenarios when quorum needs to be established. A File Share Witness does not store cluster configuration information like a disk. It does, even so, contain data near which version of the cluster configuration database is virtually contempo.

Generic Application (clusres2.dll): The Generic Application resource type manages cluster-unaware applications as cluster resources, as well as cluster-aware applications that are non associated with custom resources types. The Generic Application resource DLL provides just very bones application command. For instance, it checks for application failure by determining whether the awarding'south process still exists and takes the application offline by terminating the procedure.

Generic Script (clusres2.dll): The Generic Script resource type works in conjunction with a script that you must provide to manage an application or service equally a highly bachelor cluster resources. In consequence, the Generic Script resource type allows you to script your own resource DLL. For more data on how to use the Generic Script resource type, see Using the Generic Script Resources Type .

Generic Service (clusres2.dll): The Generic Service resource type manages services as cluster resource. Similar to the Generic Application resources type, the Generic Service resource blazon provides only the virtually basic functionality. For case, the failure of a Generic Service resource is adamant by a query of the Service Command Manager (SCM). If the service is running, information technology is presumed to be online. To provide greater functionality, you can ascertain a custom resource type (for information, see Creating Resource Types ).

A generic service resource type is normally used to manage a stateless service as a cluster resource, which can be failed over. However, generic services don't provide much country information other than their online state, and then if they have an consequence that doesn't cause the resource to get offline, it is more difficult to detect a service failure.

Generic services should merely be used when all of the post-obit conditions are true; otherwise, you should create a resource DLL.

The resource is non a device. The generic resource types are not designed to manage hardware.

The resource is stateless.

The resource is not dependent on other resources.

The resources does non have unique attributes that should be managed with private properties.

The resource does not take special functionality that should be exposed through command codes.

The resources can be started and stopped hands without using special procedures.

Health Service (healthres.dll): The Health Service constantly monitors your Storage Spaces Direct cluster to detect problems and generate "faults". Through either Windows Admin Heart or PowerShell, it displays whatever electric current faults, allowing y'all to easily verify the wellness of your deployment without looking at every entity or feature in plow. Faults are designed to exist precise, easy to understand, and actionable.

Each fault contains five important fields:

Severity

Description of the problem

Recommended next footstep(due south) to accost the trouble

Identifying data for the faulting entity

Its physical location (if applicable)

IP Address (clusres.dll): The IP Accost resource type is used to manage Cyberspace Protocol (IP) network addresses. When an IP Address resources is included in a group with a Network Name resources, the grouping can exist accessed by network clients as a failover cluster example (formerly known as a virtual server).

IPv6 Accost (clusres.dll): The IPv6 Accost resource type is used to manage Internet Protocol version half-dozen (IPv6) network addresses. When an IPv6 Address resources is included in a group with a Network Proper noun resource, the group can be accessed by network clients as a failover cluster case (formerly known as a virtual server).

IPv6 Tunnel Address (clusres2.dll): The IPv6 Tunnel Address resource type is used to manage Internet Protocol version 6 (IPv6) network tunnel addresses. When an IPv6 Tunnel Address resources is included in a group with a Network Name resource, the grouping can be accessed by network clients as a failover cluster case (formerly known as a virtual server).

iSCSI Target Server (wtclusres.dll): Creates a highly bachelor ISCSI Target server for machines to connect to for drives.

Microsoft iSNS (isnsclusres.dll): Manages an Internet Storage Proper noun Service (iSNS) server. iSNS provides discovery services for Cyberspace Small Reckoner Arrangement Interface (ISCSI) storage area networks. iSNS processes registration requests, deregistration requests, and queries from iSNS clients. Nosotros would recommend not using this resources type moving forward as it is beingness removed from the product.

MSMQ (mqclus.dll): Message Queuing (MSMQ) engineering enables applications running at unlike times to communicate across heterogeneous networks and systems that may exist temporarily offline. Applications send messages to queues and read messages from queues.

MSMQTriggers (mqtgclus.dll): Bulletin Queuing triggers allow you to acquaintance the arrival of incoming messages at a destination queue with the functionality of i or more COM components or stand up-alone executable programs. These triggers can be used to define business rules that can be invoked when a message arrives at the queue without doing whatsoever additional programming. Application developers no longer must write whatsoever infrastructure code to provide this kind of bulletin-handling functionality.

Network File System (nfsres.dll): NFS cluster resource has dependency on one Network Proper name resource and tin also depend on one or more disk resources in a resource group. For a requite network name resource there can be only one NFS resource in a resource group. The dependent disk resource hosts one or more of NFS shared paths. The shares hosted on a NFS resources are scoped to the dependent network name resource. Shares scoped to i network name are not visible to clients that mount using other network names or node names residing on the aforementioned cluster.

Network Name (clusres.dll): The Network Name resource type is used to provide an alternate reckoner name for an entity that exists on a network. When included in a group with an IP Address resource, a Network Proper noun resources provides an identity to the part, allowing the role to be accessed by network clients as a Failover Cluster instance.

Distributed Network Name (clusres.dll): A Distributed Network Proper noun is a proper name in the Cluster that does not use a amassed IP Address. It is a name that is published in DNS using the IP Addresses of all the nodes in the Cluster. Client connectivity to this type name is reliant on DNS round robin. In Azure, this type name can be used in leiu of having the demand for an Internal Load Balancer (ILB) address. The predominant usage of a Distributed Network Name is with a Scale-Out File Server (discussed side by side). In Windows Server 2019, nosotros added the ability for the Cluster Name Object (CNO) to use a DNN. For more information on the CNO usage as a Distinguished Network Name, delight refer to the Windows Server 2019 Failover Clustering New Features blog.

Calibration Out File Server (clusres.dll): A Scale Out File Server (SOFS) is a clustered file share that tin can be accessed past whatsoever of the nodes. It uses the Distributed Network Name as the customer access point and does non use a clustered IP Address. The Distributed Network Proper noun is discussed previously.

Physical Deejay (clusres.dll): The Physical Disk resource type manages a disk on a shared coach connected to two or more cluster nodes. Some groups may contain one or more than Physical Disk resources as dependencies for other resource in the group. On a Storage Spaces Directly cluster, the disks are local to each of the nodes.

Hyper-V Network Virtualization Provider Address (provideraddressresource.dll): The IP address assigned by the hosting provider or the datacenter administrators based on their physical network infrastructure. The PA appears in the packets on the network that are exchanged with the server running Hyper-V that is hosting network virtualized virtual automobile(s). The PA is visible on the physical network, but non to the virtual machines.

Storage Pool (clusres.dll): Manages a storage puddle resource. It allows for the creation and deletion of storage spaces virtual disks.

Storage QoS Policy Manager (clusres.dll): A resources blazon for the Policy Manger that collects the performance of storage resources allocated to the private highly available virtual machines. It monitors the activity to assist ensure storage is used fairly inside I/O operation established through any policies that may exist configured.

Storage Replica (wvrres.dll): Storage Replica is Windows Server technology that enables replication of volumes betwixt servers or clusters for disaster recovery. This resource type enables yous to create stretch failover clusters that bridge two sites, with all nodes staying in sync. A Stretch Cluster allows configuration of computers and storage in a single cluster, where some nodes share one set up of disproportionate storage and some nodes share another, and then synchronously or asynchronously replicate with site awareness. Past stretching clusters, workloads tin can be run in multiple datacenters for quicker data access by local proximity users and applications, also as meliorate load distribution and utilise of compute resources.

Job Scheduler (clusres.dll): Chore Scheduler is a resources that is tied to tasks you wish to run against the Cluster. Clustered tasks are not created or shown in Failover Cluster Director. To create or view a Amassed Scheduled Task, you would need to use PowerShell.

Set up-ClusteredScheduledTask

Annals-ClusteredScheduledTask

Get-ClusteredScheduledTask

Unregister-ClusteredScheduledTask

Virtual Machine (vmclusres.dll): The Virtual Machine resource type is used to control the state of a virtual auto (VM). The post-obit tabular array shows the mapping betwixt the state of the VM (indicated by the EnabledState property of the Msvm_ComputerSystem instance representing the VM) and the state of the Virtual Car resource (indicated by the State property of the MSCluster_Resource class or the return of GetClusterResourceState function).

VM State	Virtual Motorcar resource state
Disabled	three
Offline	iii
Suspended	32769
Starting	32770
Online Pending	129
Online	2
Stopping	32774
Offline Pending	130
Saving	32773
Enabled	ii
Paused	32768
Pausing	32776
Resuming	32777

Virtual Auto Cluster WMI (vmclusres.dll): The Virtual Machine Cluster WMI resource blazon is one used when virtual machine grouping (also known every bit virtual machine sets) has been configured. By grouping virtual machines together, managing the "group" is much easier than all of the virtual machines individually. VM Groups enable checkpoints, fill-in and replication of VMs that form a guest-cluster and that use a Shared VHDX.

Virtual Machine Configuration (vmclusres.dll): The Virtual Machine Configuration resource type is used to command the land of a virtual machine configuration.

Virtual Auto Replication Banker (vmclusres.dll): Replication broker is a prerequisite if you are replicating clusters using Hyper-V replica. Information technology acts the bespeak of contact for any replication requests, and can query into the associated cluster database to decide which node is the right i to redirect VM specific events such as Live Migration requests etc. The broker as well handles hallmark requests on behalf of the VMs. A new node can exist added or removed from a cluster at any point, without the demand to reconfigure the replication as the communication between the principal and recovery clusters is directed to the respective brokers.

Virtual Machine Replication Coordinator (vmclusres.dll): Coordinator comes into picture when nosotros apply the concept of "collection" in Hyper-V replica . This was introduced in Windows Server 2016 and is a prerequisite if you are using few of the latest features for eg: shared virtual hard disks. When VMs are replicated as role of a collection, the replication broker coordinates actions/ events that bear upon VM group – for eg:, to accept a point in time snapshot which is app consequent, applying the replication settings, modifying the interval for replication etc. and propagating the change across all the VMs in the collection.

WINS Service (clnetres.dll): The WINS Service resources type supports the Windows Cyberspace Name Service (WINS) as a cluster resource. There can exist only ane instance of a resource of this type in the cluster; in other words, a cluster can support only 1 WINS Service. Windows Net Name Service (WINS) is a legacy computer proper noun registration and resolution service that maps computer NetBIOS names to IP addresses.

Windows Server 2016 only

Cross Cluster Dependency Orchestrator (clusres.dll): This is a resource blazon that you can ignore and does not do anything. This was to exist a new feature to be introduced. However, information technology never came to fruition, just the resources type was not removed. Information technology is removed in Windows Server 2019.

Windows Server 2019 simply

SDDC Management (sddcres.dll): SDDC Management is installed when the cluster is enabled for Storage Spaces Direct. It is the direction API that Windows Admin Center uses to connect/manage your Storage Spaces Direct. It is an in-box resource type with Windows Server 2019 and is a download and manual add-on to Windows Server 2016. For data regarding this, please refer to the Manage Hyper-Converged Infrastructure with Windows Admin Center document.

Scaleout Worker (scaleout.dll): This is used for Cluster Sets. In a Cluster Set deployment, the CS-Principal interacts with a new cluster resource on the member Clusters called "Cluster Gear up Worker" (CS-Worker). CS-Worker acts equally the just liaison on the cluster to orchestrate the local cluster interactions as requested by the CS-Principal. Examples of such interactions include VM placement and cluster-local resource inventorying. In that location is simply ane CS-Worker instance for each of the member clusters in a Cluster Set.

Scaleout Master (scaleout.dll): This is used when In a Cluster Set, the advice betwixt the fellow member clusters is loosely coupled, and is coordinated by a new cluster resource called "Cluster Gear up Master" (CS-Master). Similar whatever other cluster resource, CS-Master is highly available and resilient to individual member cluster failures and/or the management cluster node failures. Through a new Cluster Set up WMI provider, CS-Chief provides the management endpoint for all Cluster Set manageability interactions.

Infrastructure File Server (clusres.dll): In hyper-converged configurations, an Infrastructure SOFS allows an SMB client (Hyper-V host) to communicate with guaranteed Continuous Availability (CA) to the Infrastructure SOFS SMB server. This hyper-converged SMB loopback CA is accomplished via VMs accessing their virtual disk (VHDx) files where the owning VM identity is forwarded between the customer and server. This identity forwarding allows ACL-ing VHDx files just as in standard hyper-converged cluster configurations equally before. There can be at most only one Infrastructure SOFS cluster role on a Failover Cluster. Each CSV volume created in the failover automatically triggers the cosmos of an SMB Share with an auto-generated name based on the CSV volume proper noun. An administrator cannot directly create or modify SMB shares nether an Infra SOFS part, other than via CSV book create/modify operations. This part is commonly used with Cluster Sets.

Thanks
John Marlin
Senior Program Manager
Loftier Availability and Storage

Follow me on Twitter @JohnMarlin_MSFT

Source: https://techcommunity.microsoft.com/t5/failover-clustering/windows-server-2016-2019-cluster-resource-resource-types/ba-p/372163

Posted by: luftacte1966.blogspot.com