I am not sure if I should ask this question here, but I thought I would and see if anyone yells. I am trying to get a handle on the new features of windows server; I wanted to come up with a clustered solution for hyper-v and a file server using storage pools. What I would like to accomplish is the ability to add new nodes to the cluster at different geographical areas, I would do this by creating a secured tunnel connecting each location. My question is what is the best way to do this? At this point there are only 4 total physical machines, 2 Hyper-v and 2 files server with 16TB each. I want to use storage pools for the file server. Will I have to cluster the file server as well, or can I do a DFS replication and only cluster the hyper-v servers. I am just trying to wrap my head around the best way to do this so that I can continue to add servers to the cluster to increase availability and storage, while having fail-over.

Also I know that server 2012 can work with virtual DC's, is it better to have a physical DC outside and a BDC virtually? I know about the 12% degrade in performance if I choose to use both DC's as virtual guests. Also plan to install SQL and exchange as virtual guests.

Hi,

We have a 2 node SQL Cluster and everything is configured correctly. Now there is a requirement to change the namings of the SQL Disks in Disk Management and Cluster resources to a Pre-defined standard.

I have achieved the disk management part by renaming the Volume label, however this is not getting reflected in Cluster Resources.

I do get an option to change this (as in the image), do I need to shutdown SQL or take the disks offline to this? In other words, just renaming will bring down the SQL Cluster?

Can I change the Resource Name from "Backup" to "SQLBackup"?, if this is done directly, will this have any impact to the SQL Cluster?

Thanks in advance...KK 

Sampath_Kumar

Hi,

I use windows 2008 Failover Cluster manager to create Client Access Point resource. If I try to bring resource online after creation, I get Kerberos error: access is denied. I am not managing AD environment. I guess I need some permissions, but what permissions I have to ask for AD team?

thank you,

hi,

i am in need of reliable resources about computer clustering (more academic and educational not technical ) .

please help 

thanks all

Hi, I am from Spain, excuse my bad English

I have 2008 r2 cluster with 2 nodes Windows Storage Server

When I request the FS Cluster from the client PC by UNC \\ClusterName\folder the Client get the shares and able to work normally
but when the client request cluster by IP \\192.168.0.10\folder the result is "Networkpath not found"

If i ping ClusterName the result is OK from 192.168.0.10

Is cluster file able to reply by IP instead by name?

Any sugestion?

Thanks for all

I have just set up a Windows 2008 NLB cluster.

Clustered name is Cluster1, and there are two Windows 2008 R2 SP1 nodes, Node1 and Node2. Both are the physical server.

I have set up the NLB as by follow the step from Google. My NLB is configure as muticast.

Physical Node 1                         

IP address: 192.168.10.36

gateway:192..168.10.1

------------------------------------

Physical Node 2

IP address: 192.168.10.45

gateway:192.168.10.1

-----------------------------------

Virtual IP address for NLB

IP address: 192.168.10.46

However, the clustered IP/name cannot be reached via PING from outside the subnet (192.168.20.XX)

from subet (192.168.20.XX) i can ping to gateway, ping the server in 192.168.10.XX subnet without any problem. My problem is client can not ping to NLB Virtual IP address.

I have check below these link.

http://blogs.technet.com/b/networking/archive/2009/01/15/unable-to-connect-to-windows-server-2008-nlb-virtual-ip-address-from-hosts-in-different-subnets-when-nlb-is-in-multicast-mode.aspx?PageIndex=2#comments

From the thread, it give a work around to ad ARP entry

We can add a static ARP table entry for the Default Gateway IP address on the NLB Node.

Command to add static ARP entry

Arp –s <IP address> <Mac Address>

-------------------------------------------------------

The IP address and MAC address mean is add the default gateway IP address (192.168.10.1) and MAC address in to both NLB server ?

i try to run arp -a command on both NLB server have the default gateway IP address and MAC as below

C:\Users\>arp -a

