Hi all,

 we have already setup CAU on our cluster, how should we set windows update on each cluster node windows installation?

 Should we disable it? Or can I just leave it with "Check for updates but let me choose whether do download and install them"

 At this time, a cluster node is pausing with no apparent reason and we have each windows update set to "Check for updates but let me choose whether do download and install them".

Thanks for your help,

L. Pinho

Luis Pinho

Hi Guys!,

This is my scenario:

• 1x Storage Server 2008 R2 , Dedicate to next nodes.

            I made 3 LUN's about 100 GB each on.

• 2x Windows 2008 Enterprise R2, Hyper-V . ONLY.

        We've got 1x Network Cluster for VM, 1 Storage Network, and 1 Live Migration Network. All NIC are Gigabit.

Ok, Now here is my question.

I tried to set dependency of my CSV, ok, i will explain. I force a shutdown of NODE1 and then all CSV go to NODE2. Then the NODE1 go ON again, but CSV propietary is NODE2, I want to assign (always, except when it's shutdown ) LUN1 & LUN 2 to NODE1. And if NODE1 fail and go ON again , autoassing again LUN1 and LUN2.

Sorry for my english :(.

I tried via Powershell commands unsuccessfully.

Thanks in Advance.

MRF

Okay, this has been going on for months after we performed an upgrade on our 2008 R2 clusters.  We upgraded our development cluster from 2008 R2 to 2012 (SP1) and had no issues, saw great performance increases and decided to do our production clusters. At the time, 2012 R2 was becoming prominent and we decided to just hop over 2012, thinking changes in this version weren't that drastic, we were wrong.

The cluster works perfectly as long as all nodes stay up and online.  Live migration works great, roles (including disks) flip between machines based on load just fine, etc.  When a node reboots, or the cluster service restarts, when the node goes from "Down" to "Joining" and then "Online", the CSV(s) will switch from Online to Online (No Access) and the mount point will disappear.  If you were to switch the CSV(s) to the node that just joined back into the cluster, the mount point returns and it goes back to Online.

Cluster validation checks out with flying colors and Microsoft has been able to provide 0 help whatsoever.  We have two types of FC storage, one that is being retired and one that we are switching all production machines to.  It does this with both storage units, one SUN and one Hitachi.  Since we are moving to Hitachi, we verified that the firmware was up-to-date (it is), our drivers are current (they are) and that the unit is fully functional (everything checks out).  This has not happened before 2012 R2 and we have proven it by reverting to 2012 on our development cluster.  We have started using features that come with 2012 R2 on our other clusters so we would like to figure this problem out to continue using this platform.

Cluster logs show absolutely no diagnostic information that's of any help.  The normal error message is:

Cluster Shared Volume 'Volume3' ('VM Data') is no longer accessible from this cluster node because of error '(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.

Per Microsoft our Hitachi system with 2012 R2 and utilizing MPIO (we have two paths) is certified for use.  This is happening on all three of our clusters (two production and one development).  They mostly have the same setup but not sure what could be causing this at this point.

Hi,

I am wondering if it is possible to rename a Cluster Shared Volume using PowerShell.

When I add a disk to the cluster using "Add-ClusterDisk" and then add the cluster disk as a clustered shared volume using "Add-ClusterSharedVolume" the new cluster shared volume gets a generic name in the failover cluster manager like"Cluster Disk 3" and a generic name in the "C:\ClusterStorage" directory such as "Volume1". 

My goal is for the name in the failover cluster manager to match the name in the "C:\ClusterStorage" directory.  So I would see a cluster shared volume in the failover cluster manager GUI such as "MyNewCSV" and a path such as "C:\ClusterStorage\MyNewCSV" in the filesystem.

Is there some PowerShell command that I can use to rename "Cluster Disk 3"  in the failover cluster manager to "MyNewCSVName"?  I can rename the folder in the filesystem using Rename-Item with the following Powershellcommand"Rename-Item -Path "C:\ClusterStorage\Volume1" -NewName "MyNewCSVName" to get the directory name I want, but the CSV in failover cluster manager still uses "Cluster Disk 3" as the name.

Does anyone know if this is possible in PowerShell?  I can do it easily through the failover cluster manager GUI but really want an automated solution.

Thanks,

Paul

I'm setting up a test environment as a proof of concept.

My end goal is to have a cluster setup at each site, the DFS service to replicate datain both directions, and a namespace to point at the File Server cluster instances at each site.

Currently I have two "servers" setup as a cluster and the "File Server" role installed - a disk quorum and one data volume - connected via iSCSI.

I have a third server to represent "offsite" DFS member.

I am trying to get one of the cluster members to utilize the DFS service to replicate data, but I get an error when the DFS service attempts to initialize:  "The DFS Replication service detected that the local path of a replicated folder that is hosted by the local computer is not valid. This can occur if the local path of the replicated folder is on a volume that belongs to a cluster shared disk, but the replication group member is not a failover cluster.
Using the DFS Management MMC snap-in, delete the replicated folder 'F:\Test' from the local computer in the replication group 'TestRG'. Add the replicated folder back to the replication group with a local path that is not on a cluster shared disk. " - Event ID 9101

From what I can tell, it seems is has an issue with me using a cluster disk as a source for DFS info, but also indicates this can be done somewhow, but I have no idea how.  Will this require a third machine connected to the iSCSI disk?  Will I be able to point the namespace at the file cluster instance if I get past this?

I've been reading the forum regarding how to setup mount points within a 2012 R2 failover cluster but am still confused on correct process.

1) Create c:\MountPoint\MountPountName (have to create on each node in the cluster as c: isn't clustered so mount point root disappears once you failover).

2) Create d:\MountPoint\MountPointName (where D: is a clustered volume).  In this case I would likely have a totally separate LUN added to cluster smaller in size (1GB?) and assign drive letter like D: and use as mount point root.

I've read the following restriction for mountpoints but am unclear exactly what it means... Does this mean that option 2 to create the mount point root on a clustered drive is the correct approach?

        "A volume mount point cannot be created between clustered and nonclustered disks"

Hi All,

Cluster validate validation test pass.

Getting error while creating 2 node failover clusters.

DC on windows server 2008.

Nodes are on windows server 2008 R2 SP1. with same patch level and shared storage.

Storage is iscsi

Error while creating Cluster Virtual Object

I am having some problems recently with my clustered Hyper-V environment and need to know where to look in order to find the real problem here.  We have 13 hosts in the cluster that uses a combination of CSV (Microsoft iSCSI servers) and SMB 3.0 San storage (Not managed by VMM).  Regularly we have been seeing our Linux boxes fail with the following errors. (These are Administrative events from one of the hosts that is having the most failures)

I will be happy to provide any more information however I don't really know where to look.  I have run a validation report and it looks good as far as I can tell.  I haven't included any of the storage because I don't want to bring the clustered roles down.

Error   6/23/2016 11:13:04 AM          Hyper-V-Integration     4000   None

Hyper-V Heartbeat failed to connect to virtual machine 'AppServer' because the version does not match the version expected by Hyper-V (Virtual machine ID GUID). Framework version: Negotiated (0.0) - Expected (3.0); Message version: Negotiated (0.0) - Expected (3.1). To fix this problem, you must upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Warning 6/21/2016 9:42:27 PM Hyper-V-Worker 23014 None

Device 'Microsoft Synthetic Display Controller' in 'AppServer' is loaded but has a different version from the server.  Server version 3.3 Client version 3.2 (Virtual machine ID GUID). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Warning 6/21/2016 9:42:19 PM Hyper-V-VmSwitch 27 (1019)

Networking driver in AppServer loaded but has a different version from the server. Server version 5.0  Client version 3.2 (Virtual machine ID GUID). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Warning 6/21/2016 9:42:19 PM storvsp 6 None

A storage device in 'AppServer' loaded but has a different version from the server.  Server version 6.0  Client version 4.2 (Virtual machine ID GUID). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Warning 6/21/2016 9:42:19 PM storvsp 6 None

A storage device in 'AppServer' loaded but has a different version from the server.  Server version 6.0  Client version 4.2 (Virtual machine ID GUID). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

Error 6/20/2016 3:29:18 AM FailoverClustering 1205 Resource Control Manager

The Cluster service failed to bring clustered role 'AppServer' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Error 6/20/2016 3:29:18 AM FailoverClustering 1069 Resource Control Manager

Cluster resource 'Virtual Machine AppServer' of type 'Virtual Machine' in clustered role 'AppServer' failed. The error code was '0x20' ('The process cannot access the file because it is being used by another process.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Error 6/20/2016 3:29:18 AM Hyper-V-High-Availability 21502 None

'Virtual Machine AppServer' failed to start.

'AppServer' could not initialize. (Virtual machine ID GUID)

'AppServer' failed to create or access memory contents file \\SMB3SAN\VMInfo\AppServer\AppServer\Virtual Machines\GUID\GUID.bin. (Virtual machine ID GUID)

Error 6/20/2016 3:29:18 AM Hyper-V-High-Availability 21107 None

'Virtual Machine AppServer' failed to start.

Error 6/20/2016 3:29:18 AM Hyper-V-Worker 3040 None

'AppServer' could not initialize. (Virtual machine ID GUID)

Error 6/20/2016 3:29:18 AM Hyper-V-Worker 3130 None

'AppServer' failed to create or access memory contents file \\SMB3SAN\VMInfo\AppServer\AppServer\Virtual Machines\GUID\GUID.bin. (Virtual machine ID GUID)

Error 6/20/2016 3:29:16 AM FailoverClustering 1069 Resource Control Manager

Cluster resource 'Virtual Machine AppServer' of type 'Virtual Machine' in clustered role 'AppServer' failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Error 6/20/2016 3:29:16 AM Hyper-V-VMMS 20114 None

The Virtual Machine Management Service failed to verify the running state of the virtual machine 'GUID': The system cannot find the drive specified. (0x8007000F).

Hi Guys,

Any one have idea about this error message which we are getting in our 2008 SQL Failover cluster , Before some week ago resources was not responded , we had reboot  both the nodes.

==============================================================================Event Id:- 1207

Cluster network name resource 'abc' cannot be brought online. The computer object associated with the resource could not be updated in domain 'x.coml' for the following reason:
Unable to update password for computer account.

The text for the associated error code is: Access is denied.

 
The cluster identity 'abc$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can

In current situation no issue on server , everything are working fine , but this event is coming again ad again

Please suggest how to check logs and what would be resolution of this issue

Regards,

Triyambak

Regards, Triyambak

Hi there!

We have a Windows 2012 R2 cluster node with 3 NICs:

1. NIC1 (External Public)
2. NIC2 (Migration)
3. NIC3 (Cluster Heartbeat)

My inquires are related to the Migration andCluster Heartbeat NICs only

Could you please advise, whether as a best cluster configuration practice:

1. We should uncheck TCP/IP v6 if we are using only IPv4.
2. We should uncheck "Append parent suffixes of the primary DNS suffix"?
3. We should uncheck "Register this connection's addresses in DNS" if we are not using DNS servers?
4. Any links to the related documentation would be highly appreciated!

Many thanks for your help, in advance!

Hi

One of our (rogue) offices recently started using a 3 Node Hyper-V cluster without CSV's. Our other offices only use Clusters with CSV (with no issues so far).

I told the rogue-office I'm having serious doubts about not using CSV's, but they are convinced it works. They already did succesfull tests with Live Migrating VM's without the VM's having any downtime.
It's not like they don't have a SAN. They do, connected with dual Fibre Channel to each node in the cluster. They just never created the CSV's or a seperate CSV VLAN between the hosts (just a VLAN for Live Migration). Not smart if you ask me.

So how would this work ?
And, is is supported at all by MS Services ?

And what are the downsides compared to CSVs ?

Any input is welcome.
Grtzzz

Hi first time poster here,

I have set up a two node Scaled out File Cluster and set its Cluster Shared Volume.

I believe I have successfully set up the SOFS role and created the continuous available share as I can access it but the remote speeds are capped at 4.5 GB/s for sequentials and the iops are at about 250k. 

Locally, i get 5.8 GB/s and 500k iops. 

I'm trying to find out how to make both nodes of the cluster active / active so it uses both systems to enhance performance.

In the Nodes tab, it only shows one node owning the SOFS role...I wish I could post pictures to show so.

Thank you in advanced for any feedback, much appreciated.

I encountered an issue today while trying to check available disks from cluster storage by doing add disk, after verifying disks killed add disk window in cluster instead of clicking cancel button. After add disk window was killed it still added available disks to the cluster , removed newly added disks from the cluster which caused all cluster disks to go offline and then come online one of the disks which was added had binary files of SQL server.

Did anyone encounter this kind of situation in the past? Until today i was thinking killing a window is like closing it but was surprised to see killing a window in fact did what it should be doing when we accept by clicking OK button.

This is windows 2008 cluster with windows 2008 OS and SQL 2008 R2.

How can I download FTP 8.0 installer what is supported for Windows 2012 Failover Cluster.

There is no link.

Hi,

Can anyone suggest, for windows 2012 R2 windows cluster for SQL, is it mandatory  to keep/configure the dedicated network for heartbeat? I heard that, it is not compulsory to configure dedicated NIC for private heartbeat network but want to know if any official Microsoft document available to support this.

Regards,

Hi.

First, one of cluster node is lost Witness share. After reboot servers cluster service do not started. In Event Viewer write some errors:

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

Please, help my. Say, how i can manualy remove cluster from AD and uninstall feature Failover Cluster from server.

in cluster.log file:

00001e30.00001b60::2010/12/07-15:52:25.371 INFO  -----------------------------+ LOG BEGIN +-----------------------------

00001e30.00001b60::2010/12/07-15:52:25.371 INFO  [CS] Starting clussvc as a service

00001e30.00001b60::2010/12/07-15:52:25.371 INFO  [CS] cluster service logging level is 5

00001e30.00002224::2010/12/07-15:52:25.371 INFO  [CS] Creating cluster node <vector len='1'>

00001e30.00002224::2010/12/07-15:52:25.371 INFO      <item>ClusSvc</item>

00001e30.00002224::2010/12/07-15:52:25.371 INFO  </vector>

00001e30.00000864::2010/12/07-15:52:25.371 INFO  [StartupConfig]: Initializing.

00001e30.00000864::2010/12/07-15:52:25.371 INFO  [StartupConfig]: Local node name: MSK-MAIL1.

00001e30.00000864::2010/12/07-15:52:25.371 ERR   [CS] Service CreateNodeThread Failed, ERROR_FILE_NOT_FOUND(2)' because of 'Open parameters key failed.'

00001e30.00000864::2010/12/07-15:52:25.371 ERR       000007fe:fddaaa7d( ERROR_MOD_NOT_FOUND(126) )

00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:0109f650( ERROR_MOD_NOT_FOUND(126) )

00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:00f1a260( ERROR_MOD_NOT_FOUND(126) )

00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:ff96a368( ERROR_MOD_NOT_FOUND(126) )

00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000000:0109f5c0( ERROR_MOD_NOT_FOUND(126) )

00001e30.00000864::2010/12/07-15:52:25.371 ERR       00000001:e06d7363( ERROR_MOD_NOT_FOUND(126) )

Hello, I'm experiencing the following problem on a two nodes WS2012 failover cluster, starting when I did the first setup. After 10-12 days up, I cannot connect anymore with failover cluster manager, I get "invalid query". Also, if from one of the hosts I try to connect to hyper-v manager, I get an error related to missing permissions. In the logs I cannot find anything relevant (please note that guest VM are always up&running also if I cannot connect to the cluster). I configured on the two nodes a powershell script in order to periodically send an email with the output of the command "get-clusterresource" and this morning I noticed I didn't receive the email. So I tried to run locally this command on an elevated Powershell prompt and I got "AuthorizationManager check failed". Searching online, I found that it could be a WMI problem, so I restarted the "Windows Management Instrumentation" service on the two servers and... voilà, I could connect to Failover Cluster and to Hyper-V manager. Now, I identified the process to restart to bring it back online, but I'd like to identify the cause. Any suggestion?

edit: another thing I noticed after restarting WMI process, I don't know if it is relevant

"The root\mscluster namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level"

I have 7 physical servers I am trying to arrange in three clusters and leave out the 7th server.

Four of the servers are  Hyper-V host to be two, two server clusters.

Two of the servers I am trying to make a files server cluster to use as storage for VMs of the two clusters.

The seventh server is running Hyper-V and I am using it for holding for migrations to the appropriate locations once the storage creation is completed.

All servers are running Server 2012R2. All have Teamed interfaces. All have 64 GB of memory.

The two for file services have file services and cluster services installed. They have 80 GB operating system volumes and 18 TB Data Volumes. I used cluster manager to make them a cluster. Cluster validation shows no drives available for clustered storage. Under Drives in cluster manager no drives are listed.

I have watched hours of Microsoft Videos on Hyper-V and File Services from their site,  "Microsoft Virtual Academy" and read for months everything I can find that seems pertinent.

I confess, I am still not able to figure out the exact order for my particular set of circumstances and humbly ask for anyone's assistance.

What is the order of and what roles services, etc. must I make in order to have the two server cluster have storage available for Hyper-V to use as storage? I am not unfamiliar with Hyper-V or Windows Server. I just haven't had enough hardware to try Clustering until now.

The two file server currently have no data on their DATA volumes.

I am trying to do this as simply as possible, even if it is not best practices, I would like to follow them as well as I am able with our hardware.

Hello

I have found this post: https://eightwone.com/2012/12/20/cluster-name-object-pre-staging/

And this is for Exchange.

Is there any way to do the same on SQL Server 2014 without Exchange in power shell?

I need to associate CNO with the Cluster Name Resource usnih PowerShell

Thanks