Are there different requirements for failover clustering between Windows Server 2012 and 2012 R2?
It appears that requirements are the same according to TechNet link below.
http://technet.microsoft.com/en-us/library/hh831579.aspx
Thanks,
Joseph
Joseph Kejr
Hello,
I have a 2 node cluster (for SQL services).
One of the 2 nodes keeps giving an error in the error log every 15 minutes.
Actually there is an error and a warning:
ERROR eventid (1196):
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS server failure.
WARNING eventid (1578):
Error retrieving the event description.
This error is only thrown by node2 of the cluster and has done this right from the creation of the cluster, but the cluster seems to work fine.
It mentions a DNS server failure, but there is nothing wrong with it (as far as I can see), node1 does not throw this error.
Can someone point me in the right direction to solve this?
And where does the name "Cluster Name" come from?
The only difference is a WINS entry in the NIC settings, I have added the WINS entry to node2.
So for I don't see any changes...
I have two Windows 2008 R2 VMs (ESXi) running Double-Take.
We currently have a Health-check running on our Netscaler to force a failover from the primary VM to the secondary VM if the Netscaler cannot access the an SMB share on the Primary VM.
This hasn't proven to be a good method of providing Fault Tolerance, so I am trying to cluster these two VMs using a File Share Witness.
(I should add that my client engineers this solution, I only implement according to their requirements).
The Witness share has been created on an EMC VNX. My domain account and the domain Cluster Computer Name account both have Full Control permissions on the Share.
I have installed the File Services Role as well as the Failover Clustering Feature on both VMs.
To configure the Quorum, I am selecting Node and File Share Majority (For Clusters with special configuration).
I am providing the IP address and share name in the form of \\<ipaddress>\<sharename>.
The wizard returns \\<ipaddress>\<sharename> is not a valid share path.
Reading the documentation from Microsoft, there is a statement saying that the witness share should have nothing else stored or using that share. Within the shared folder is an .etc folder with Everyone, Unix UID=0x0, and Unix GID=0x0. All three accounts have 'special' permissions, Traverse, List, Read. I am unable to delete this folder (haven't tried to take ownership) because I don't know what the impact could be.
Is it possible that this folder is preventing the share from becoming a Witness Share?
Any other thoughts, ideas?
The client did test this in their lab, but used a file share on another Windows server rather than a NAS.
Hi Folks,
Can anyone please suggest me how can I safely change the 2 node Windows Server 2008 cluster as follows:
Server A - production Node Active,
Server B - recovery Node Passive.
I will be changing the following IP address in the production node (Server A) after I fail over the mailbox to DR node (Server B):
Nic 2 Cluster Private network IP 2 (which send the mailbox replication data to DR mailbox node)
Please let me know your thoughts and comments if that is possible without causing any downtime apart from the failover from one node to another.
Thanks
/* Server Support Specialist */
Hello,
I have inherited a cluster at one of my clients that has given them nothing but headaches and is introducing more complexity than what their environment needs. The quorum configuration is Node and Disk Majority. The cluster consists of 2 nodes that share access to a SAN. The SAN stores all of the Hyper-V VMs and VHDs. The servers are all running Server 2008 R2.
Ideally I would like to get rid of the cluster altogether and just have a standalone VM host. For all you HA gurus out there, what are some of the pitfalls of removing the cluster and to be blunt, where would I begin?
Thanks,
Sean
Full error (wall of) text:
Unable to cast COM object of type 'System._ComObject' to interface type 'System.Management.IWbemServices'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{9556DC99-828C-11CF-A37E-00AA003240C7}' failed due to the following error: The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED)).
Scenario:
I have a two node Hyper-V failover cluster using a HA scale out file server as VM storage. When I attempt to create a virtual machine (through the failover cluster MMC) I get the error. If I attempt to do the same through the regular Hyper-V management console
I do not get the error. Also, I only get the error when creating the VM on the 1st node. This started happening after I rebooted the first node to get delegated permissions set on the SOFS share. Turns out a reboot was unnecessary because the 2nd node wasn't
rebooted and works just fine. But something during the reboot @#$!ed the first node between FC console and Hyper-V management.
Searches for the error turn up mostly programming sources; nothing about hyper-v or FC.
Hi,
We have a new 2012 cluster with 2 nodes. We're trying to get a backup solution (Asigra) working to back up the cluster but it requires that the ADMIN$ share on the cluster IP address is reachable across the network - which it is not. The ADMIN$ share on each physical node is reachable.
So for example -
cluster IP = 10.0.0.1 - ADMIN$ not reachable
node 1 = 10.0.0.2 - ADMIN$ reachable
node 2 = 10.0.0.3 - ADMIN$ reachable
We have a 2008 cluster with 3 nodes, where the ADMIN$ share is reachable (I can map to it fine in Windows Explorer) - but someone else set this up and they've since left the organisation.
Anyone able to suggest how we might get this working please?
thanks, Will
Hi,
I am trying to create a cluster between 2 nodes and it failing although it is passing the validation test successfully.
The error I am getting is while creating the cluster and is as follows:
Forming cluster '<Cluster_name>'.Even I have no idea where and how to cleanup the cluster nodes, and am not sure if cleaning them may fix this issue.
Any idea?
We have a new Dell VRTX server with 2 blades and shared storage.
Its my first Cluster so I'm trying to get to grips with the design and terminology.
What I want to achieve (Goals):-
Any advice on how best to configure this would be appreciated, not necessarily step by step but whether to use high availability file server?, do we use SMB?, how to best partition the storage?, how best to provide storage for file server? etc etc
I will also be wanting to make snapshots of the Hyper-V servers onto another physical server off-site just in case of a disaster.
Windows 2008 R2 enterprise and has two node for SQL 2005 cluster
node and disk majority quorum
Recently, we had hard time to bring it online when failovers.
I just check the public NIC which has "disable netbios over
TCP/IP" checked and with one WINS server.
Will this cause issue since this is not heartbeat NIC?
Thank you.
Hi,
I have 2 VMs Windows 2012 Datacenter in a fail-over cluster. Each VM resides over VMware ESXi 5.1 U1 server. Every ESXi has SAS HBA HP H221 in Pass-through mode and every VM is connected to this SAS controller.
I have 2 virtual disks connected to both VMs. Both disks are located on a DAS. I can add both disks to the cluster but when I bring them up I am receiving error message:
error code 0x80070001 incorrect function
Error ID 1069
If I disconnect both disks form SAS connection and connect them via ISCSI everything is OK.
I need to use them under SAS connection. How to fix this problem
Thanks!
Hello,
I would like to share a directory on RHEL 5 Linux server with Windows 2008 R2 server cluster having 2 nodes via NFS read only access.
Tried sharing in /etc/exports file as following, got permission denied at Windows server node when tried to open the folder after connecting to it.
/etc/exports file look like following:
/user/test_share windows_server.com(async)
Kindly let me know the best practice to accomplish this.
Thanks in advance.
Hi All,
I'm trying to configure Cluster-Aware Updating for my Windows 2012 Hyper cluster.
I have a separate management server (also Windows 2012).
First I created a prestage computer account. I changed the permission of the Computer OU so the cluster account has persmission to create computer objects.
But the configuration still failed with error:
“Unable to create the CAU clustered role because a Network Name resource could not be created. This can occur if a computer account (virtual computer object) for the role could not be created in the domain. Check the event log for more information. If the cluster name account does not have permissions to create the object, you can pre-stage a computer account in Active Directory. Then, use the Add-CauClusterRole Windows PowerShell cmdlet with the VirtualComputerObjectName parameter to create the CAU clustered role. For more information about pre-staging computer accounts, see http://go.microsoft.com/fwlink/p/?LinkId=237624.”
When I check the Computer OU I see some added computer accounts (CAUNL-C***):
So it's looks like that the permission are correct?
Hi
I'm using Windows 2012 Sp1 Standard edition . When I create the cluster on the node where I have installed Failover Clustering feature using below PowerShell line
Install-WindowsFeature-nameFailover-Clustering,Multipath-IO -IncludeManagementTools -ComputerName$host1-Credential$cre
Install-WindowsFeature-nameFailover-Clustering,Multipath-IO -IncludeManagementTools -ComputerName$host2-Credential$cre
While creating the cluster new cluster cmdlet
New-cluster-Name$clustername-Node$host1,$host2-StaticAddress$clusterIP
Installation freezes by saying Forming new Cluster .. The fix is I have to uninstall the failover clustering feature , reboot the nodes and install the feature via GUI or individually on each node using PowerShell
Can anyone suggest me what could have gone wrong . Cluster validation is passing successfully . I'm just not sure what has gone wrong . Is there a hotfix or something ? I couldn't find much on the net
Hi
I want to create multiple NLB clusters on a single network adapter on windows 2012 server to support load balancing for multiple different web sites , each with different DNS Name.(Two Hosts)
In the NLB Manager I create first Cluster and determine my hosts but when I want to create second cluster and determine my host , there is no interface .
How Can I configure multiple NLB clusters on a single network adapter?
Thank you for your help!
Best Regards
Hi all,
We have two-node Windows 2008 R2 cluster which is set up for DHCP. (two VMs on VMware)
Both public and private NICs are teamed. The private team has gateway set up and DNS set up.
The cluster failovered every other day.
What should I troubleshoot?
Thank you.
Hi ,
We are stuck in problem with our private cloud protection , when ever DPM trying to backup virtual machines the cluster shared volume i.o timeout and the disk disappeared for a moment and that cause my virtual machine rebooted unexpectedly and move to different nodes of cluster .
Follow are the configuration of my Infrastructure .
1. Windows server 2012 Cluster X 6 nodes
2. DPM 2012 SP1
Event Generated when backup initiate :
Cluster Shared Volume 'Volume2' ('CSV 7TB Cluster Disk Production') is no longer available on this node because of 'STATUS_CLUSTER_CSV_AUTO_PAUSE_ERROR(c0130021)'. All I/O will temporarily be queued until a path to the volume is reestablished.
I have applied hot fix as Microsoft recommended
http://support.microsoft.com/kb/2813630/en-us
Disabled ODX as well , because my storage doesn't support this feature .
please help me out to resolve this matter .
Best Regards,
Muzammil Ubaray
Hello,
We have a 3 nodes Hyper-v Cluster running Windows Server 2012. Recently we start having error below intermittently on a node, and the VMs running on this host and LUN will power off.
Alert: Cluster Shared Volume is no longer accessible from cluster node
Source: Cluster Service
Path: HV01.itl.local
Last modified by: System
Last modified time: 12/1/2013 12:27:18 AM
Alert description: Cluster Shared Volume 'Volume1' ('Cluster_Vol1_R6') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
The only changes made recently is we installed VEEAM on test basis for DR replication. We switched off the Veeam server and stop the Veeam Services on the Hyper-V Hosts but we are still having same issue.
We are using an EMC SAN connected via FC as Shared storage and Powerpath as Multi-Pathing. No errors were found on the SAN.
I don't think the issue is related to the number of IO as we also experienced the issue at midnight during the week-end where no one was working.
Any help would be very much appreciated.
Thanks.
Irfan
Irfan Goolab SALES ENGINEER (Microsoft UC) MCP, MCSA, MCTS, MCITP, MCT
Hello,
we have a two node cluster running server 2012R2, at the weekend we had a power failure and one of the nodes (I presume it was the active node) has a hardware failure and won't come back up. I thought this will be fine because we have another node and that would take on the work - however, in failover cluster manager the it won't connect to the cluster name, or the local node which is running. if I run the command Start-ClusterNode -FixQuorum it shows that the node is in the state of "joining" but never seems to get any further than that. I can manually start the cluster service but after a while it seems to stop.
I believe this is all because the active node is not contactable now I think what I am asking is how to make this remaining node be the authoritative active node....but I don't know what to do to make that happen.....
I would appreciate any help,
thank you
Steve