Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

I am pretty new to Hyper-V virtual but I have 2 Hyper-V Clusters, each with 2 Nodes and a SAN, 1 Physical Domain Controller for failover cluster management and 1 virtual domain controller as backup. All is running well, no issues. I installed
windows updates on the physical DC and upon reboot, got an error 5120 on cluster 2 that says "Cluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'. All I/O will
temporarily be queued until a path to the volume is reestablished. It pointed to the 2nd node in that cluster as being the issue but when I look at it, it is online and all healthy so I don't understand why the error was triggered and if the DC would
go down for a failure, would that node not be able to access the CSV permanently.
Appreciate any help anyone can provide.

Hi mtnbikediver,
In theory, if you has the correct configuration of cluster the DC restart will not cause the CSV down, does your shared storage installed on your DC? Did you run
the cluster validation before you install the cluster? We strongly recommend you run the cluster validation before you build the cluster, same time please install the recommend update of 2008 cluster first.
Recommended hotfixes for Windows Server 2008-based server clusters
http://support.microsoft.com/kb/957311
I found a similar scenario issue the DC restart will effect the cluster network name resource offline, but it is for 2008R2.
Cluster network name resource cannot be brought online when one of the domain controllers is partly down in Windows Server 2008 R2
http://support2.microsoft.com/?id=2860142
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Server 2012 R2 Running Failover cluster role on Domain Controler

I absolutely need to have Domain controller running failover Cluster node,
we have been doing it in 2008r2 and there are documents from Microsoft stating it is possible but not recommended
but the document is for 2012, I am running 2012r2
I can install failover clusting role on a 2012r2 server and from a Member node install the cluster but when I need to add the nodes that are Domain controller they thry to add but then they timeout after 5 minutes, then they delete the node that was try
to add and clean up
I have tried the CNO record and try to install DC befor and after Cluster role,
HELP
thx

Not supported, see this KB:
http://support.microsoft.com/kb/281662
Run the DC in a virtual machine, and then put it on top of the cluster.
Thanks!
Elden

Requirements for similar hardware in a 2012 Hyper-V failover cluster?

Simple question:
How similar does the hardware have to be on the host servers in a Windows Server 2012 Hyper-V failover cluster?
We have 6 dell servers that we are hoping to use for building a Windows 2012 Hyper-V cluster.
As I recall from our existing 2-host Hyper-V cluster, which is running on 2008 R2, there are fairly harsh demands in the cluster validation wizard with regard to similarity of hardware. So I am wondering if it will work?
The servers in question are 3 x R620, 2 x T410 and 1 x T610 Dell servers. So 3 x 12th generation servers and 3 x 11th generation servers
The servers all use Intel CPUs:
R620: Xeon E5-2670/2680
T410/610: Xeon X5650
and broadcom NICs:
T610: Broadcom 5709c
2 x T410: Broadcom 5716c
3 x R620: Broadcom 5720
Windows 2012 is supported by Dell on all the servers.
Shared storage will be on an SMB3 file share.

Simple question:
How similar does the hardware have to be on the host servers in a Windows Server 2012 Hyper-V failover cluster?
We have 6 dell servers that we are hoping to use for building a Windows 2012 Hyper-V cluster.
As I recall from our existing 2-host Hyper-V cluster, which is running on 2008 R2, there are fairly harsh demands in the cluster validation wizard with regard to similarity of hardware. So I am wondering if it will work?
The servers in question are 3 x R620, 2 x T410 and 1 x T610 Dell servers. So 3 x 12th generation servers and 3 x 11th generation servers
The servers all use Intel CPUs:
R620: Xeon E5-2670/2680
T410/610: Xeon X5650
and broadcom NICs:
T610: Broadcom 5709c
2 x T410: Broadcom 5716c
3 x R620: Broadcom 5720
Windows 2012 is supported by Dell on all the servers.
Shared storage will be on an SMB3 file share.
You'll be fine with a listed config no need to have identical machines. The only thing I'd try to change is use the same NICs all-around if possible.
P.S. Make sure you understand SMB share is a single point of failure unless SoFS or "old skool" NAS failover is configured. But it adds latency so using shared storage
directly w/o a file transport is FASTER and CHEAPER.
StarWind iSCSI SAN & NAS

