Hi Everybody,

I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard "  This operation returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.

thanks 

Hello Everyone,

Thanks in advance for your help and thoughts.

We have a 2 node cluster running Windows 2008 R2 that runs our virtualized appliance, the witness disk resides on another server on the same subnet.  A month ago the servers were patched, security only mind you, as part of our standard business practice and since this time the cluster has failed to start.

When looking in the logs it states that it cannot reach the witness disk, however, I can reach the server that holds this disk from both servers in the node - all network connectivity / checks have been done that I can think of.

The cluster service on both nodes will not start either, when attempting to start the service on either node, it states that it cannot and entries in the log are showing event ID 1090 and 7024.  After checking online about these it would appear that the local cluster database on each node would be corrupt?  I ran a cluster log /g and I see entries pertaining to 'open key parameters' as well.

I am at the point, unless anyone has a better solution, that I need to rebuild the cluster.  I was thinking that I would start by removing one node (evict command) and seeing if I could bring up the other node as a standalone box.  However, information that I saw online indicates that doing this was bad and that the evicted server cannot be brought back into the cluster unless Windows was reinstalled and possibly on new hardware?

Can anyone validate the evict command and what exactly it does, both good and bad, and if anyone has any ideas on how to fix our downed cluster, please let me know.

Thanks,

CU

Its my first Server 2012 R2 Cluster and its based on a Dell VRTX server with shared storage.

I've created the cluster and I'm now trying to setup the Quorum witness disk.

In FCM Storage/Disks a 600mb disk is shown as online and I've called it Quorum.

In Win Disk Manager this disk shows as offline and reserved.

When I run the 'Configure Cluster Quorum Settings' wizard, pick 'Select the quorum witness', pick ' configure a disk witness' I get the error 

No suitable disks exist in Available storage.

What am I missing?

Any help/advice/suggestions grateful appreciated :)

Installed a Windows Server 2008 R2 Failover Cluster.  By default, the Failover Cluster Manager assigned the X:\ drive as the Quorum drive.  Using Failover Cluster Manager, I was able to move\reassign the Quorum drive as, let's say, the N: drive.  However this action does not delete the "Cluster" folder that was initially created on the X: drive.

What is the correct procedure to be rid of the "Cluster" folder that was created on the X: drive when the cluster was initially created without any impact to the existing failover cluster?

I have a failover DHCP cluster on W2008 Ent R2 .  need to move the database from D:\dhcp\db  to the e:\dhcp\db

My steps would be

Please correct me if I am going wrong somewhere. 

1. Open DHCP manager and open the DHCP server with your cluster name and stop the dhcp service

 2. copy d:\dhcp tp e:\dhcp

3. In the  DHCP manager Start your dhcp service back up.

3. In the Failover cluster Manager,  move your cluster to your preferred dhcp service

4. In the Failover cluster Manager,  under Services and application select the dhcp service and go to the properties of the DHCP server.

5. In the DHCP server properties -- General Tab change the database path and hit apply.

Thats it.  This is the working solution

Hello,

We recently ran into some trouble with our cluster running Windows Server 2008 R2 after security patching was completed. The cluster did not return to normal and now when attempting to start the cluster service it states that it cannot and comes back with an error code of 2.  The logs are reporting 7024 and 1090, and Cluster Log /g states 'open key parameters'.

I was going to to destroy the cluster and start all over again, however, when I attempt to destroy the cluster, I receive an error message - System error 1753 has occurred (0x000006d9). There are no more endpoints available from the endpoint mapper.  I am going to make the assumption that Windows cannot destroy the cluster as the service is not running?

I tried to remove the feature from the Server, however, Windows comes back and states that the Server belongs to a cluster and therefore it cannot be removed.  If I disable the cluster service, I can remove the feature, however, I am not sure if this is the best method of what may happen if I do it this way?

So with this said, does anyone have any advice on how to destroy the cluster when it is in a state such as this?

Thanks in advance,

CU

Server 2008 r2 ent

An error occurred while executing the test. There was an error getting information about the running services on the nodes. There was an error retrieving information about the Services from node 'XXXXX.XXXXX.COM'. Object reference not set to an instance of an object.