Interface: 192.168.10.36 --- 0x13
  Internet Address      Physical Address      Type
  192.168.10.1          00-00-cd-XX-XX-XX     dynamic
  192.168.10.30         ac-16-2d-XX-XX-XX     dynamic
  192.168.10.31         ac-16-2d-XX-XX-XX     dynamic
  192.168.10.33         00-9c-02-XX-XX-XX     dynamic
  192.168.10.45         ac-16-2d-XX-XX-XX    dynamic
  192.168.10.212        f8-d1-11-XX-XX-XX     dynamic
  192.168.10.255        ff-ff-ff-ff-ff-ff     static

Interface: 192.168.250.36 --- 0x1b
  Internet Address      Physical Address      Type
  192.168.250.255       ff-ff-ff-ff-ff-ff     static
--------------------------------------------------------------------------

C:\>arp -a

Interface: 192.168.10.45 --- 0x13
  Internet Address      Physical Address      Type
  192.168.10.1          00-00-cd-XX-XX-XX     dynamic
  192.168.10.30         ac-16-2d-XX-XX-XX     dynamic
  192.168.10.31         ac-16-2d-XX-XX-XX     dynamic
  192.168.10.33         00-9c-02-XX-XX-XX     dynamic
  192.168.10.34         00-9c-02-XX-XX-XX     dynamic
  192.168.10.36         ac-16-2d-XX-XX-XX     dynamic
  192.168.10.255        ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-XX-XX-XX     static
  224.0.0.252           01-00-5e-XX-XX-XX     static

Interface: 192.168.250.51 --- 0x19
  Internet Address      Physical Address      Type
  192.168.250.30        ac-16-2d-XX-XX-XX     dynamic
  192.168.250.31        ac-16-2d-XX-XX-XX     dynamic
  192.168.250.33        00-9c-02-XX-XX-XX     dynamic
  192.168.250.34        00-9c-02-XX-XX-XX     dynamic
  192.168.250.36        ac-16-2d-XX-XX-XX     dynamic
  192.168.250.255       ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-XX-XX-XX     static
  224.0.0.252           01-00-5e-XX-XX-XX     static

Any ideas on how to fix this?

Hi,

I want to set up a guest Virtual Machine cluster on a Hyper-V(WS2012) Cluster.  The guest VM Cluster will use as quorum a fileshare.  I've built 2 guest VM with WS2012.  They are on the same virtual network, I disabled the firewall and they can ping each other.  I have installed the Failover cluster feature on both VMs.  I'm logged in with a domain administrator and the cluster validation is fine. (except for a spof for the NICs and no shared storage).  Once that I start the create cluster operation I get ...."forming the cluster...." Waiting for the node ... to become a fully functional member of the cluster.  Eventually after 2-3 min. I get the message "An error occured while creating the cluster and the nodes will be cleaned up. This is a brand new test environment with a new AD/DNS.

In the Failover Windows eventviewer I found these warnings:

The first warning is referring to an IPv6 address.  IPv6 is not disabled. (I know if it is it uses the IPv4 path) There isn't a anti-virus software installed on the VMs. Any help would be appriciated.

hello, i have a server member of cluster formed with 3 node windows 2008 r2 disjoined from AD

how to rejoined it ??

thank you

We have several Hyper-V Clusters where we have the same issue. We're running Windows 2008 R2SP1 with hotfixes, latest drivers, latest FW, ... on BL460cG7 HP Blades

From some nodes we can Live Migrate and from some nodes not:

For Example

Live Migration from Node1-> Node2 = Perfect

Live Migration from Node2 -> Node1 = Live Migration fails at 10% with the error:

EventID 22000

Source: Hyper-V Worker

Message: Could not send data to the remote node: An Established connection was aborted by the software in your host machine (0x00002745)

I've been combing the net and the knowledge bases here to find a fail-over solution for storage that does not involve a SAN backend.  To lay some background down the development solution I'm messing with is as follows:

4 total physical nodes:

2 Hyper-V hosts(HA-Clustered for failover)-

2 Storage Hosts(HA-Clustered for failover)