Virtual memory in a hyper-v failover cluster

Hi all,
We have a window 2008 R2 hyper-V failover cluster working fine. It has two hosts, with 104 GB of memory on each of them.As I added new virtual instances I had been updating memory.
The point is that as I do that page file for virtual memory has been growing and now System volumen has only 20 GB free space.
I had like to go on adding memory for new virtual instances, so I need to fix this problem. Which is the recommended configuration for this? Can I disable virtual memory as long as I have an enormous quantity of physical memory available?
Thank you very much.
Kind regards,
David.

Hi,
that enormous page file at Hyper-V Servers make no sence.
We do not need to configure virtual memory for physical Memory that is assigned to VMs.
Check this for more informations:
http://blogs.technet.com/b/rwagg/archive/2010/03/08/how-big-should-pagefile-sys-be-on-a-server-2008-hyper-v-server.aspx
Hope that helps
Regards
Sebastian

Hyper-V Failover Cluster virtual guests suddenly reboots

The environment is Server 2012 R2 using dual clusters--a Hyper-V Failover Cluster running guest application virtual machines and a Scale-Out File Server Cluster using Tiered Storage Spaces which are used to supply SMB3 shares
for Quorum and CSV. Has anyone had this problem?

Anything relevant in the host or guest event logs? I would also check the cluster event logs to see if there are any indications there as well.
Does the guest go down hard or gracefully reboot?
Need more info.
Andy Syrewicze
Come talk more about Hyper-V and the Microsoft Server Stack at
Syrewiczeit.com and the Altaro Hyper-V Hub!
Post are my own and in no way reflect the views of my employer or any other entity in which I produce technical content for.

Moving VMs from Standalone Hyper-V to Hyper-v Failover Cluster

Hello All.................I need to move Virtual Machines from Standalone Hyper-V based on Windows Server 2012 R2 to a Hyper-V Failover Cluster based on Windows Server 2012 R2.
- The VMs OS is Windows Server 2012 R2
- Applications installed on VMs are SCCM, SCOM, SharePoint, etc.
1. I am looking for a Checklist that I can run through and move them. To make sure I do not miss out anything.
2. Would a downtime be required in this scenario while the VM is being moved?
3. What requires special attention in this scenario?

Thanks for the reply.
So, I do not need to do anything and just simply add both the cluster and standalone into VMM and then simply use the Move option. Please, confirm if I have understood it correct.
Yes. But be carefull. First shut down your VM's
if possible and configure them in such a way they don't automatically start. If you install the SCVMM Agent, some Hyper-V related services are restarted, when some VMs start during that process you system may stall. I have seen this multipe times.
There is another dirty option that worked of us perfectly. Export the VMs. Then import those VMs to a local disk on one Hyper-V Server. Refresh the Hyper-V Server and Virtual Machines on that Hyper-V Server. Give it a few minutes. Then do
a Live Migration while at the same time makeing it "Highly Available" by moving it to your CSV. Works flawlessly. DO NOT IMPORT THE VMS TO YOUR CSV, otherwise you can't change it to "Highly Avaiable" unless you have
two CSVs. Importing it straight to a CSV does not make them Highly Available.
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Crystal Reports XI R2 and Window Server 2008 Hyper-V environment

Hello,
Is there any known issue that Crystal Reports XI R2 running on Window Server 2008 Hyper-V enviroment?
I tested on Development Server which is Window Server 2008 and it is working fine but when tested with another servers which are in Hyper-V enviroment and ASP.NET program keep crushing.
I got the below error on my event log:
Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e023cf, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x03976ce8, process id 0x%9, application start time 0x%10.
Thanks,
Yin

