Hi guys !!

I am looking for information about Windows Failover Cluster - Architecture. I need deep inside info.

Somebody know where find this? I cant find info about CLIUSR account, low level Networking, dlls, so on. (A customer wanto to rename CLIUSR account).

Thanks in advance,

JD

We have a Server 2012 R2 Cluster running our production VMs, and were looking at removing the need for our last physical DC. We have two other DCs running as VMs. However testing whether the cluster would start without any DCs running completely failed.

I even tested this is a completely new testlab environment and had exactly the same result. The cluster wouldn't start unless there was a DC running.

So what's going if all of Microsoft's documentations seems to suggest that this is no longer a requirement due to the addition of AD-less Cluster Bootstrapping???? Was it added in Server 2012 and then removed in R2, doesn't make sense?

Andrew

Andrew France - http://andrewsprivatecloud.wordpress.com

Dear Microsoft Employees,

could you please answer the following question:

A customer of me plans to deploy a new File Server Cluster. The plan is to deploy 2 physical boxes and 2 virtual Servers as a 4-node Cluster.

My question: is it officially supported, to use the Windows Storage Server 2012 R2 Standard for the physical Servers and Windows Server 2012 R2 Standard for the virtual Servers? The customer is fully licensed with Server 2012 R2 for the virtual Servers and has appropriate CALs already purchased. The Background of the question is to save money when purchasing the physical servers (approx. 800€ für Server Standard vs. approx. 400€ for Storage Server Std.).

Thank you!

Kidn regards, David

i have Windows Server 2012 R2 and the cluster services is down if i do restart for it , it will work for 30 Second then go down again when i checked the event viewer i found the main reason behind this the below error but i don't know How i can fix it i believe it is related to Windows batch or update something like this but what it is i don't know so please i need your urgent help 

ERROR :

Mustafa EL-Masry Principal Database Administrator & DB Analyst SQL Server MCSE, MCSA, MCITP, MCTS http://mostafaelmasry.com/

Hi everybody and thank you in advance.

Environment:

• I have 2 separate servers (physical) each running Windows Server 2012 R2.
• Each one having its own local storage attached via DAS using HBAs (SATA SSD Drives). None of the disks are replicating to the other host, so completely separate. I used Storage spaces to create a storage pool on each server, so the volumes are the sizes I want.
• I enabled MPIO for iSCSI devices only
• I created a windows failover cluster with no special configuration.

Issue:

The cluster took the storage spaces and made them clustered storage spaces. In server manager the storage pools show that they are available to the cluster, but managed by both servers (both are listed under each one). The pools are not replicated, so of course this presents a problem.

When running validation tests, the cluster takes each node offline and detaches each one of the virtual disk during the test. This is where the problem is occurring as it is detaching virtual disks that are not replicated, so it causes programs installed on these storage spaces to crash instantly.

Question:

How do I remove the storage spaces from being clustered? I have searched the web, searched each cmdlet matching *cluster*, *disk*, removed the cluster and re-added it, created on completely separate hosts which produce the same result. I tried creating the stroage pools after the cluster has been created, but the premordial storage is owned by the cluster even though none of the disk ids match up across the 2 host, so I am lost and frustrated beyond belief. Any advice would trully be appreciated. Searching here and google and everywhere returns "How to...storage spaces" which I'm not looking for how to create storage spaces. Thanks again. Here is a screen shot of how it detaches the virtual disks while running the validation tests.

Hi. I have 2012R2 cluster configured for CAU in self-updating mode with both WindowsUpdate and Hotfix plugins. The configuration went fine, however when I try to run CAU using these options, it will fail with the error "The plug-in argument HotfixRootFolderPath has invalid value".

I've repeatedly checked that the path is correct and browsable and has all the correct permissions it should have. I've tried with both DisableAclChecks True/False, didn't make a difference. The path contains a space, so I've tried enclosing it in double-quotes, that didn't help either.

I've ran CAU from the GUI, here's the command it generates:

Invoke-CauRun -ClusterName cluster01 -CauPluginName 'Microsoft.WindowsUpdatePlugin','Microsoft.HotfixPlugin' -CauPluginArguments @{ 'HotfixConfigFileName' = 'DefaultHotfixConfig.xml'; 'DisableAclChecks' = 'False'; 'HotfixRootFolderPath' = '\\fileserver\CAU\Windows Server 2012 R2\Hotfixes\Hyper-V\Root'; 'IncludeRecommendedUpdates' = 'True'; 'RequireSmbEncryption' = 'True' } -MaxFailedNodes -1 -MaxRetriesPerNode 3 -EnableFirewallRules -FailbackMode Immediate -Force