I am trying to improve the uninstall experience of our custom cluster resources. The user of our product can uninstall the product on one of the nodes of the cluster. When the customer uninstalls our product on the passive node, I want to remove that node from the possible owners for the resource type and delete the resource DLL on the passive node.

 I do not want to affect our resources on the active nodes. Hence I cannot use DeleteClusterResource and DeleteClusterResourceType APIs on the passive nodes. How do I do this?

Hi,

I'm a Windows NT student and I need help with understanding how to do clustering using multiple Windows 2008 R2 Enterprise servers in VirtualBox 4.3.8. I have a Windows 7 host computer. I was wondering if someone could provide clearly detailed step-by-step directions (ex. Click this, then click that) on what I need to do prior to clustering, as well as starting the clustering process. Please ask if you need additional information. 

Thank You.

Hello!

There're three cluster disks in my test cluster: cluster disk 2-3-4, the disks 2 and 3 are CSV disks, the disk 4 is NOT a CSV disk.

I have a vm named Single and I'd like to move its storage from cluster disk 2 to cluster disk 4, but the"Move virtual machine storage" wizard shows only two CSV disks (volume 1 and volume 2) as targets for moving a vm storage - there's no cluster disk 4...

Is there a way to move a vm storage from a CSV disk to a non-CSV disk?

Thank you in advance,

Michael

I created a 2 node Hyper-V Cluster that uses SMB3.0 for shared storage.

On both of my Hyper-V hosts I have a iSCSI disk that go to 2 seperate VM's for data storage.
Since I created the cluster the iSCSI disks are no longer available. In fact if I got Server Manager it won't even load anything under File and Storage Services. It just states "Display will be complete when the server inventory has finished...".

I attempted a reboot of the Hyper-V server, restart the iSCSi target service with no luck.

In Event viewer I see the following:

The Wintarget service has detected the creation of a failover cluster. Any existing iSCSI Target and Virtual Disk objects that were created in standalone mode are no longer accessible. Restart the Wintarget service on any cluster nodes that were running iSCSI Target Server in standalone mode.

I'm not finding how can I resolve this and everything I've tried has failed so far.

Hello Everyone,

I have 2-2012 servers that I'm trying to setup clustering with. Individually they can create their own 1 node cluster no problem, adding to an existing cluster doesn't seem to work either. If I destroy one cluster and try to add it to the other existing cluster it fails with timeout. I use the Validate a Confirguration Wizard it says everything checks out successfully (warning on Storage and Network for minor stuff), then fails once it tries to create the cluster with the following:

Tried going into ACU, then giving full access under Security to the computer accounts by prestaging a cluster name as well. That didn't seem to help even after it enabled the disabled computer account when forming the cluster. I can see if I try to join one to an existing node that it joins, never comes "UP" then gets evicted after a timeout.

Suggestions on where to go next would be much appriciated. It's intersting to me since I've setup multiple clusters on 2008/R2 and am currently running clustered Hyper V 2012 servers as the hosts for these without any issues, so right now 2 clusters are in the environment without any problems. Started a debug log during the creating of the Failover Cluster, didn't see anything that caught my attention as useful information. Not quite sure where to go next.

Hello ,

Environment: Windows server datacenter 2012 R2

i am receives the below error when trying to add a virtual machine through Failover cluster manager:
The Operation failed.
Failed to create external configuration store at 'C:\ClusterStorage\..' . General access denied error. (0x80070005).

<o:p></o:p>

<o:p>I am surprise why c:clusterstorage showing error message </o:p>

C:\ClusterStorage\..' . General access denied error. (0x80070005).

<o:p>please need your help .</o:p>

<o:p></o:p>

I've just created a new two-node Windows Server 2008 failover cluster that is going to be used for an Exchange 2007 SCC deployment. I built the servers and configured them using an ip-kvm, so I was on console the whole time. Now that the nodes are built and the cluster is formed I went to try and RDP to them, but it does not connect...I don't even get an authentication prompt -- just can't connect to remote computer.

So, here is what I've checked and tried:

