Hi,

Does this grow on an on-going basis? For example we created a 500GB virtual disk an immediately something like 5GB was used. We then added this as a CSV and created a 490GB fixed size VHD on it, which should have left 5GB. It did initially but after a few months something has grown leaving the virtual disk with only 20MB free space meaning the VMs on this disk are in a permanent paused state.

Powershell won't even let me resize the virtual disk. We use storage tiers (HDD + SSD):

I have a couple of virtual Failover Clusters that run on a physical Hyper-V 2012 R2 cluster.

They have few shared vhdx.

I need to migrate them to new physical CSV storage.

But ofcourse FCM does not allow Storage migration, because vhdx are "shared"

So how do I do that?

Seb

https://blogs.msdn.microsoft.com/clustering/2015/06/03/virtual-machine-compute-resiliency-in-windows-server-2016/

QuarantineThreshold means Number of failures before a node is Quarantined. I have some questions

1. which kind of error will count as "failures?

2. I see cluster log there something about Quarantined:

"the node experienced '3' consecutive failures within a SHORT amount of time"

what short is defining here ? 1s ? 2s ? 2 mins ? consecutive SAME KIND of failures ?

Dear All

We are facing an issue with live migration of VM. The configurations are mentioned below

1. Hyper-V on windows server 2012 R2 latest update 

2. VM have red hat 6.5 

3. Linux integration service version is 3.8.13 (Redhat builtin)

4. VM is configured with Static MAC address 

This all started after kernal update to latest kernal 1 month ago and now it 3.8.13.

As soon as we move the VM to the another node with LM, it loses network connectivity even IP. But after a reboot both IP and Network connectivity works fine. 

https://blogs.msdn.microsoft.com/clustering/2015/06/03/virtual-machine-compute-resiliency-in-windows-server-2016/

QuarantineThreshold means Number of failures before a node is Quarantined. I have some questions

1. which kind of error will count as "failures?

2. I see cluster log there something about Quarantined:

"the node experienced '3' consecutive failures within a SHORT amount of time"

what short is defining here ? 1s ? 2s ? 2 mins ? consecutive SAME KIND of failures ?

I need assistance on implementing a heartbeat network on an existing 3 node Failover Cluster.  This is my first time ever doing this and I have never even set up a heartbeat on new Failover Cluster.   So far I have:

- Cabling for the Servers

- Networking for the ports

-Existing NIC's on Server 2012r2 with the networking configured

-DNS Set up in dual configuration order of public network and then private network

How would I go about adding the heartbeat networks to the Failover Cluster and then configuring them to monitor it?

Hi everyone, 

I want to upgrade a Windows 2012 R2 guest cluster (File server) to Windows 2016. This cluster is running on Windows 2016 hosts. The VMs that compose this cluster are using shared drives (VHDS). 

The link to perform the upgrade https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade says:

"The following scenario is not supported in Windows Server 2016:
Cluster OS Rolling Upgrade of guest clusters using virtual hard disk (.vhdx file) as shared storage"

I don't think this applies to me. I think it refers to the way that Windows 2012R2 shared drives, which is different tan the way Windows 2012R2 does (Enable virtual hard disk sharing. vhdx)

Can I go ahead with the upgrade?

Thanks to everyone,

Ivan Mckenzie

We have a three node W2012 R2 Fail over cluster that has been running spotless for years with the HPE P4300 SAN but after adding the HPE Storevirtual SV3200 as a new SAN we are having iScsiPrt errors that HPE Support cannot fix, crashing VMs and also two of the three fail over nodes. 

At first everything seemed to work, but after adding additional disks on the SAN a SAN controller crashed. That has been replaced under warranty but now when moving our servers and especially SQL 2008 Servers to the SAN, problems start to occur. The VHDX volumes of the SQL servers are thin provisioned.  

Live moving of the storage worked fine for none SQL servers. For some SQL servers the servers frooze and operation was halted, so we needed to perform an offline move. Then during high disk IO and especially during backups W2012 R2 FOC started to behave erratic eventually crashing VMs and in one instance rebooting two fail over nodes, as a result of a flood of iScsciPrt errors in the eventlog:

System iScsiPrt event ID 27 error Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
System iScsiPrt event 129 warning The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\RaidPort4

the message resource is present but the message is not found in the string/message table

System iScsiPrt event ID 39 error Initiator sent a task management command to reset the target. The target name is given in the dump data.
System iScsiPrt event ID 9 error Target did not respond in time for a SCSI request. The CDB is given in the dump data.
System iScsiPrt event 129 warning The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\RaidPort4

