User Tools

Site Tools


virtualization:microsoft:hyper-v-cluster

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
virtualization:microsoft:hyper-v-cluster [2014/07/07 09:44]
gcooper
virtualization:microsoft:hyper-v-cluster [2019/05/20 11:29] (current)
gcooper
Line 1: Line 1:
 ====== Clustering with Hyper-V ====== ====== Clustering with Hyper-V ======
  
-See also **[[https://www.sonoracomm.com/wiki/doku.php?do=search&id=hyper-v|more Hyper-V pages]]**+See also **[[https://virtualarchitects.com/wiki/doku.php?do=search&id=start&q=hyper-v|more Hyper-V pages]]** 
 + 
 +:!: When you are running Hyper-V in a failover cluster, you should always create the VMs in Failover Cluster Manager. If you create the VMs with Hyper-V Manager, you need to specify the location of the VMs configuration and virtual hard disk so they are located on a clustered shared volume.
  
 **Hyper-V Server 2012, Powershell and SMB**: http://blogs.technet.com/b/keithmayer/archive/2012/12/12/step-by-step-building-a-free-hyper-v-server-2012-cluster-part-1-of-2.aspx **Hyper-V Server 2012, Powershell and SMB**: http://blogs.technet.com/b/keithmayer/archive/2012/12/12/step-by-step-building-a-free-hyper-v-server-2012-cluster-part-1-of-2.aspx
 +
 +**Step by Step, 2012 R2**: http://blog.augustoalvarez.com.ar/2014/03/27/step-by-step-creating-a-windows-server-2012-r2-failover-cluster-using-starwind-iscsi-san-v8/
  
 http://kristiannese.blogspot.com/2010/10/how-to-make-your-existing-vms-highly.html http://kristiannese.blogspot.com/2010/10/how-to-make-your-existing-vms-highly.html
Line 27: Line 31:
 |**Replica Traffic** |Used for virtual machine replication through the Hyper-V Replica feature | |**Replica Traffic** |Used for virtual machine replication through the Hyper-V Replica feature |
 |**Virtual Machine Access** |Used for virtual machine connectivity - Typically requires external network connectivity to service client requests | |**Virtual Machine Access** |Used for virtual machine connectivity - Typically requires external network connectivity to service client requests |
 +
 +===== Default Hyper-V Storage Locations =====
 +
 +Once your cluster is up and running and you have a Cluster Shared Volume (CSV), you must store your VMs in the CSV to make them highly available.
 +
 +http://blogs.technet.com/b/canitpro/archive/2012/09/11/default-file-locations-in-hyper-v.aspx
 +
 +===== Live Migration =====
 +
 +http://blogs.technet.com/b/iftekhar/archive/2010/01/18/microsoft-virtualization-hyper-v-live-migration-network-configuration.aspx
 +
 +**Configuration Guide**: http://technet.microsoft.com/en-us/library/ff428137%28v=WS.10%29.aspx
 +
 +It's recommended to use Cluster Shared Volumes (CSV) for Live Migration storage for these reasons:
 +
 +  - All cluster nodes have concurrent access to shared storage
 +  - Multiple VHDs can be stored on a single shared volume
 +  - No drive letter problems
 +  - Faster failovers
 +
 +:!: Live migration will only use one TCP stream between any pair of hosts.  For faster live migration, use 10GbE NICs or migrate to multiple destinations over multiple 1GbE NICs.
  
 ===== Basics ===== ===== Basics =====
virtualization/microsoft/hyper-v-cluster.1404747840.txt.gz · Last modified: 2014/07/07 09:44 by gcooper