1.) Verified RDP access is enabled (set to LESS SECURE mode)
2.) Verified my account has RDP access (trying to login with a domain admin account which has access by default -- but I don't even get as far as authentication)
3.) Disabled Symantec Endpoint
4.) Checked the adapter binding order -- the public NIC is first, then the private
5.) Tried changing Terminal Services configuration to only allow connections specifically on the Public network adapter (default is all adapters)
6.) Tried installing this TS hotfix while the ts configuration was set to a specific adapter (http://support.microsoft.com/kb/960742)
7.) The private network adapter is on an 'Unidentified Network' according to the network sharing center in 2008 - this can be set to Private or Public. It was running in Public which I believe is incorrect, so I changed it to Private.
8.) Tried modifying the local security policy to set Private to default for Unidentified Networks so the change would persist on reboots
9.) Tried re-enabling IPv6 (I had it disabled early on) 
10.) Tried various permutations of all these settings
11.) Rebooted several times during the process

So, obviously I've tried a bunch of things with no success and am a little frustrated at this point that such a trivial thing has consumed so much time!

Here's the kicker though -- when I disable the private network adapter, RDP suddenly works! This would immediately make me think it's a network binding order issue...I've tried modifying it every way I could think but haven't been able to get this working.

Here is all my ip configuration information & binding order. There are (4) physical NICs in the server, but (5) total network interfaces.

Public-A (Broadcom)
Public-B (Broadcom)
Public Team (Broadcom)
Private-A (Intel)
Private-B (Intel)

Public-A and Public-B are combined into a virtual adapter 'Public Team' for high-availability. The team is configured in an active/passive mode -- not load-balancing.

Private-A is the active Private cluster heartbeat adapter.
Private-B is currently DISABLED. I would like to use it for a 2nd cluster heartbeat adapter to provide high-availability since teaming is not recommended for the cluster adapters. I left it disabled for now because I wanted to get the configuration working with just one private cluster adapter first and then add the 2nd after everything is already working.

IPCONFIG /ALL


Windows IP Configuration