the message resource is present but the message is not found in the string/message table
System iScsiPrt event ID 27 error Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
System FailOverClustering event id 5121 Information Cluster Shared Volume 'Volume4' ('NEMCL01_CSV04') is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network to the node that owns the volume. If this results in degraded performance, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.

After a 2 hour period of these events the FailOver Cluster services started to give errors, VMs failed and finally 2 nodes of our 3 node failover cluster rebooted because of a crash.

Sofar HPE has not been able to fix this. The SV3200 logs has occasional ISCSI controller errors but the error logging in the SVMC is minimal. 

HPE support blamed using a VIP and using Sites (a label). Both are supported according to the HPE product documentation. This has been removed and ISCSI initiator has been set to the Eth0 bond IP adresses directly. As problems persist they blamed that we are using the Lefthand DSM MPIO driver on the initiator connections to the SV3200 which is not the case. Standard MS DSM. Yes the Lefthand driver is on the system for our old SAN but not configured for the SV3200 initiator sessions, which is round robin with supset.     

We  are currently facing a legal warranty standoff.

Any pointers  or other comparable experiences with the HPE Storevirtual SV3200 SAN?

TIA,

Fred

Hi,

I just removed a storage pool from my clustered resources with remove-clusterresource and I can't find it in get-clusterresource anymore. Why is it still showing in server manager under Clusterd Storage Spaces? Did I forget to remove something?

PS C:\Users\admin> get-clusterresource -cluster ctr-bx-store-2

Name                            State  OwnerGroup                           ResourceType 
----                            -----  ----------                           ------------ 
Cluster Disk 1                  Online Srv-Store01-3-4                      Physical Disk
Cluster IP Address              Online Cluster Group                        IP Address   
Cluster Name                    Online Cluster Group                        Network Name 
Cluster Pool 1                  Online 8b1854ad-e451-4fc8-895c-3dc8b2cf2e3a Storage Pool 
File Server (\\Srv-Store01-3-4) Online Srv-Store01-3-4                      File Server  
IP Address 172.16.1.77          Online Srv-Store01-3-4                      IP Address   
Srv-Store01-3-4                 Online Srv-Store01-3-4                      Network Name 

Kind regards,

Maarten

MaartenD

Hello,

I've recently had an issue on a Failover CLuster for Hyper-V that uses CSV, the problem was during the addition of new disks to the Failover Cluster that was configured to be CSV (Cluster Shared Volumes). 

During the process some disk were removed and added again. But in some nodes of the Cluster, mount point links were not cleared and remained under C:\ClusterStorage

I've tried to manually remove, but this mount-point/link was unable to be deleted, the error was and access denied due  that the file was accesed by some process.

I was able to rename, but not delete. And after rename, I was able to add again the same volume, but the mount point/link had the same identifier.

The only workaround that I've found was perform an 'stop-clusternode' on the affected node, and when the node was stopeed I was able to remove these bad links.

Does anybody knows why this problem could happen? and there is a better workaround to avoid duplicated mount points?

Best Regards

Hello, community!

There is a new Hyper-V cluster built on W2k16 DC. I try install CAU through standard GUI and get an error:

With this error, I was a long time and googled.

1. The rights to create a computer object on the container in AD, where the accounts cluster nodes are located and the cluster account is set to FULL rights for the my cluster account HVCLUSTER1$.

2. The CAU object in AD is created, but for some reason there are several of them!

3. This duplicate CAU objects also created in DNS records without problem & register how ClusterResource.

Analysis results:

Connecting to server with domain administrator rights, but error is always the same!

Please, any ideas?

Hello,

we have a Hyper-V Cluster with two nodes Server 2012R2. So far everything is working fine. Now I found out that not all IP adresses are shown in the server manager.

Host1 VMS01:
10.10.10.11 (local LAN access)
172.16.1.11 (LM)

Host1 VMS02:
10.10.10.12 (local LAN access)
172.16.1.12 (LM)

Cluster IP: 10.10.10.10

I do not understand why:
- The cluster ip is not shown under vms02
- IP address of vms02 is not shown under vmscl

Thanks in advance for some ideas

Jens

Hi,

We’ve recently been in the process of extending a number of single site SQL failover clusters (on WS2016) into multi-site geoclusters. Our environment is a mix of physical and virtual nodes, however for the purpose of simplifying my question I will discuss a single site multi-subnet cluster which is experiencing the exact same issues as our multi-site geoclusters.

The single site, multi-subnet cluster is setup as below:

2 x nodes in network “A”

2 x nodes in network “B”

Each node is on identical infrastructure and has a “Data” network (for client and cluster communication) and a dedicated “Heartbeat” network (for cluster communication only). The heartbeat network is routable between the two subnets. Static routes have been added to each host.

