Hello,

I currently have a Bladecenter which has 2 Blades accessing the same LUN of the Storage of the Bladecenter.

If I create a new folder on one Blade (Server) the other Blade does not see this folder. But currently both have VMs running from the LUN without problemsand are up to date Windows Server 2012.

How is it possible that the one machine does not see changes made by the other Server?

Hope someone can assist in resolving the problem.

Thanks in advance

Whity88

Seems like a simple enough error but i cant seem to figure out what I need to change.

Results by Category > Hyper-V Configuration

Node 'Server Name' is missing a virtual Ethernet switch 'Switch Name' that is present on at least one other node. Either remove the virtual Ethernet switch from all nodes or ensure that it is present on all nodes.

Any help would be much appreciated.

Dear All,

We have installed two DFS clustered role on the same 2-node Hyper-v 2012 cluster, of course with different Client Access Points (CAPs); we assigned a NAS storage LUN to one DFS role and another LUN on a different NAS to the 2nd DFS to have a back-up failover DFS.

We created shares for both DFSs CAPs, namespaces for the first one, added both folder targets to each DFS namespace, with one of the two targets pointing to the "main" storage as preferred. The idea is to use the 2nd back-up target folder only if the main storage hardware fails.

We will manage the replica off-line with 3rd part software EXCEPTION MADE for two folders which are critical for some of our applications and would like to be replicated "in real time".

When we created the replication Group for such folders everything goes apparently smoothly but the replication is not working.

Looking at the server logs table, it seems like the DFS-R service expects to find the replication database on a network share with this syntax:

\\.\F:\etc.etc, where F: is the drive letter of one on the iSCSI storage attributed to one of the DFS roles. I have never seen \\.\ before..

Is there a way to fix this issue? I tried to modify manually the replication path introducing the corresponding netshare (e.g., \\DFS\etc.etc\folder where the database is located) but this returns an error.

Kind Regards

Filippo

Hi, All!

Currently reading the official MS Press MCTS Self-Paced Training Kit for exam 70-432 (SQL Server 2008 - Implementation & Maintenance). MS errata info had nothing about the following.

A note by the author (Mike Hotek) regarding implementation of failover clusters and the location of the Quorum files on the nodes, specifies the location of the Quorum (config DB, I believe), but I could not verify.  When I tried to follow the path, I came up empty-handed.  At the beginning of the chapter, he confesses that 2008 was just being released at the time of writing for the book, so the majority of the information is predicated on 2003/2003 R2 architectures but it's updated with relevant 2008 info where available (at the time).  Sooooo...I'm not sure if this is outdated info or not.  See excerpt (paths emboldened):

Note

LOCAL QUORUM

The location of the quorum is %SystemRoot%\Cluster\QoN.%ResourceGUID%$\%ResourceGUID%$\MSCS.  A Share is created on each node that is named\\%NodeName%\%ResourceGUID%$.  You should not modify this directory or change the permissions on this directory or share in any way.

When I try to browse to those directories either manually (clicking through folders) by directly (typing absolute path in explorer address bar), I cannot access either of those path locations.  Anybody know the updated paths or if this information veritably pertains to 2003 AND NOT 2008 Architectures of Windows Server??

I'm totally OCD and I can't find anything, I can't even determine the ResourceGUID.  One forum post inferred that it could be found on a node by reviewing the config of shares via (compmgmt.msc) but even that revealed nothing.

Any help or insight would be greatly appreciated--thanks!

Very Respectfully,

POAB

I created a 2012 cluster of 2 servers. I had it all set up with storage and all and then found that I messed up with the storage. So then I started trying to back out, dismantling the cluster piece by piece. Somewhere along the way, I goofed.

Now the cluster still seems to exist somehow but I can't access it from either server. The cluster service won't start on either server and if I try I get errors 1090 and 7024 in the System event log.

I've tried uninstalling and reinstalling cluster services on both servers twice but that hasn't helped.

In the Failover Cluster Manager, I can do the Validate Configuration tests and they all come out green with a few minor warnings that do not impact this in any way. But when I try to create a new cluster using the old name, I get an error that says that name is already in use. If I try the link "Create cluster" and try to add either host to it, I get an error saying it's already a member of a cluster. If I try to connect to the original cluster I get an error that the details say "Value cannot be null. Parameter name: clusterServiceParametersServiceParametersKey".