Ethernet adapter Local Area Connection* 8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
   Physical Address. . . . . . . . . : 02-21-5E-54-74-D8
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b59f:79fc:7146:daa4%15(Preferred)
   IPv4 Address. . . . . . . . . . . : 169.254.2.133(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Public Team:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : BASP Virtual Adapter
   Physical Address. . . . . . . . . : 00-21-5E-54-74-D8
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6570:998d:6b8e:1953%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.10.164.102(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.10.164.1
   DNS Servers . . . . . . . . . . . : 172.16.75.1
                                       172.16.75.34
   Primary WINS Server . . . . . . . : 172.16.75.1
   Secondary WINS Server . . . . . . : 172.16.50.18
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Private-A:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Dual Port Server Adapter
   Physical Address. . . . . . . . . : 00-15-17-6D-36-1A
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d444:6dd7:605d:86ec%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.10.165.97(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes



If anyone has any suggestions, please let me know! I'm eager to finally resolve this issue. I'd also like to take the opportunity to verify my network configuration for the cluster is correct.

Thanks,
-Brian

Cluster-Aware Updating

i am reading about Cluster-Aware Updating and i installed on my hyper failover cluster .

Till now i have some questions ....

why should i use Cluster-Aware Updating although i have wsus installed in my enviroment ?????

can we said Cluster-Aware Updating is replacment of WSUS ?

i installed Cluster-Aware Updating but till now when i click on ( preview updates for this cluster ) i didnt anymore updates .

please need help in this matter .

thanks

On a 2008 R2 2 Node cluster , when we run the  'Cluster validation Wizard' it gives an Alert before starting the validation process

Cluster Disk X1 May Require running chkdsk.exe as part of the validation process
Cluster Disk X2 May Require running chkdsk.exe as part of the validation process

Is this normal ?

Is it applicable for all 2008 R2 clusters ?

Hi

I am testing san controller failover. It takes around 2 mins for the second controller to come online after the first has failed.

There are some registry settings that can be configured to increase disk timeout but they don't seem to work when failover clustering is enabled.

I am testing this on a Hyper-V 2012 R2 failover cluster (regular clustered disks and CSVs - the same issue occurs on both)

I have changed the following registry settings 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk\TimeoutValue = 240

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mpio\Parameters\PDORemovePeriod = 240

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e97b-e325-11ce-bfc1-08002be10318}\0003\Parameters\LinkDownTime = 60

But as soon as the second controller comes up the cluster registers a failure of all the clustered disks and restarts the VMs. Just wondering whether the 2nd controller coming online is somehow triggering the clustered disk failure.

I am seeing the following in the event log.

Connection to the target was lost. The initiator will attempt to retry the connection.

\Device\MPIODisk3 is currently in a degraded state. One or more paths have failed, though the process is now complete.

Ownership of cluster disk 'Cluster Disk 1' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

Thanks

Daniel

Hello!

We have a Windows Server 2008 Standart SP2 x64, which is connected via two HBAs QLogic QLA2440 to a Storage Xyratex F5402. On DS5402 are located three LUNs for the corporate file storage. These LUNs are displayed in Windows Server as local disks E F G.

As the MPIO software it is used Xyratex Storview Pathmanager 6.00.5016.14 (Microsoft MPIO Driver 6.0.6002.18005) in Failover\Failback configuration, and three disks are adjusted for work on three different ways.

It is all normally worked since 2008

But problems have begun with the beginning of this year.

In operation time any of the SAN disks falls off. With a F5402 all is normal and its logs there are no errors.

In Windows Event System Log the folowing errors and warnings:
EventID: 515, Source: xyrsp200 (Xyratex F5402E Multi-Path Device Specific Module). The path for logical drive [SN: 60050CC00020188D0000000000000007] has failed over to [0005 4:0:1:2] because of a path error.

EventID: 23, Source: mpio. Errors in all ways. \Device\MPIODisk2 it will be removed.

EvetID: 260, Source: xyrsp200 The active path on logical drive [SN: 60050CC00020188D0000000000000007] has been switched to the preferred path on [0005 5:0:0:2].

EventID: 15, Source: disk. Access to the device \Device\Harddisk5\DR5 while is impossible

and further an disk erors...

Disk reloading in Windows Disk Manager doesn't help. I am compelled to reboot the server. After reboot all works as though anything and wasn't to the following such case.

As fall off not all LUNы at once (one can fall off, others and will to work normally) a problem probably either in Windows or in Xyratex Storview Pathmanager.

After adjustment of monitoring I have found out that at the moment of failure the current queue of a falling disk was 6 and the size of operation of record on a disk has sharply increased.

May be the disk simply hasn't sustained loading (though strange - Fiber-Chaneell, and High-Perfomance Disks Storage). In Windows it can be somehow possible to optimize operations of work with disks that there were no such falls.

I need a help !!!

I'm rather new to clustering and DAS and SAN storage devices so I am trying something rather simple to get me going, this is  the scenario

2 x Dell Servers of different spec both installed with Windows Server 2012 Standard Edition.

I have added the hyper-v role on both the servers.

1 x Dell MD3200 (DAS using SAS cables and SAS Controller Cards) I have created1 Virtual Disk of 2TB

Please note I am not using iScsi

My Intention is to do the following

Host Server 1

4 x Virtual Guests the Virtual Machine info and VHD's to be stored on the single Virtual Disk i created on the MD3200

Host Server 2

4 x Virtual Guests the Virtual Machine info and VHD's to be stored on the single Virtual Disk i created on the MD3200.

So basically both Host Server's can see and write information to the Single LUN Virtual Disk I created, and in the event that one of the hosts fails then the virtual guests merely cutover to the other host server, and the memory and processor power adjusts accordingly to handle the 8 machines it is now looking after.

Is this possible with out of the box features in Server 2012 Std? Will I have issues around data corruption due to different file systems? If possible then what is the process.

Do I connect Host Server 1 to the (DAS) Virtual Disk, create my VM's setup clustering on Host Server 1, then connect Host Server 2 to the DAS add it to the cluster and then create the VM's? Or do I connect both machines to the DAS setup the cluster and then start writing data (creating the vms) on the Host Servers.

Lastly could I use the same process for file servers? Which in essence is 2 x servers connected to the DAS, but I'm sure if I understand the above I will be able to answer this one myself. :-)

Thanking the technet world in advance.

Ahmed