multiple regressions in migration from Server 2003 to Server 2012 (R2)

November 20, 2013, 6:24 am

≫ Next: 2012 r2 failover cluster add storage disk fails

≪ Previous: cluster failovered often

$

0

0

Hi,

I'm preparing a migration from Windows Server 2003 (Enterprise) to Windows Server 2012 R2 and came across multiple regressions (removed features) while doing so.

Current situation: Active Directory Domain with 3 controllers. Each of them is a member node of a failover cluster with DHCP and print spooler services. With this configuration I have a HA environment with ADDS, DNS, DHCP and print spooler.

With Windows Server 2012 (R2) a failover node is NOT allowed to be a domain controller and print spooler is not supported as clustered resource any more. To re-create a similar HA level I would need now at least 4 Windows Server instances with 2 DCs and 2 cluster nodes for DHCP. The new DHCP failover feature seems to have issues with replication delays of configuration changes as well as with replication of reservations, therefore it is not an option. Along with these disadvantages I still do not have a solution for the print spooler.

Any comments?

Best regards,

Nikolaus

---

2012 r2 failover cluster add storage disk fails

November 19, 2013, 7:44 am

≫ Next: ask your advice.

≪ Previous: multiple regressions in migration from Server 2003 to Server 2012 (R2)

$

0

0

 Hello,

I am hoping for some help here, I have searched the forums/web and can't come up with the reason for my disk failure. I am working on 2012 r2 virtual servers sitting in a vmware environment. Dell compellent boxes are my storage.  This is my first attempt to setup a failover cluster and I think I have the concept down for what I want to do... but when I attempt to add storage disks to my cluster they come up in a failed state. The following error is what I get. 

event 1069 : Cluster resource 'Cluster Disk1' of type 'Physical Disk' in clustered role 'Available Storage' failed. The error code was  '0x1'("incorrect function.")

I realize this is much info to go on but I'm lost... any help would be greatly appreciated. 

ask your advice.

November 20, 2013, 11:09 am

≫ Next: Failover cluster - correct placement of DC with FSMO

≪ Previous: 2012 r2 failover cluster add storage disk fails

$

0

0

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.

Failover cluster - correct placement of DC with FSMO

November 20, 2013, 8:35 am

≫ Next: Unable to Validate a Cluster Configuration. The operation has failed. The action validate a configuration did not complete .

≪ Previous: ask your advice.

$

0

0

Hi,

I have been searching all over the net but am unable to find any indication of the best way to have my specific infrastructure configured.

Current configuration:

7 sites with one of those being Head Office.

1 local domain.
Head Office has 1 physical DC (2008 R2) which holds all FSMO roles and is a Global Catalogue server.
A secondary DC is a VM (also a GC & 2008 R2) hosted on a HVA Failover Cluster (2008 R2) with CSV's. Each of the 3 nodes is a member server of the domain.

Each branch office has a host member server with only the Hyper-V role installed. Each of those has a local DC VM (GC & 2008 R2)

All branches connected by a private MPLS network, 4 sites with 10mb, and 2 with 20mb - Head Office also has a 20mb connection. (so, fairly quick WAN links)
Local branch ADSL as a backup.

At the weekend we had to power off Head Office for the electric meters to be changed. Everything was safely powered off, but i had issues when powering on again.

Powered the physical DC (FSMO) first, then powered on the SAN and the 3 cluster nodes.
The cluster service wouldn't start - authentication failure.
Checked the logs on the DC and it was receiving event id 2092. Which states that the "FSMO-owning AD LDS instances are required to in-bound replicate a particular partition on service start-up in order to satisfy initial synchronization requirements."
DNS was also unable to start.
The closest DC is a VM held on the cluster and unable to start.

DNS config: Head Office physical DC1 has itself as first server (actual IP address, not loopback) then DC2 as secondary.
Head office DC2 (VM) has itself as first DNS (again IP address not loopback) then DC1 as secondary.

To get the physcial DC to perform inbound replication I had to add an entry to the hosts file to point to one of the branch DC's and set secondary DNS to the same server, then manually replicated with that server through AD Sites & Services.

Once that was complete and replication successful I was able to start the cluster service and power on the VM's.

From everything I have read MS recommend to have a physical DC in the same site as a Failover Cluster. Which I have got, all be it the FSMO owner, which cannot replicate with another DC upon start up, from the same site as it is located on an un-available cluster.

