When using Microsoft Fail-Over Clustering with Cluster Shared Volumes or Clustered disks which are on a HP EVA storage box, you may run into a problem about the disk/volume only being accessible from one of the nodes of the failover cluster, usually the node on which the disk/volume was added. When trying to access the volume from another node (e.g. by moving the role using that volume to another node), the role will fail and complain that the disk/volume is not accessible. Moreover, in Disk Management, the disk is not accessible and does not show the size of the disk. This makes the use of a fail-over cluster rather useless as the role can only run on the one node that does have access to t ...
In a Windows Failover Cluster, you can move roles from one node to another node using the Failover Cluster Manager. Unfortunately, the GUI in 2008 R2 does not provide a way to move the quorum disk to another node. For this, you need to use the cluster command-line tool. This tool allows complete management of the cluster and its roles from the command-line, and this also includes moving the quorum disk.
Note that the cluster command-line tool no longer exist on 2012 and up. In that case, you need to use the Powershell cmdlets for Failover Cluster.
Each 2008R2 failover cluster comes default with two resource groups that are always present:
Available Storage contains all storage that hasn't ...
If a server that is part of a fail-over cluster and also runs SCOM 2012 agent, you may get the following alert:
Alert: Agent proxy not enabled
Last modified by: System
Last modified time: 8/10/2015 3:53:20 PM
Alert description: The agent was not able to submit data on behalf of another computer because agent proxy is not enabled. Details:Health service ( server-name ) should not generate data about this managed object ( Microsoft.Windows.Computer ).
The agent will notice the server is part of a cluster and will attempt to retrieve additional information about the cluster, which is not allowed by default.
When you create a Windows Server 2012 failover cluster, the following event may be logged in the System log:
Event ID 1222 (Microsoft-Windows-FailoverClustering)
The computer object associated with cluster network name resource could not be updated.Unable to protect the Virtual Computer Object (VCO) from accidental deletion.
When a failover cluster or a cluster role is created, a computer account (a so-called Cluster Name Object (CNO)) is created in Active Directory. Since Server 2012, these objects are flagged to prevent accidental deletion. If the main cluster resource (also a computer account) does not have the required permissions on the OU containing the CNOs (by default, this is the ...