When we run a validation test on a multi-site (or multi-subnet cluster) we get an error on the network validation test stating the below:

Node site1-node1 is reachable from Node site2-node1 by multiple communication paths, but each path includes network interface site2-node1 - Heartbeat. This network interface may be a single point of failure for communication within the cluster. Please verify that this network interface is highly available or consider adding additional networks or network interfaces to the cluster.

When delving deeper into the validation report it shows a failure communicating on UDP port 3343 between the two data networks at each site. We’ve ran the report numerous times and never get a network failure between the local nodes, only between different subnet nodes. We also never see a communication issue on the heartbeat network (dedicated to cluster communication).

The data network errors intermittently on the validation report. Sometimes the report will pass without any errors. Other times it will show certain cross subnet nodes can’t communicate and occasionally all nodes can’t communicate across subnets. We seem to be able to recreate the issue by simply restarting all of the cluster nodes or the cluster services on each node. Even more strange is if we reboot the nodes or restart the cluster service once we get validation errors (as above), they’ll clear for a period of time.

We’ve tested disabling the heartbeat network which we’ve created specifically for cluster communication on all nodes and then run the validation test. The tests pass successfully showing that our data > data networks between nodes and subnets/sites can communicate successfully. As soon as we reenable the heartbeat NICs and rerun the validation test it begins erroring again.

We’ve tested with a UDP port emulator, disabled the cluster service (after the validation test has reported that the cluster isn’t communicating over the data network) and then sent UDP packets over port 3343 to confirm that they can reach node that failed the validation test successfully. We’ve also run packet traces and can confirm that both tests show that the respective ports between the hosts are open. Windows Firewall is turned off on all nodes and the two subnets used don’t pass through a firewall. The hosts are also fully patched.

It doesn’t appear to be a networking issue as the packets are reaching the nodes, but for some reason the validation report is intermittently failing.

Any help with this would be greatly appreciated.

R

I have Windows 2012 R2 failover cluster with shared disk.

I have configured file server role along with 2 file shares on this cluster.

both file shares are hosted on shared disk, but after some time showing both file shares in cluster manager and allowing me to change properties etc its now suddenly doesn't show the file shares in cluster manager.

it gives error message that "no file shares are available because the file server role is offline"

but that is not true, file server role shows as online and i can access the file shares remotely using CAP hostname fine, it just doesn't show up in shares section of cluster manager.

I have tried failing over to other node, restarting cluster services on both nodes but no luck.

Hello,

We have a 3-node Server 2016 cluster, based on Dell R730 servers.All Hosts show a CPU Usage of 50% or above. TaskManager shows the correct value (around 0%)

Only 3 small test-vm's are running on those hosts. Has anyone seen this behavior?

We would like resolve this.

Regards,

Jan

Jan

Aloha everyone,

At my organization, we have a Dell VRTX M630 with two hosts, and we are using eight of the storage drives for CSV/Quorum.  We were able to load Windows Server 2012 R2 on the two hosts, then use Hyper-V Manager to create our DC1 VM.  We joined both Hypervisors to the domain, then the game plan was to create a HA cluster, after which the rest of the VMs (DC2, HBSS, ACAS, and SQL) would be created in the cluster.  We've done this on two other stacks, but this one had to be built from scratch and we ran into a fatal error while trying to create the cluster.  The error message is:

00001054.00000f4c::2019/01/12-02:51:27.899 ERR   [CORE] Node 2: exception caught (-1073741811)' because of '[CLI] GenerateKey - BCryptImportKey failed with error -1073741811'

This exception causes a fatal error.  The cluster creation process loops several times, but always ends with this error.  Does anyone know of a solution, or why I can start to look for resolution?

I was going to attach my cluster log file, but as I don't have any online storage, I couldn't do so.  I can post portions of the file, but need to know what y'all need to see. 

Thanks in advance for any and all responses

Hi Guys

Need some help.

I have following cluster configuration

- 2 Nodes ( Windows Server 2012 R2) with Hyper-V 

- Disk Share with a network share on the same subnets. Permission is given to both nodes computer account and cluster account.

- 2 Domain Controllers (One virtual which runs on the Hyper-V and one physical. Both nodes are the physical domain controller as primary in DNS settings)

If there is one node failure at a time, no problem and all resources are failed over to the other node.

The problem comes when both hosts are shut down The following happens

- If I power on only Node 1 then everything works and cluster comes online.

- If I power on only Node 2 then the cluster does not come online and I give the following error "The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, the cluster service has prevented itself from starting on this node. "

Both nodes are newly built and are identical in configuration. 

Any ideas??