<div>
<div class="content wysiwyg-content">
I'am testing in a lab environment Hyper-V Failover-Szenarios. We now have 4 Hyper-V Host with 2 Storages separeted in two locations. 
 
Location 1 
HV1 
HV2 
Storage1 
Virtual Machine 1&amp;2 
 
Location 2 
HV3 
HV4 
Storage2 
Virtual Machine 3&amp;4 
 
All Devices in the same cluster are linked with 10 GB (LAN and ISCSI). What would here be the best choice for the quorum configuration? 
 
If i do not configure someting...the quorum is p.e. on HV1. When the Storage1 fails with the quorum on it...the whole cluster crashes...even the 2 nodes in the other location and the storage2 goes also offline. 
with the separete storage. 
 
thanks you for your answer. 
 
m@2
</div>
</div>

I'am testing in a lab environment Hyper-V Failover-Szenarios. We now have 4 Hyper-V Host with 2 Storages separeted in two locations.

Location 1
HV1
HV2
Storage1
Virtual Machine 1&2

Location 2
HV3
HV4
Storage2
Virtual Machine 3&4

All Devices in the same cluster are linked with 10 GB (LAN and ISCSI). What would here be the best choice for the quorum configuration?

If i do not configure someting...the quorum is p.e. on HV1. When the Storage1 fails with the quorum on it...the whole cluster crashes...even the 2 nodes in the other location and the storage2 goes also offline.
with the separete storage.

thanks you for your answer.

m@2

Hyper-V Quorum for 4 Nodes and two storages

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.