The root folder contains DefaultHotfixConfig.xml per documentation and also there's CAUHotfix_All folder (currently empty as there are no hotfixes I need to install).

As I've said above, I tried modifying the path in the command above to 'HotfixRootFolderPath' = '"\\fileserver\CAU\Windows Server 2012 R2\Hotfixes\Hyper-V\Root"', which didn't help.

Any idea what's wrong?

I am running 5 Hyper-V 2012 R2 Clusters and working to get CAU running properly with the Hotfix plugin.  The updating is working fine, updates are applied appropriately with folder rules for installing third-party driver updates.  However, the hosts are not rebooting after the driver update even though the installer is returning 3010, update successful reboot required.

The report is complaining that CAU can not determine if rebooting the host would break quorum or not, so it skips the reboot.

Running CAU with the windows update plugin behaves as desired, including rebooting the hosts so I do not believe this is a problem with the cluster setup.

Here is the output of the report with the error I am getting:

<NumberOfFailedUpdates>0</NumberOfFailedUpdates>
  <NumberOfSucceededUpdates>1</NumberOfSucceededUpdates>
  <Status>Succeeded</Status>
- <TransientInstallErrors z:Id="61" z:Size="1">
- <ErrorRecordData z:Id="62">
  <Category>OpenError</Category>
  <ErrorDetails xmlns:d8p1="http://schemas.datacontract.org/2004/07/System.Management.Automation" i:nil="true" />
- <ExceptionData z:Id="63">
- <Data xmlns:d9p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" z:Id="64" z:Size="1">
- <d9p1:KeyValueOfstringanyType>
  <d9p1:Key z:Ref="18" i:nil="true" />
  <d9p1:Value z:Id="65" xmlns:d11p1="http://www.w3.org/2001/XMLSchema" i:type="d11p1:boolean">true</d9p1:Value>
  </d9p1:KeyValueOfstringanyType>
  </Data>
  <ErrorCode>-2146233088</ErrorCode>
  <ExceptionType z:Id="66">Microsoft.ClusterAwareUpdating.ClusterUpdateException</ExceptionType>
