How Does HyperV Clustering Work
-
Am I missing something with this topic? isn't Hyper-V 2012 R2 supposed to manage Clustering between 2 or more Hyper-V servers, or is there supposed to be another server, running a specific clustering service.
This seems like he's installed Hyper-V 2012 R2 onto an existing Windows Server 2012 R2 server as a "service". Rather than to bare metal.
Maybe I'm missing something, I'm not a hyper-v expert.
-
Great question - in light of the free StarWind virtual SAN, I've been wondering this myself.
A basic walk through of install would be great.
-
It makes sense that a separate host would have to be configured to monitor both Hyper-V servers to see if one goes down. So does that mean you have to perform this with a 3rd server?
Could the clustering service be run as a VM on each Hyper-V host to monitor the other?
-
By 2012, HyperV can do clustering for free. Here is Microsoft's own guide for this using PowerShell to manage it:
-
@DustinB3403 said:
It makes sense that a separate host would have to be configured to monitor both Hyper-V servers to see if one goes down. So does that mean you have to perform this with a 3rd server?
Could the clustering service be run as a VM on each Hyper-V host to monitor the other?
Nah, that's what the heartbeat betweent he boxes is for...
-
@Dashrender said:
Great question - in light of the free StarWind virtual SAN, I've been wondering this myself.
A basic walk through of install would be great.
StarWind does not use Windows Server Failover Clustering (WSFC) in a normal operations mode so it's another story...
-
@scottalanmiller I've read that article, and the guy states that he already has his own shared storage for that setup... It could be done using a standalone SMB-3 server for the cluster's storage, but I find that a bit risky as it is a SPOF.
This is where a product like StarWind shines if you have multiple NICs in your computer.
-
Exactly, SMB3 is just as dangerous as iSCSI or any other SPOF approach. It's an easier to manage protocol, so better in that regards, but that is about it.
-
@DustinB3403 said:
This seems like he's installed Hyper-V 2012 R2 onto an existing Windows Server 2012 R2 server as a "service". Rather than to bare metal.
Hyper-v never runs as a "service". Hyper-v is always a Type 1 Baremetal hypervisor running below the OS. Even if you have a Windows GUI on top of it.
-
Best way I've heard it described is that when you enable Hyper-V on a Windows Server, your Windows Server Core (or GUI) becomes the Linux equivalent of Dom 0
-
@dafyre said:
Best way I've heard it described is that when you enable Hyper-V on a Windows Server, your Windows Server Core (or GUI) becomes the Linux equivalent of Dom 0
And exactly like installing Xen onto Linux, Xen inserts itself as a "shim" under Linux and then reboots, booting into Xen instead of Linux. HyperV is identical, inserting itself as shim under Windows, rebooting and booting into HyperV instead of Windows.
HyperV is modeled identically after Xen.