Hi Yin,
Hyper-V I assume is the Hyper threading Intel and others enabled correct? Should not make a difference other than performance. You are still using 1 CPU so the cycles are being split between multiple programs. Not really an advantage.
Try using ProcessMonitor and search on access denied to see what is having the problem.
Other issue is CR XI R2 is not supported on windows 2008, or at least you should be running Service Pack 6 to at least get Windows 7 and Vista support, which is about the same as Windows 2008.
Go to our download page and install SP 4 full build and then SP 6. ( assuming you don't have any SP's installed ) or look in the download area and download all of the patches from SP 4 as well as the distribution files for how ever you are deploying your application.
Thank you
Don

Guest cluster on Hyper-V failover cluster

I want to implement Hyper-V failover cluster on Windows Server 2012 R2. Then Install Windows 2003 R2 as Hyper-V guest OS.
Do you know whether Windows 2003 R2 guest cluster support on Hyper-V on Windows Server 2012 R2?

Hi steventsf,
Windows Server 2003 R2 with Service Pack 2 (SP2) is in the supported guest operation system list :
http://technet.microsoft.com/library/hh831531.aspx
The guest OS is independent of hyper-v host , I think windows server 2003 R2 SP2 guest cluster is a supported scenario .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Heartbeat Network inside Hyper-V Failover Cluster

Dear All,
I need to build an SQL Server 2012 SP1 Two-node cluster inside Hyper-V Failover Cluster. There is only one virtual switch in the Hyper-V Failover Cluster environment which is being
used for communication to the outside world using VLAN Tagging. Now, since SQL Server 2012 Failover Cluster would require a heartbeat network as well and although possible to assign VLAN tag to the heartbeat adapter and use that for hearbeat, but since there
would not be any gateway on the heartbeat network, it would render the VLAN tagging useless, so is following plan good enough:
1. Create an Internal Virtual Switch on all nodes of the cluster with the same name
2. Link the heartbeat adapter of the virtual machines to the Internal Virtual Switch
Is it good enough? or is there any other better way?
Thanks in advance.

I am not an expert on this, but here is what I would do.
Create the VLAN and use that to keep the network setup as easy to understand as possible. Our Hyper-V cluster is only using IPv6 on the heartbeat network, and that is working like a charm. I would do the same inside the hyper-v hosts if I need to builld
a virtual cluster.
What is the reason for deploying a failover cluster for SQL inside Hyper-V? Wouldn't a log shipping "cluster" provide a more secure solution for your SQL?
/Martin
Exchange is a passion not just a collaboration software.

Removal of Node from Hyper-V Failover Cluster

Hello All....................I have a 8 node Hyper-V Failover Cluster based on Windows Server 2012 R2. I am facing some issues with one of the servers, so I have decided to take that node out of the Hyper-V Failover cluster. I would appreciate if someone
could share the steps that I should take to ensure smooth removal of node especially with respect to CSV Volume and Quorum. THanks.

Hi Sir ,
Please try the following command (before you do this please live migrate VMs to another nodes ):
Remove-ClusterNode –Name node4 -Force
For this command please refer to :
http://technet.microsoft.com/en-us/library/hh847251.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Failover Cluster Networking Configuration After Install

Hello All,
Is it possible to install hyper-v and failover or in other words create a hyper-v failover cluster and then configure the networking part of the solution later? As I am coming into
terms with the networking part of it, wanted to do it later after the install. Is it possible?
And from later configuration, I am trying to say, creation of NIC Team, Virtual NICs, VLAN tagging, etc.

Hi,
Failover cluster deployment requires network connectivity between cluster nodes. You can't create a cluster without properly configured TCP\IP on cluster nodes.
http://OpsMgr.ru/

Hyper-V Failover Cluster Configuration Confirmation