So I'm stuck with this original cluster that can't be managed, joined, or removed (at least I haven't figured out how to remove it). Due to how the client's business is setup, I really need to use that name used for the original cluster. I did find some powershell commands for cluster management but the usage is not the clearest and I don't want to damage the servers themselves. Also the powershell commands require the cluster service to be running which, as I stated above, won't start.

Any ideas on how to wipe out all traces of the original cluster without reinstalling the OS? Backups haven't been set up on the 2 servers yet because I'm still trying to get things set up.

Jonathan

hello everyone 

i have a small project to do 

i need to deploy VM hosts with +100 VM each 

these hosts are identical in hardware and software. 

what i want is to find out 

1. can i automate deployment 

2. can i automate updates "adding/removing VMs" to the hosts

i am planing to have WS 2012 and SCVMM 2012 SP1. is that enough ? do i need anything else because i never did something like this before 

any ideas how to achieve that ?

thank you

I am Supporting WP7 but please keep improving it MS.

I have a 6 node Server 2012 Hyper-V cluster. Each node was a fresh install with all local drives formatted and repartitioned during OS install.

The first 5 nodes went great, but the 6th node is causing me some problems.

On the 6th node, Im able to connect to the iSCSI LUNs with no issues. Everything looks great until I add this node to the cluster.

When I add it, the add succeeds, but none of the LUNs are mounted to the c:\ClusterStorage folder correctly.

Instead of showing up in ClusterStorage as a mountpoint for each LUN (6 LUNs in total) they show as folders, and are not accessible. In the Windows Event Logs, for FailoverCluster, Diagnostic it shows the following:

Log Name:      Microsoft-Windows-FailoverClustering/Diagnostic
Source:        Microsoft-Windows-FailoverClustering
Event ID:      2051
[DCM] failed to set volume mount point, source \\?\C:\ClusterStorage\Volume4\ target \\?\Volume{89454e8c-4832-4ad8-a43e-75c4ecab253c}\ error 87

It does this for each of the 6 Luns.

I've tried removing this node from the cluster and reinserting it. Reboots while a member of the cluster, and not the cluster. All Windows updates are applied. Full format and wipe of the server, reinstall of OS and try again, etc. I tried looking on Technet and found some references to this error code but they appeared to be related to driver builds using windows API to use mount points. I haven't written any special drivers or anything unique at all for this cluster. Everything is out of the box Microsoft native drivers.

The server is a Dell PowerEdge R710, same as one of the other nodes in the cluster which is working fine. The other 4 are Dell PE 1950s. The first 5 are working great, its just this sixth one. All 6 servers were reloaded over the course of about a week, using the same checklist, same media, etc. I currently have 72 VMs running on this cluster with 5 nodes, and really looking forward to joining #6.

Anyone have any ideas before I call Microsoft support?

Thanks

Sean Greenbaum

Why will a 2 disk, 1 column, 2-way mirrored space work fine outside of a cluster? Yet, when I want to use clustered storage spaces I need a minimum of 3 physical disks for a 2-way mirrored space? Killing me...

I mean if I add 2 additional disks and do a 4 disk, 2 column, 2-way mirrored space it's ok. What would be the purpose of using 3 disks as a minimum?

Thanks,

Scott

Hi guys.

the company i work for has a big cluster server made of 2 physical servers with lots of important shared folders and home folders that needs to be migrated from domain A to domain B with all permission etcetera.

we used ADMT with other servers but none of them were clustered.

what is the best way to do this?

and how long will it take as some departments are working 24/7?

there is nothing to fear, but fear itself

I am adding a separate interface on my windows 2008R2 nodes and would like to know if we can exclude the interface from the cluster or validation.

The problem I am facing is that the switch port is configure for private vlan. The mean that the host cannot talk to other host on the same segment or vlan. The purpose for this is PCI compliance when accessing the server...I want to use the nic for dedicated backups. Or dedicated backup network segment is a private vlan.

That being said, anyone know how to exclude a nic or network from the failover clustering detection?

Thanks.

Hello,

I have two Windows 2012 Datacenter Core installed on two box. I'm using Windows 2012 and Windows 8 PC to manage those two servers that are in a cluster. Everything is working fine. But when I came in yesterday, I get "Keberos security error" in Server Manager only on the cluster object, but not the servers. See image:

First line is the first physical host and second is the second physical host. Third line is for the cluster. Now, I can't create drives any more. Please advise.

Looks like MS needs to verify my account before i can attach an image.

This node, an 'active' node in a five-node SQL cluster, seems to report a different domain controller depending on which tool I run.   (see output below)

This SQL server is error free. 

I checked it because I'm troubleshooting another SQL node in the same cluster that lost its connection to the domain controllers.  I saw this exact situation on the problem computer.  I thought running these commands on another computer might shed light on why the troubled node  was having difficulty communicating with any domain controller.  SQL continues to run; no functionality has been compromised, but I can't add domain user accounts to ACLs.  And I'm due to fail the SQL Instances it runs to another node.  I wonder if this will work.  I can always turn the node off, I suppose.

In fact, three of the other four had the same odd situation, but also run well.  On only one of the four does the output of 'nltest' match that of 'set.' 

I noticed the problem an hour and half after I failed each of the most heavily used instances over to the two most powerful nodes, the ones that had brought the node-count to five.

FWIW, the OS is 'W2K8 SP2' and the versions of SQL are 'SQL2K8 SP1' and 'SQL2K8 R2 RTM'

OUTPUT FROM NLTEST DOESN'T MATCH OUT PUT FROM 'SET'

C:\Users\JDoe>set
ALLUSERSPROFILE=C:\ProgramData
LOGONSERVER=\\XXX-DC2
USERPROFILE=C:\Users\JDoe
windir=C:\Windows

C:\Users\jdoe>nltest /dsgetdc:doe-land
DC: \\XXX-DC1
Address: \\172.16.0.34
Dom Guid: 2577d1e2-4a5c-4d3e-a00c-6e308b06cead
Dom Name: DOE-LAND
Forest Name: DOE-LAND.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_FOREST CLOSE_SITE FULL_SECRET 0x2000

The command completed successfully

C:\Users\jdoe>

We created a 2008 r2 failover multisite Steel EYE File cluster with different IP subnet. Cluster and Failover are working fine. No problem. The problem is to access the cluster name when it failover.

Ex. Cluster name CL1 has two ip address for each subnet and the owner is configured properly for each subnet.

DNS entry for CL1 is the ip address of SITE1. SO during the failover whether we need to CL1 owns the ip address of SITE2. Is there any way we can access the CL1 without changing the DNS entry.

Sony

SI

Our base network is a 192.168.1.X

Im setting up our iSCSI SAN connection on 192.168.15, does the server cluster need to be setup on a different network than the 15?

Here is a diagram with what my current setup is:

Diagram

Thanks V

Hi,

I'm trying to get familiarized, in lab, with some 2008R2 advanced topics. My lab machines are :

- DELL PowerEdge T310 server (with virtualization option and VMWARE ESXI 5.1 installed) for running 2008R2 VM servers.

- 1 P4 PC (100Mbps NIC) for running Openfiler SAN.

I tried to configure a 2008R2 cluster. I successfully configured the SAN and I was able to write on it via iSCSI target in 2008R2 VMs. But, If I run the Failover Cluster Mangement validation step, it does tell me that the storage is not adequate for clustering. The cluster did not recognize the SAN and the iSCSI target stops working. I suspect it is a "SCSI-3 reservation add-on" issue.

Anyway !

- Do someone know how I can make the Clustering work without adding any hardware equipment ?

- By the way, I'm asking the same question for RD Virtualization and for Hyper-V ?

Thanks in advance for any help !

NB : I have couple of other P4 and Dual Core PCs. But, the only machine where I can run my 2008R2 servers is the DELL PowerEdge.

Is there a reason this fix isn't available for Hyper-V Server 2008 R2 as well? The cluster I've built is affected by this same problem, just with Hyper-V Server!

http://support.microsoft.com/kb/977158

Hi ,

I am using both windows 2008 r2 machine and windows 2012 server machine.I need to configure cluster  environment in both these(2008 r2 and 2012) machines.

It is possible to configure cluster in two machines ?

any other limitations? or it supported to configure cluster on 2008 R2 and windows 2012 machines?

regards,

Gouse

I know this is really a question for the Dell forums (which I posted on also) -

Has anyone in the community had any success getting Failover Clustering working on Windows 2012 using a MD3000 and PERC 6/e's?

I have been able to configure the storage but the servers don't see it in storage manager.   Should it appear at POST?

This is stopping me from moving forward and might roll back to 2008 R2, that is officially supported.

hi all,

i had posted the following a question here [http://blogs.msdn.com/b/clustering/archive/2012/06/02/10314262.aspx?PageIndex=2#comments]

I have a SAS storage box which is not a JBOD. The SAS storage box has a RAID controller which cannot be bypassed. If I create RAID 1s of all the disks individually, it means I dont have an abstraction layer on the storage.

Will such a configuration be supported by MS? the Cluster Validation Utility passes all the test the moment it sees a SAS storage. It doesnt look at RAID metadata on the disks.

So basically in my configuration there is no failure in the Cluster Validation Utility but the statement on this blog

"         The clustered storage pool MUST be comprised of Serial Attached SCSI (SAS) connected physical disks. Layering any form of storage subsystem, whether an internal RAID card or an external RAID box, regardless of being directly connected or connected via a storage fabric, is not supported.

"

means my config is not supported.

Response i got was:

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

I have an additional question:

Does Microsoft have any plans to get this working on SATA/FC disks? Or will it always be on SAS disks only? Secondly, if the hardware RAID is RAID 0 the RAID controller is virtually bypassed. So why is it not supported?

Lastly, the moment i use SAS disks and with SAS backend, the Cluster Validation Utility passes, irrespective of which RAID I use. So does that mean the Cluster Validation Utility is not the final say in-terms of support?

Thank you

We have an OEM storage vendor telling us that it is NOT recommended at this time to use SAS interposers with any SATA drives (regardless of brand or type (HDD or SSD)) and use it with Windows Storage Spaces/Clustered Storage Spaces. This would be for a shared-SAS backend using a JBOD/HBA and Windows Storage Spaces as a scale-out file server solution. This is the setup you see referenced from Microsoft all over the place.

Is anyone seeing any issues? They claim it's an issue with the LSI SAS interposers (LSISS9252) that all storage vendors rebrand or sell. And, apparently LSI is not seeing this as a high priority fix.

They're alleging that Microsoft product development has told them it's an issue with the firmware on the SAS interposers (which is only upgradable by OEMs BTW) and that using these will result in drives dropping off/not showing up.

BTW, this comes from a Windows Storage Spaces certified product...thoughts? I'm just looking for any information so we can make an informed decision.