...so far I've gotten this above working in  a 3 node solution. 2 Hyper-V hosts with 1 storage node, which is an iSCSI target hosting Quarem and a CSV disk.

In this config, if I lose that 1 storage node, I obviously lose Hyper-V clustering, so I thought...OK lets add add a second storage node to fail-over to.

Here in lies my issue. Everything I've read up until now points to adding not only an additional storage node, but also another backend server(SAS ect...) which then allows for clustering of the 2 storage nodes much like how the single storage node above allows for clustering of the 2 hyper-v hosts.

At this point I'm already wondering if I'm making any sense. Or maybe my thought process is just completely wrong.

In a nutshull I'm trying to achieve  failover storage nodes without having to add another backend server to cluster the 2 storage nodes together.

So far the only thing that achieves this is 3rd party software by means of something like:

http://www.starwindsoftware.com/windows-server-clusters

In which the storage platforms run active-active and are continuously syncing with each other. Is there a build in mechanism for this behavior? Or is it required that I have a stand alone SAN hosting quarem disks and CSV disks for both the Hyper-v nodes and the Storage nodes?

I don't need a walk though by any means, but I'd be much appreciated to be pointed in the right directions, because right now I'm going in circles.

Hi Team,

I am trying to configure a 2 node windows failover cluster. But when I try adding the second node to the failover cluster it throws below error.

System error 1460 has occurred (0x000005b4).
This operation returned because the timeout period expired.

I am using ISCSI target to setup the quorum and windows 2008 r2 enterprise as nodes.

Please help...need this immediately.!!!!

I have 2 servers(DL380 G5 with Windows 2008 R2 DataCenter) connected to a iscsi san (P2000 G3 iSCSI),
Failover cluster configuration report shows no errors or warning.

Faulting application name: clussvc.exe, version: 6.1.7601.17514, time stamp: 0x4ce7999c

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2

Exception code: 0x80000003

Fault offset: 0x0000000000033c32

Faulting process id: 0x740

Faulting application start time: 0x01cdc8890cf8a434

Faulting application path: C:\Windows\Cluster\clussvc.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 268dfc04-3482-11e2-8e19-cdadae78b39e

Sami Marzouki

Hi :)

Yesterday I've have "failover cluster meltdown :( as I suspect because of network failure and very possible network missconfiguration on nodes.

Error is:

Event ID:      1127
Task Category: Network Manager
Cluster network interface 'node1 - vlan99' for cluster node 'node1' on network 'vlan99' failed. Run the Validate a Configuration...

small net config recap:

os: win svr 2080 R2 sp1 datacenter / 5 nodes

all 5 nodes have two nic teamed (nic2 and nic3) in switch fault tolerance mode and virtual teamed interface is in trunk mode so it have some vlan's:

vlan152-csv - cluster use: internal - allow cluster network communication on this network, not allow clients to connect trough this network

subnet: 10.7.152.0/24

vlan156-lmig - cluster use: internal - allow cluster network communication on this network

subnet: 10.7.156.0/24

vlan77-daex - cluster use disabled: do not allow cluster network communication on this network

subnet: 192.168.168.0/24

vlan99-nodes- cluster use enabled: allow cluster network communication on this network, allow clients to connect trough this network

subnet: 10.0.0.0/16, interface is 1st in binding list order

On subnet 10.0.0.0/16 are also DC's and CAP address have IP 10.0.67.67 from mentioned subnet. vlan99 is accrossed vlan on 3 sites.

Whole failovercluster goes down (blade servers, swtiches and storage are located in site 1) after router in site 2 goes down ? How such thing is possible ? I've expected that blade switch in site 1 should have on itself mentioned vlan99 and that nodes internal on site 1 could communicate between them using vlan99 because they are on same switch ?

However, from above network config recap you'll see that reconfiguration is needed.

Can I add one more vlan interface, assign IP address and then change CAP IP address in cluster core resources properties for IP address so that I can

change settings for vlan99 interface in cluster and not allow cluster communication on this network ?