- <InnerExceptionData z:Id="67">
  <Data xmlns:d10p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" z:Id="68" z:Size="0" />
  <ErrorCode>5005</ErrorCode>
  <ExceptionType z:Id="69">System.ComponentModel.Win32Exception</ExceptionType>
  <InnerExceptionData i:nil="true" />
  <Message z:Id="70">A cluster node is not available for this operation</Message>
  <NeutralMessage i:nil="true" />
  <StackTrace z:Id="71">at MS.Internal.ClusterAwareUpdating.FailoverClusterImpl.FailoverClusterNodeImpl.ClusterControl(Int32 controlCode, Byte[] input, Int32 startingBufferSize) at MS.Internal.ClusterAwareUpdating.FailoverClusterImpl.FailoverClusterNodeImpl.FailureWillBreakQuorum() at MS.Internal.ClusterAwareUpdating.FailoverClusterImpl.NodeFailureWillBreakQuorum(String nodeName)</StackTrace>
  </InnerExceptionData>
  <Message z:Id="72">Could not determine if updating node "cluster-node01" would cause the cluster to lose quorum: (Win32Exception) A cluster node is not available for this operation</Message>
  <NeutralMessage z:Id="73">Could not determine if updating node "cluster-node01" would cause the cluster to lose quorum: (Win32Exception) A cluster node is not available for this operation</NeutralMessage>
  <StackTrace z:Id="74">at MS.Internal.ClusterAwareUpdating.FailoverClusterImpl.NodeFailureWillBreakQuorum(String nodeName) at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.<_RebootNode>d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.<_InstallFirstOrderUpdates>d__31.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.<>c__DisplayClass3f.<<_InstallUpdates>b__3a>d__41.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.Retrier.<>c__DisplayClass91.<<RetryAsync>b__90>d__93.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand.Retrier.<RetryAsync>d__96`1.MoveNext()</StackTrace>
  </ExceptionData>
  <FullyQualifiedErrorId z:Id="75">QuorumCheckFailed,Microsoft.ClusterAwareUpdating.Commands.InvokeCauRunCommand</FullyQualifiedErrorId>
  <InvocationName z:Ref="30" i:nil="true" />
  <ScriptStackTrace z:Ref="31" i:nil="true" />
  <TargetObjectString i:nil="true" />
  </ErrorRecordData>
  </TransientInstallErrors>

I have searched on the errors but am having no luck.  Any help would be appreciated.

Hi,

I have a question regarding Windows 2012 Failover clustering.

We have Windows 2012 running with Exchange 2013 DAG. 8 nodes 1 witness server 

There are few instances where one of the nodes lost the quorum due to network issues.  When ever that happens cluster service goes in restarting (crashing).  I tried to change Cluster service to manual and then start it but, it just keep crashing until I restart the server after that it works fine that node once again gets added into the quorum without any issues.

My question - Is it normal behavior if node lose the quorum cluster service keep restarting until you restart the server?  Or is there any way to bring back that server in the quorum without restart of the server.

clussvc.exe version 6.2.9200.21268

Error

The Cluster Service service terminated unexpectedly.  It has done this 15 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

Thanks,

Raman

I have 2 HP DL380's that are running hyper-v on W2K12R2.  One machine has a PDC and Exchange 2007 VM and the other has a BDC and file server VM.  Both the Exchange VM and file server are connected to dedicated drives on a Dell 3200i SAN.  There are various other servers as well but they don't concern me.

Can I add failover clustering to both servers now, even with an existing hyper-v installation?

If I can, can I import the existing VMs into the cluster so they will fail over automatically?

Are there any special issues to be aware of regarding the 2 VMs that are connected to their own SAN drives?

Thanks in advance for your time...

We had 2 Windows 2008R2 servers using Windows Clustering Services to create a HA SQL Server instance. They are using iSCSI shared storage. One of the servers failed to rejoin the cluster after a reboot and has been shut down. The failed server appeared to have been removed from the cluster correctly. The remaining server was working fine until it too was reboot and now the cluster won't start. 

The Cluster Management recognizes there is still a cluster and that the working server is a member node. The Cluster Service can be started but the cluster itself never initializes. Using Force Cluster Start fails.

I get errors like this:

Node 'SERVERNAME' failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available.

One problem I can see is that the shared iSCSI volumes (Quorum, Data etc.) are mounted on the remaining server but marked as Reserved, Offline, Read-only and Clustered. I assume that to resolve the issue I need to get them online on the remaining working member of the cluster but can't figure out how. Here is the Diskpart output (Disk 0 is the boot drive, Disk 1-4 are the clustered drives):

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online           50 GB  1024 KB
* Disk 1    Reserved        200 GB  1024 KB
  Disk 2    Reserved       1545 MB  1984 KB
  Disk 3    Reserved        100 GB  1024 KB
  Disk 4    Reserved       1545 MB  1984 KB
DISKPART> select Disk 1

Disk 1 is now the selected disk.

DISKPART> attribute disk
Current Read-only State : Yes
Read-only  : Yes
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : Yes

As you can see from the output I can't clear the Read-only or the Clustered Disk state. How do I resolve this?

Thanks,

Daniel.

Hi

I'm looking to create a new Hyper-V cluster for 4 VMs running on two hosts (either host able to handle that load of the 4 VMs of course). I'm planning to use a couple of IBM x3650's with a Storwize V3700 SAN. I was planning to add SAS HBA's to the servers and use SAS connections to the SAN. My question is, does Windows 2012 R2 Clustering feature support a SAS-connected SAN? All the vids/blogs I've found only mention iSCSI and FC.

Thanks 

Dear all,

I have a 2-Nodes Fail-over Cluster running on top of a HP Store Easy 1430 8 TB SATA Storage that needs to be re-installed. I have 4 VMs running there, how do I do?

What will happen with the two nodes when I format the storage and re-install, they will continue being able to see the CVS and boot the VMs?

I mean, I want an idea on how to do this please.

Regards,

Nelson Chamba\

nelson chamba

Hi All,

The our exist setup have one cluster for two Nodes, each node have 4 network interface make two NIC as teaming finally we have for each nodes Two network teaming name [ Management & Production]

Cluster network:

Assigned  "Management" 10.10.8.0/21 as cluster network only.

VLAN setting for Teaming:

"Management" assigned to VLAN ID:10

"Production"     assinged to VLAN ID: default   ( have multi Vlan's like [20,21,30,31,110,120,40,26,27,24])

All our VM's machines connect to "Production" network  in this case if "Production" come down interface that mean all VM's on one node will be stay in the same node without any task of fail-over clustering which mean they doesn't have any connectivity network and it will work as local VM's in one node.

Now my request how can I add the "production" network to be second NIC in cluster network and the same time all VM's which work with different VLAN's likes [20,21,30,31,.......]?

Please if need any more information ?

Thank you.

Hasanain Ghanem

I have a two node cluster, all 2012R2,

some day one node system crash in loop boot, therefore I wipe it.

today I choose the Stop cluster in failover cluster manager, but I found I can not connect to this cluster in failover cluster manager later time, It always connect to the wiped node to start the cluster but that node has gone :(, how I need to do to start this cluster node

We have a cluster with Windows Server 2012 R2.

When we create a share inside another share, the Sharing tab is very slow to appear (about 2 minutes).

We thought it is because the root folder has many subfolders, but with an empty root folder the behavior is the same.

Does anyone know how to fix this behavior?

Hi

Server 2012 R2

I am wanting to set up Failover clustering with 2 nodes connected to a Dell MD3400 storage array using SAS (not iSCSI).  The disks are a mix of SSD and SAS drives and  have been configured as 2 disk groups (LUN 0 for all the SSD drives and LUN 1 for all the SAS drives).

Reading up on 2 node Failover clusters suggests that a Witness disk is need for Quorum and this should be a "Dedicated LUN that stores a copy of the cluster database" (https://technet.microsoft.com/en-GB/library/jj612870.aspx).  Other resources suggest a Witness disk of 1GB.  My questions are:

1. Would the prefered location for the Witness disk be on the SSD or the SAS drives
2. Should I reconfigure my Storage to have a separate LUN for the Witness disk or would a 1GB 'drive' suffice?

Thanks
Tony

Hi Everyone,

I got one issue with Hyper-V Replica:

From a single-host I am replicating VMs to a Cluster. So far, so good.
After adding more Nodes to the Cluster, these can't receive the replication. One example:

Trying to enable the replication from single-host, I get an error that the replication can't be enabled. Clicking ok and trying again and again, it will go through the cluster nodes until it finds one that is properly configured.

Network access has been checked, local firewalls as well. Any idea regarding this behavior?

Thanks,
Jens

jensit.wordpress.com

Hi All.  I'm trying to troubleshoot an apparent network issue on our 2 node failover cluster, and have found that on one of the nodes, the status of the NIC team is "Host Unmanageable" in Server Manager.  In Local Server properties, it shows that NIC Teaming is Disabled.  

Additionally, the NIC Team is actually active and I'm not seeing any obvious connectivity issues (this team is being used by 3 vNICS for Live Migration, CSV and Management networks).  The cluster fully passes the Network portion of the Cluster Validation with no issues.  Additionally, the MsLbfoProvider Operational log has no errors over the last 2 years.  I can't find any logs that pinpoint when exactly this happened.

The issue we're having, and I'm not sure if it's related or not, is that I can't transfer ownership of any of the CSV disks from this node to the other.  If I manually disable the vNIC for the CSV network, I see the quorum disk attempt to move to the other node, but then it goes offline and the entire cluster disappears, as does access to all the CSV disks that are owned by this node.  Again, I'm not sure if this is related to this teaming issue or not.

I've seen a couple of posts regarding the "Host Unmanageable" status, but in those situations, the team isn't functioning and there are blatant connectivity issues.

I'd rather not recreate the team because the current issue with the cluster means the entire cluster has to be shut down (there's 30 VMs on it.)  Of course if I have to I will.

Does anyone have any suggestions on what I can do?  I've attached a few screenshots which might be helpful.  Thanks!

George Moore

I have 2 physical servers. 

I need to have a failover system so when the first server fails it will activate the second server. 

What i have done is: 

On both physical servers i have installed hyper-v and created VMs to make DC in each one. Connected the physical servers as members of these DCs and made a cluster between the physical servers. 

What i need to know is how can i make it 100% proof so that it fails over. I will install a postgresql server in a HD which is in the first server and will make it a ISCSI target which the second server sees. 

Will that failover correctly with this scenario? 

What can i do to make sure the system fails over and the users can connect if the system fails and i only have 2 servers?

hi all,

Setup 2x Windows 2012 R2 VMs on VMware to host a SQL cluster.

I've setup 4x volumes on Dell Equallogic and presented them to the VMs (DB, DBBackups, DBLogs and Quorum). Brought the disks online, initialized, formated and created volumes.

In Failover Cluster mmc I have added the disks to the cluster and set them up as CSV (apart from Quorum).

QUestions:

1) Once this has been done, do I go to the disk owner and assign a letter, then offline/move the disk to the other node and assign the same driver letter?

2) On C:\ClusterSTorage can I rename the Volume1, Volume2, etc to whatever is meaningful to me (identical on both nodes)?

Comments are appreciated.