Proper environment planning mitigates many risks in the future. For the lab network in this scenario, four network adapters have been configured for each host. Both lab hosts are not doing any NIC teaming for simplicity sake. However, you would want to team your adapters in production to avoid having a single point of failure in any one network.
With the above networks in mind, we assign IP Addresses to each server in our desired subnet ranges. This would need to be thought through in advance.
Hyper-V cluster storage is a crucial point for building a cluster. Of course, setting up iSCSI on vendor hardware of your choice or software iSCSI can be different depending on the vendor, so always follow the methods defined for each. Note: Quorum is the mechanism in a Windows cluster that is used to make sure that in the event of something going down between parts of a cluster, you always have a majority of cluster resources available for the cluster to function.
In the screenshot below, we have created the two target names: a quorum volume to be used as a disk witness and a volume to be used for our cluster shared volume. To install the Hyper-V role service, run the following command in a PowerShell command prompt:. Note: You can use the get-disk command to show disk information and make sure the Hyper-V cluster shared storage is online and healthy.
Configuring virtual switches is needed for proper Hyper-V failover cluster network configuration. Note: Set up your virtual switch names identically between both hosts as we need to ensure that the virtual switches match, especially when performing a live migration. Even though we have shared storage from an iSCSI target perspective, we need to make sure the storage that houses our VMs is set up on a Hyper-V clustered shared volume.
Note: If you have a management workstation to connect using the Failover Cluster Manager , you can look at storage with the graphical user interface GUI by connecting to Windows Failover Cluster. Here we can easily see the Disks available and the roles assigned to them.
Below we see both the Quorum and VMs disk that is designated as a cluster shared volume. Now that we have our clustered shared volume setup, we can change our Hyper-V settings to use our Hyper-V cluster shared volume as the default location for storing our VMs. What’s new in Failover Clustering. Scale-Out File Server for application data. Deploy a two-node file server. Cluster and pool quorum.
Using guest virtual machine clusters with Storage Spaces Direct. Prestage cluster computer objects in Active Directory Domain Services. Configuring cluster accounts in Active Directory. Manage the quorum and witnesses.
VM load balancing. Cluster sets. Cluster operating system rolling upgrades. Upgrading a failover cluster on the same hardware. Deploy an Active Directory Detached Cluster.
Failover Clustering PowerShell Cmdlets. High Availability Clustering Forum. Troubleshooting using Windows Error Reporting.
Leave a comment