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.
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

Similar Messages

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".

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.

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.

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.

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.

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.

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 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/

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
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 Subscriber Support, contact [email protected] .

2 Node Hyper-V failover cluster with sql server

I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over.
The second will act as virtualized failover of the main node with failover instace to act as active to active approach.
I hope can someone give me an advice with my question.

I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over.
The second will act as virtualized failover of the main node with failover instace to act as active to active approach.
I hope can someone give me an advice with my question.
Sure you can do that. But it's a long story what's better SQL Server FCI or AlwaysOn. See:
FCI Vs. AlwaysOn
http://msdn.microsoft.com/en-us/library/ff929171.aspx
(biggest issue with AlwaysOn - it does require Enterprise license so is COSTY)
Good idea to ask here:
SQL Server High Availability and Disaster Recovery
http://social.technet.microsoft.com/Forums/sqlserver/en-us/home?forum=sqldisasterrecovery
In any case you'll need either physical or virtual shared storage. For FCI to host everything and witness disk and for AlwaysOn just for witness (AlwaysOn does replication between DAS on it's own).
Good luck :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

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]

How to recover from accidental VM role removal in Hyper-V Failover Cluster Manager?

Hello
My VMs are still available in Hyper-V Manager but they are no longer available in Cluster Manager. I am curious if there's a way to move them back into the Failover Cluster Manager while retaining their GUIDs?
I know I can manually create a new VM and add the existing VHD but that process recreates a new GUID causing the VM to regard the stuff I wanted as old.
I have tried to follow
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/14/recovering-virtual-machines-in-hyper-v-server-2012-r2-part-1.aspx but I am curious if there's a faster way to do this without becoming a scripting genius overnight.
Thanks,
Prince

Thanks for the reply but that does not help.
I am not looking to move my VMs to a remote Host but rather looking to repopulate the fail-over cluster manager with the existing VMs in Hyper-V Manager. In a sense, I am looking to reuse the existing GUID without creating new ones.
Again, my VMs are alive in Hyper-V Manager but are currently not available in Failover Cluster Manager.
Any scripting assistance will be greatly appreciated.
Thanks,
Prince

Windows 2012 Server multinode failover cluster (6 nodes)

Dear All,
We are facing problem of Huge time takes for cluster validation test on IBM Blade Server with Storage. The details are given below.
Escalated with IBM OEM, confirmed that "there is no hardware issue with Server and storage, Please take support from OS (Microsoft) OEM as 2 node validation test is working fine".
Server : IBM BladeCenter S-HS23
OS : Windows 2012 X64 Datacenter Edition
MPIO.SYS Version: Default came from OS
Note : Failover cluster validation test is successful on 2 nodes in 15 min with 5 shared volumes between 2 nodes and also between set of 2 on other 6 nodes.
When we are running validation test on 6 nodes its taking 30 min in list and more than 45 min potential cluster disk.
Thanks in adv for support from your end....
T & R,
Kamlesh
kamlesh

Hello,
I'd ask in the
High Availability (Clustering) subforum of the Windows Server forums.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog:http://unlockpowershell.wordpress.com
My Book:Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

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?

Similar Messages

Maybe you are looking for