Should it new vlan interface be internal only on blade switch like vlan's vlan152 and vlan156 (because it is used only for communication on those 5 nodes on same switch) ?

Can I expect after that change on vlan99 interface some problems with authentication on DC's (they are on same vlan99) ?

Failovercluster purpose is hyper-v servers so I do not have clustered resources which clients need to connect and will also remove allow clients to connect trough this network.

Thank you for any advice

Best regards

Nenad

I have a simple 2 host cluster. W2008R2.

On one node  (host A) I have 4 VMs running nicely. The other host (host B) is currently idle. However, when I run a cluster valiation from host A, it fails at the "validating the inventory > List running processes" stage.

I checked the processes on the host A and there are currently 290 running, more than half are cscript.exe.

I guess this is not normal. Any idea what's causing the validation issues?

Thanks.

Hi,

I have created a two node cluster in my environment. After creating the cluster service, it reports me the following error and warning,

Warning

Event ID – 1579

Cluster network name resource 'Cluster Name' failed to update the DNS record for name 'MyCluster' over adapter 'PRO'. The error code was 'DNS bad key. (9017)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record 'MyCluster'.

Error

Event ID – 1196

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:

DNS bad key.

Both the cluster node servers are running Windows 2008 R2 Enterprise, Service pack 1

My environment has a third party DNS setup. After some searching I found out that this problem can occur when I use a third-party server application for DNS resolution. But I could not apply the fix. It reports me “This hot fix is not applicable to your system”. May be I have already got the fix.

Does anybody know how to fix this issue?

Thanks in advance.

Good Day Everyone;

I would like to seek for expertise on Cluster server 2008 r2. We have created 2 node cluster and is working perfectly. however, i would like to create a batch file on the Task scheduler which will help me to performed certain backup in the active node cluster (SQL server database) on scheduler. At Present, I have to login physically the server and execute the batch file every-time went i want to performed backup of the database. The concern here is whether Task scheduler is cluster aware cause we do not want to jeopardize the cluster servers setup. the scheduler will be performed at Daily, week & Monthly.

Kindly assist me on the said matter. 

Regards

Randep Singh

Hi!

We're facing an issue when cluster service starts. It won´t accept any group for a while (from 10 to 90 minutes after startup).

We did troubleshooting of the cluster.log and found out a lot of records like this:

ERR   [RES] Physical Disk: Failed to get snapshot info for disk, status 170. Ignoring...
WARN  [RES] Physical Disk <%1>: Open: invalid device number!

where %1 is one of the disk resources in the cluster.

After it, the RHS consider it deadlock and restart.

ERR   [RHS] RhsCall::DeadlockMonitor: Call OPENRESOURCE timed out for resource '%1'.
ERR   [RHS] Resource Cluster Disk 3 handling deadlock. Cleaning current operation and terminating RHS process.

and submit a WER.

When this occurs, RCM warns it:

WARN  [RCM] HandleMonitorReply: FAILURENOTIFICATION for '%1', gen(0) result 4.

And if it fails 4 consecutive times, it marks the resource as poisoned:

WARN  [RCM] rcm::RcmResource::HandleMonitorReply: Resource '%1' consecutive failure count 4. Moving resource to the poisoned state.
INFO  [RCM] TransitionToState(%1) Offline-->Poisoned.

When every disk return a good status (gen(0) result 0.) or is marked as poisoned, the issue dissappear.

Meanwhile, on eventviewer we see

Log Name:      Microsoft-Windows-FailoverClustering/Operational
Source:        Microsoft-Windows-FailoverClustering
Date:          DATE
Event ID:      1209
Task Category: Physical Disk Resource
Level:         Information
Keywords:      
User:          SYSTEM
Computer:      SERVERNAME
Description:
Cluster service is requesting a bus reset for <resource>

and BFAD errors 7 (Logical unit reset was performed upon request. Dump data contains additional details.) and 118 (The driver for device <resource> performed a bus reset upon request.)

Any hint on this issue?