Dear All,
I have created a Hyper-V Failover Cluster and I want you to confirm if the configuration I have done is okay and I have not missed
out anything that is mandatory for a Hyper-V Failover Cluster to work. My configuration is below:
1. Presented Disks to servers, formatted and taken offline
2. Installed necessary features, such as failover clustering
3. Configured NIC Teaming
4. Created cluster, not adding storage at the time of creation
- Added disks to the cluster
- Added disks as CSV
- Renamed disks to represent respective CSV volumes
- Assigning each node a CSV volume
- Configured quorum automatically which configured the disk witness
- There were two networks so renamed them to Management and Cluster Communication
- Exposed Management Network to Cluster and Clients
- Exposed Cluster Communication Network to Cluster only
5. Installed Hyper-V
- Changed Virtual Disks, Configuration and Snapshots Location
- Assigned one CSV volume to each node
- Configured External switch with allow management option checked
1. For minimum configuration, is this enough?
2. If I create a virtual machine and make it highly available from hyper-v console, would it be highly available and would live
migrate, etc.?
3. Are there any configuration changes required?
4. Please, suggest how it can be made better?
Thanks in advan

Hi ,
Please refer to following steps to build a hyper-v failover cluster :
Step 1: Connect both physical computers to the networks and storage
Step 2: Install Hyper-V and Failover Clustering on both physical computers
Step 3: Create a virtual switch
Step 4: Validate the cluster configuration
Step 5: Create the cluster
Step 6: Add a disk as CSV to store virtual machine data
Step 7: Create a highly available virtual machine
Step 8: Install the guest operating system on the virtual machine
Step 9: Test a planned failover
Step 10: Test an unplanned failover
Step 11: Modify the settings of a virtual machine
Step 12: Remove a virtual machine from a cluster
For details please refer to following link:
http://technet.microsoft.com/en-us//library/jj863389.aspx
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MS- WIN SERVER 2008-R2 FAILOVER CLUSTER --ERROR 1127 ,1583

DEARS ,
I HAVE BEEN FACING PROBLEM FOR MY WINDOWS FAIL OVER CLUSTER SCENARIO.
THE ERROR CODES ARE 1127 AND 1583 WHICH ARE STATING THAT
All nodes IPv4 networks should be configured properly.
Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster. If the adapter is to be used by Windows Failover Cluster, the IPv4 properties of the adapter should be changed to allow assignment
of a valid IP address that is not in the APIPA range.
However , I have checked that all of my NIC adapters have valid Static IP addresses. Also , when one of the nodes is down ,it cannot look for another node.
Please advise for the solution.

Hi,
Could you clarify your described “Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster.” Did you
found one of your cluster node “automatically” have the APIPA address? If so, it seems is the IP conflict issue.
If it is not the IP address conflict issue, please try to disable your all the nodes firewall
or AV soft have the event 1583 typically cause by this function incorrect configured.
More information:
Event ID 1127 — Cluster Network Connectivity
http://technet.microsoft.com/en-us/library/dd353958(v=ws.10).aspx
Event ID 1583 — Network Connectivity and Configuration
http://technet.microsoft.com/en-us/library/ee830320(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Network Name Resource Availability - failover cluster error 1196 on Hyper-V 2012 R2 nodes

Hello,
We're getting this error in our even logs of our four node failover cluster, we tried deleting Host A record in DNS management, that did nothing.
Failover cluster event: 1196
"Cluster network name resource 'CAUCrgt8' failed registration of one or more associated DNS name(s) for the following reason: This operation returned because the timeout period expired.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server."
And this resource http://technet.microsoft.com/en-us/library/cc773529%28v=WS.10%29.aspx did not help in solving this.
Do you guys have any other suggestions we could try to resolve this error?

Hi Jonas,
Please offer us which platform server you are using, such as if you are using server 2012 please refer the following update first.
Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters - http://support.microsoft.com/kb/2784261
If the update not work please ppply Full Control permissions for the Cluster Name Resources in the DNS console.
More detail information please refer the following article:
Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering - http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-troubleshooting-event-id-1196-microsoft-windows-failoverclustering.aspx
DNS Registration with the Network Name Resource -
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Server 2008 Hyper-V Failover Cluster Error on Domain Controller Reboot

Similar Messages

Maybe you are looking for