So my question is where should the FSMO roles be placed?

As far as I can see I have a couple of options.
I could create another physical DC in Head Office, starting both would enable replication with each other.

Or is it safe (recommended?) to place the FSMO roles on the DC VM in Head Office. Therefore the physical server would just be a DC - but wouldn't be able to replicate to the FSMO holder until the cluster was online. But if the cluster came online the Virtual FSMO holder could replicate with the physical DC.

Or I could leave the host entry where it is, and wait for the physical FSMO holder to sync with the branch DC. Would this take a long time?

Any advice offered would be greatly appreciated

Thanks

Unable to Validate a Cluster Configuration. The operation has failed. The action validate a configuration did not complete .

November 19, 2013, 12:03 pm

≫ Next: Network list for administrative access point

≪ Previous: Failover cluster - correct placement of DC with FSMO

$

0

0

There is an error in XML document (5, 73).  

Attempt by method

Microsoft.Xml.Serialzation.GeneratedAssembly.XmlSerialzationReaderClusterPrep.Config.Read4_As...Bolean) to access method

MS.Internal.ServerClusters.Validation.TestAssemblyCollection.Add(MS.Internal.ServerClusters.V....Failed

Network list for administrative access point

November 20, 2013, 1:33 pm

≫ Next: Can't access Failover Cluster Manager in Windows 2012 R2 Cluster - The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server

≪ Previous: Unable to Validate a Cluster Configuration. The operation has failed. The action validate a configuration did not complete .

$

0

0

I'm having a problem where I've got 4 networks and only 1 will show up in the list for the admin client access point list.  

192.168.71.x - This is used only for remote access in our environment.  I don't want the access point to be on this network but it is the only one in the list.

192.168.72.x - Used for internal application communication

192.168.73.x - 10 Gb iSCSI SAN access

192.168.74.x - 1 Gb heartbeat network

These are IBM blades using a 4-port NIC and I have created VLANs and teams on them for failover and whatnot.

Why are my other networks not showing up in the list?  All it shows is:

192.168.71.0/24 with an area for the Cluster Name and the address to use.

Can I get this on the .72 network?  When I go into the properties the .71 network is still the only one available, even though all 4 are available and used in the cluster.

The domain is on .71.x and .72.x

Do I need another network for this?

Can't access Failover Cluster Manager in Windows 2012 R2 Cluster - The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server

November 19, 2013, 5:48 pm

≫ Next: Disk Space in Windows Drive

≪ Previous: Network list for administrative access point

$

0

0

Hello!

   My client has a two-node Windows Server 2012 R2 Hyper-V Cluster which has been running for month or two.  The other day I found that from the Hyper-V1 host I couldn't run the Failover Cluster Manager - I got an error "The RPC Server is Unavailable - Exception from HRESULT: 0x800706BA".  Then I tried to log into the other Hyper-V Host (Hyper-V2) and found that I couldn't log in using domain credentials - I had to log in locally.  On this Hyper-V2 server I saw errors in the System event log:

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server hyper-v2$. The target name used was HYPER-V2$. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (XXXX.XXXX.com) is different from the client domain (XXXX.XXXX.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

   I've done quite a bit of searching but I didn't find this exact scenario.  And because this is a very busy season for my client I'd like to try to resolve this issue with minimal impact to the running VM's.  As of right now all of the VM's are working - I just can't manage them from the Failover Cluster Manager (which means that I can't even run live-migrations).  I feel pretty much stuck.

   Can anyone give me any (safe) guidance on how to proceed?  I'd certainly appreciate the help!!!

dave

Disk Space in Windows Drive

November 21, 2013, 12:10 am

≫ Next: 2012 R2 Failover Cluster Move Storage Fail to load Cluster Disk list

≪ Previous: Can't access Failover Cluster Manager in Windows 2012 R2 Cluster - The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server

$

0

0

Hello

We have two Windows 2008 R2 Enterprise Servers, configured as nodes for a failover cluster, hosting virtual machines. Both are connected to a SAS disks Storage system.

Although it work fine there is something I am a bit worried. Windows disk space is 130 GB in both servers, and in both of them there are only 30 GB free, I have been looking for the files or folders that take so much space, but I couldn't find it.

Is this normal? Does it has to do with the cluster configuration. I looked even in hidden files or folders but I didn't find the reason.

I could not understand how such a Windows installation take as much space.

Thank you very much.

Kind Regards.

David

---

2012 R2 Failover Cluster Move Storage Fail to load Cluster Disk list

November 19, 2013, 3:36 pm

≫ Next: cluster failure

≪ Previous: Disk Space in Windows Drive

$

0

0

2012 R2 Failover Cluster 2 CSV's.

Attempting to move VM's from CSV1 to CSV 2.

Move Virtual Machine Storage does not load cluster disks available to migrate the VM.

Lower left hand cluster disk area shows "loading..." for over 12 hours.

cluster failure

November 19, 2013, 4:33 pm

≫ Next: Error: The computer is joined to cluster when creating the Cluster

≪ Previous: 2012 R2 Failover Cluster Move Storage Fail to load Cluster Disk list

$

0

0

hello,

I had an two node iis nlb cluster which failed in a strange way. both nodes were able to respond internally to web requests.

while the cluster was active with both systems, there was no activity on the internet for iis requests.

one of the systems was 'stopped' on the cluster which then allowed service requests to the internet.

still both servers on internal and external individual dns were able to respond.

I removed one of the servers which was suspect from the cluster then I added it back to the cluster.

the cluster then started responding properly.

is this normai? what could have caused this failure? I looked in the logs however was not able to find anything there.

thanks in advance,.

Error: The computer is joined to cluster when creating the Cluster

February 28, 2012, 1:33 pm

≫ Next: Microsoft failover clustering feature

≪ Previous: cluster failure

$

0

0

Hello Guys,

I have created a cluster to configure Hyper-V for 2 Nods, everything was greate and works perfectly, next day the storage hang and the cluster didn't work any more, I have destroyed the cluster the removed the cluster feature from both nods, deleted the cluster-computer from AD and the deleted the storage. after we fixed the storage, I have reconnect the storage, installed the cluster service on both nods, then I have validate the configuration and I had everything green 100%.

while creating the cluster, I faced an issue Unable "to successfully cleanup" I kept trying and removed the anti-virus, restarted the servers manytime, then I ended up to have another error, direclty when I add the server name on the creat cluster wizard, its telling me that the computer I'm adding is joined to cluster.

I think I need to do some cleaning to the previous cluster, can I have some help here ?

Regards..

Nour

---

Nour

Microsoft failover clustering feature

November 21, 2013, 10:20 am

≫ Next: server 2012 R2 failover clustering

≪ Previous: Error: The computer is joined to cluster when creating the Cluster

$

0

0

Hello,

I have a question regarding microsoft's failover clustering feature. I have 3 physical servers(Windows Server 2008 R2) that i want to add to a cluster so that the virtual machines can be Highly Available. The 3 servers are connected to a DAS. I have created only 1 LUN on that DAS.

The problem is that the LUN needs to be associated with one owner(one of the three servers) and if that owner fails all the VMs go down(from all 3 servers). Is there any way to corect this with only one LUN, or do i have to create 3 LUNs and asociate each server with a LUN?

At first when i created the LUN, i only created one because i've read that one is enough, but now i consider it a flaw.

Any suggestions?

server 2012 R2 failover clustering

November 22, 2013, 1:14 am

≫ Next: CAU Scan for updates fails with CIM Exception 0x8024401c

≪ Previous: Microsoft failover clustering feature

$

0

0

I am setting up a new domain with 2 windows server 2012.

I have the first server setup for AD, DNS and DHCP, this is the primary DC.

I have the second one is joined to the domain and promoted to a DC.

I am trying to cluster between the 2 but when I do the validation, I get this error:

I have done nslookup on both servers and they can see each other.

I have been googling for the past day to try and find the answer.

 

any help would be appreciated

CAU Scan for updates fails with CIM Exception 0x8024401c

November 22, 2013, 12:42 pm

≫ Next: Cannot connect to roles that are on other nodes

≪ Previous: server 2012 R2 failover clustering

$

0

0

Try to update Windows 2012 HyperV Cluster but CAU wizard failed to preview needed updates with CIM exception FAILED HRESULT 0x8024401c message. Failover Cluster Management Console logs message with EVENT ID 2002 for all Cluster Nodes.

Last month CAU completed successfully.

Cannot connect to roles that are on other nodes

November 22, 2013, 6:03 pm

≫ Next: Nic Teaming and Clustering

≪ Previous: CAU Scan for updates fails with CIM Exception 0x8024401c

$

0

0

In Failover Cluster Manager, If I am on node 1. I can only connect to VM's that currently reside on node 1. Trying to connect to a vm on node 2 or 3 results in this error.

An authentication Error has occurred. The specific target is unknown or unreachable.

Remote Computer  servername.domainname.com  (example)"

In Hyper-V Manager  I get the same result.  Logged into Server1 , connect to Server1 roles, all okay. Add Server2 and Server3 to Hyper-V Manager, try to connect to VM's on Server2 or Server3.  Same above error.

DNS is perfect, I can ping each server from each server.

Cluster Verification is clean...

---

Nic Teaming and Clustering

November 23, 2013, 8:27 am

≫ Next: Shadow copies on a failover cluster

≪ Previous: Cannot connect to roles that are on other nodes

$

0

0

I have 3 nodes in a cluster running server 2012. I have 2 ex4550 juniper switches connected via virtual chassis cables so they act as one switch.  I have 2 10G Nic teams on each server.  They are switch independent and I have one nic set for standby.  The other team is used for my ISCSI connection and is set the same way.

I am getting a ton of errors on the cluster events, but everything seems to be working fine, well seems to be.

What would be the recommended network setup for connecting these 3 servers using 4 10G adapters to 2 ex4550 switches?

Thank you

Shadow copies on a failover cluster

November 24, 2013, 2:54 am

≫ Next: Linux NFS share to Windows 2008 R2 cluster

≪ Previous: Nic Teaming and Clustering

$

0

0

I have a failover cluster with two nodes and 8 disks. Four of the disks are Data disks, while the remaining four holds shadow copies for the shared folders on the data disks.

Code:

E:\(Data1) F:\(ShadowCopyOfD1)
G:\(Data2) H:\(ShadowCopyOfD2
And so on and forth.

But this is a configuration I can only make by using the Configure Shadow Copies option in Windows Explorer (right-click a volume to see the option). Because by using that option, I can choose on which volume I would like to store the shadow copies of the volume I want to create Shadow Copies of.

For it to work properly, I have to create the shadow copies schedule on both nodes of the cluster, and the passive node will have errors in the system log that it can not create shadow copies, obviously because it is not holding the disks/volumes, because they are owned by the active node, and there are no error messages in the active nodes logs.

I figured I could use failover cluster manager to create the shadow copies, and in that way I would not see the errors in the system log of the passive node, but if I try to use the Shadow Copies tab in Failover Cluster Manager, I can create shadow copies, but I am not able to choose on which volume I would like to put the shadow copies.

Anyone ever dealt with this issue?

Linux NFS share to Windows 2008 R2 cluster

November 24, 2013, 7:59 pm

≫ Next: How to set up a compute node only application network

≪ Previous: Shadow copies on a failover cluster

$

0

0

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.

How to set up a compute node only application network

November 22, 2013, 2:43 am

≫ Next: Windows Storage Server 2012 Failover Cluster with NFS Resource

≪ Previous: Linux NFS share to Windows 2008 R2 cluster

$

0

0

I am setting up a compute cluster using HPC Server 2008 R2 cluster manager and have my compute nodes isolated on a private network, to which the head node is also connected, but I also have a high-speed application network running between my compute nodes only. How do I configure the networking for the cluster? I can't use topology 3, as my head node only has 2 network adapters.

Thanks

Windows Storage Server 2012 Failover Cluster with NFS Resource

November 25, 2013, 1:04 pm

≫ Next: 2012 R2 failover cluster requirements

≪ Previous: How to set up a compute node only application network

$

0

0

Hi, 

(I'm not at work at the moment so I'm attempting to write this from memory). As stated in the title, I have a 2012 Cluster with the NFS resource added to my File Server role, however, upon fail over, the resource fails to start stating that the group / resource isn't in a valid state? and I have to kill the multiple "Server for NFS" tasks that start, restart the service and try again.. this can take a few attempts before it eventually comes on-line.

Is there anything I can check that may be causing the issue?

Also, I'm not sure if this should be posted as a separate question but we're having issues with files being copied from Unix to the NFS share in the 2012 cluster. We have a feeling it's down to the file names as they contain colon's. I've tried to use character translation but it doesn't appear to be working, does anyone have any have any examples of how character translation should be configured?

Thanks in advance,

Mark.