This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
virtualization:microsoft:hyper-v-cluster [2014/04/28 17:11] 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:// | + | See also **[[https:// |
- | http:// | + | :!: 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**: | ||
+ | |||
+ | **Step by Step, 2012 R2**: http:// | ||
http:// | http:// | ||
Line 14: | Line 18: | ||
http:// | http:// | ||
+ | |||
+ | **2008 R2**: http:// | ||
+ | |||
+ | ===== Network Traffic Types ===== | ||
+ | |||
+ | **Network Recommendations, | ||
+ | |||
+ | |**Management** | ||
+ | |**Cluster** | ||
+ | |**Live Migration** | ||
+ | |**Storage** | ||
+ | |**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 | | ||
+ | |||
+ | ===== 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:// | ||
+ | |||
+ | ===== Live Migration ===== | ||
+ | |||
+ | http:// | ||
+ | |||
+ | **Configuration Guide**: http:// | ||
+ | |||
+ | 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. | ||
===== Basics ===== | ===== Basics ===== | ||
Line 19: | Line 57: | ||
http:// | http:// | ||
- | The Hyper-VTM Failover Cluster should be created in the following order: | + | The Hyper-V Failover Cluster should be created in the following order: |
- | - Configure physical NICs on both Hyper-VTM servers | + | - Configure physical NICs on both Hyper-V servers |
- | - Configure storage resources on both Hyper-VTM servers | + | - Configure storage resources on both Hyper-V servers |
- | - Install Hyper-V role on each servers | + | - Install Hyper-V role on each server |
- | - Install Failover Cluster feature on both servers | + | - Install Failover Cluster feature on each server |
- Create the virtual networks used for the Virtual Machines | - Create the virtual networks used for the Virtual Machines | ||
- Validate the cluster configuration | - Validate the cluster configuration | ||
- Create the cluster | - Create the cluster | ||
- | For a step-by-step guide on Hyper-VTM Failover Clustering | + | **Step-by-step guide on Hyper-V Failover Clustering**: http:// |
:!: Redundancy for iSCSI connections is typically done with MPIO, not with bonding/ | :!: Redundancy for iSCSI connections is typically done with MPIO, not with bonding/ |