Have a two node Exchange 2007 cluster (windows sever 2008 r2) currently using WWN and cluster is presented Netapp storage. We are changing out Storage to ZFS and using ISCI initiator (IQN) for new Storage group databases and Log Luns.
Question:
would adding Isci iqn with wwn already setup mess things up?
Hi
we have the server geting rebooted by a bugchk error for netft.sysPlease let me know if we have any fix for this issue. i am not sure wht is causing the issue on the server
the server is windows 2008 R2 Datacenter and it is on the HyperV cluster
Thanks in advance
Hi,
I am not able to rename my cluster network name. I have configure cluster on server 2008r2 using HP MSA 2040 SAN storage, when ever I change my cluster host name after restart the service same name is displaying. Kindly help me.
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
Hi all
We have Hyper v 2012 r2 cluster , if we restart the Hyper v Virtual Machine Management Service on one of the node , does this effect the running virtual machines on this node or we want to move the virtual machines first to another node then restart..
Regards
We are running a 2012 Hyper-V cluster managed primarily by SCVMM 2012 R2 and as a backup Failover Cluster Manager.
I have installed Windows 10 RSAT (WindowsTH-KB2693643-x64.msu) and been testing I can again manage our various services with my Windows 10 client.
When trying to connect to either of our 2012 Hyper-V cluster I get the following:
Connection Not Supported
Cluster XXXXXXX not supported
The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager
On each host Failover Cluster Manager connects without issue.
I have traced the connections, checked firewalls, checked WMI and RPC etc and cannot find an issue.
My colleagues can connect with v6 of Failover Cluster Manager.
If I try connect without appropriate credentials I does fail for not enough privileges so I can see it does talk to the cluster.
Any thoughts? Next step? Bug?
## UPDATE ##
I lab'd this by creating very simple no setup 2012 R2 DC, 4 hosts 2 of which created a 2012 R2 cluster and the other two created 2012 cluster. I was able to connect fine to the 2012 R2 but had the same issue with the 2012 cluster. I will play with the lab in hope it is not a missing feature of the latest RSAT/FOCM.
What is cluster and types , Use of clusters
What are common issue in cluster and Most common event ids and how to resolve the issues.
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,
I am trying to add third node to a Windows 2012 fail over cluster, but gets the following error.
The server 'DR.domain.com' could not be added to the cluster.
An error occurred while adding node 'DR.domain.com' to cluster 'domain-fc'.
Keyset does not exist
The User I am using to Add Node is Domain Admin, so it may not be a permission issue.
All nodes are Windows 2012 R2 VMs on Azure
Usman Shaheen MCTS BizTalk Server http://usmanshaheen.wordpress.com
I keep getting this error. I am using the Microsoft iSCSI Initiator to connect to a MSA 2040. I am trying to figure out how to fix this issue.
Two disks have been found on node 1 that cannot be distinguished from one another. The disks involved have disk signature 98ce4f1c, SCSI page 83h VPD descriptor 600C0FF00025A142################, SCSI page 80h VPD Serial Number 00c0ff25a1420000################. Please verify the storage configuration. You must either mask (unpresent, detach) one of these LUNs at this node, or, run validation and specify a disk list that includes only one of these disks, for example by using the Test-Cluster cmdlet in Windows PowerShell.
Hi,
We have setup a two node Guest Cluster in Hyper-V 2012 and have created a File Server role that will hold general user data (Roaming Profiles, Redirected Folders, etc.).
We have created shares for the Profiles and Documents folders with the default security settings. We then used RoboCopy to copy the existing Profile and Documents data to the new shares.
When testing users logging onto to the system (with Group Policy using the new server name) we get a couple of problems:-
1) A second Documents folder is created in additional to the existing one with the users data in it
2) The users Roaming Profile is unable to be loaded from the new server and a local version is used
We've been looking at the various security settings and everything "appears" OK but obviously something is wrong to cause the above problems?
Has anyone else had similar problems and know what we might need to do to resolve these problems?
Cheers for now
Russell
I've just completed the setup of a new two node Guest Cluster that resides on a two node 2012 R2 physical Cluster running Hyper-V.
The Guest Cluster seems fine and we've been using it in anger for a few days when a duplicate IP address caused the Clustered Resource (File Server) to fail.
The cluster Manager showed that the second Guest Cluster node was online but the first one wasn't. On further investigation I found that the first Cluster Node VM wasn't detecting the domain that it had previously been connect to. Nothing I could do would get it to detect the domain Network until I moved it to the other physical node and then it worked fine.
Moving it back again to the first physical node results in it losing the domain network association.
Has anyone else come across this or got any suggestions on how I can get this working again?
Cheers for now
Russell
Hi,
I am looking for a solution/script to get notified when windows 2012 cluster has failed over to another node, without using any 3rd party software.
Thank you,
TFaraj
Hello Everyone,
i'm using windows 2012 R2 failover cluster, can anyone help me to understand how manyRTO occurred on the network that initiate the failover to another Node.
Hello.
I have some 3 VMs on a Hyper-V server(2012 R2) which is part of a Failover Cluster.
These machines are not highly available, but I would like to have them highly available, added to my cluster.
These VMs have 4-5 snapshots and when the snapshots were taken, there was an ISO file mounted, from a drive which no longer exists.
When I try to create a role of HA VM in the cluster, I select the VM which is not HA and I get the error as in the title.
I tried to see how to remove the ISO file from snapshots, but the only solution I found was to delete snapshots which is not possible as I need those snapshots.Is there a powershell solution to get rid of the ISO file from the snapshots? Is there another solution to do this?
Thank you,
Gabi
Hi all,
I am new to the concept of clustering, so please enlighten me.
I manage a domain with 5+ RD session host servers and 10+ misc admin/support servers (DC, file servers, webservers, RD Gateway etc). All servers are running windows server 2008 R2, domain functional level at 2008 R2. RD session hosts serve heavy
computational tasks, very little web/network activities (mainly through RD Gateway for RD traffic).
Now I am considering to reorganize the domain to provide high availability and load balancing for RD session hosts.A planned investment of 2 high-powered servers with a central storage device (Direct Attached Storage with mixed SSD and SAS disks) is considered.
I am inclined to deploy VDI remote desktop solutions to 30+ users.
I am considering a 2-node clustering, with a common DAS storage. From what I have read, in a failover clustering scenario, one node is idle/passive and another node is active in normal operation. Should one node fails, another kicks in and all VMs would be moved to the active node. This seems a lot of wasted hardware. I have less pressure for downtime (not required to have operational status 24/7), but more for computational power.
So I am interested in mostly a load-balancing cluster with failover feature. My questions are these:
1. Can I achieve the goal that VDI vms are evenly distributed to the two nodes in normal operation? At the same time when one node fails, all VMs can be moved to the other nodes without down time?
2. Is it correctly understood to say that the clustering is archived at physical server level, that is, two identical physical servers are configured in cluster mode, with access to the storage device as Cluster Sharing Volume. On top of each physical servers, hyper V visualization hosts are installed and provision the vms. While load balancing is achieved by RD connection broker to distribute VMs across two visualization hosts.
3. so my ideal configuration would be like this (from bottom to top):
Node1 || Node2
physical server1 || physical server2
hyper V host1 || hyper V host2
RD connection broker1 || RD connection broker2
VM1-VM10 || VM11-VM20
In case of failure of say Node1, all VMs will be moved to Node 2 for continuous operation.
Can this configuration be achieved? Please correct me if I have misunderstood the concepts. What requirements are there to achieve this?
Thank you very much.
We have a 2 node 2012 R2 cluster running on a Dell VRTX chassis with M620 Blades. Cluster Storage is a 10 TB shared chassis storage and a 21 TB iSCSI Synology NAS. Cluster, Live Migration, Management and iSCSi are all on their subnets. We have about 30 VMS on the cluster. The Quorum and the chassis storage CSVs are owned by node #1. The iSCSI CSV is owned by node #2.
Cluster is functional and Live Migration works fine as long as both nodes are running.
Here’s the problem I have discovered: I need to shutdown node #1 to do some Dell recommended troubleshooting (1 port on a dual port Intel 10 gig pci card is receiving but not sending packets, but that’s another story.)
So it seems node 2 is having problems talking to the Quorum 2 out of 3 CSV disks when node 1 is missing. Definitely not very redundant!
When we built this cluster a year and a half ago, everything was validated and working flawlessly. The problems seemed to begin after a long lasting blue screen issue on node #1 which was finally traced to a bad fan on one of the 10 Gig NICs. I suspect a networking issue, but when I run the Cluster Validation, the only issue that pops up is a connection issue to our iSCSI drive (because we have a bad port on one of our NICs, working with Dell on that now.) The iSCSI CSV is owned by node #2 and doesn’t go offline when node #1 is rebooted.
Can anyone offer any insight?
Thanks!
George Moore
Hi guys
can the clustering done between two different os such windows server 2012 and windows server 2008