- Top 10 new features in Windows Server 2012 R2 - Mon, Jun 10 2013
- FREE: Unitrends Enterprise Backup Free Edition - Hyper-V and VMware backup - Tue, Nov 6 2012
- FREE: Remote Desktop Manager - A powerful RDP client - Wed, Sep 19 2012
Windows Server 2008 version ^The first item to consider is which Windows Server 2008 licensing to use. If you take a look at Microsoft ’s comparison of editions for R2, you’ll see that Standard, Enterprise, and Datacenter editions each come with a different number of virtual machine instances included. Standard edition does not support Failover Clustering, so make sure you have Enterprise or Datacenter. Enterprise includes rights to run up to 4 virtual machines. Datacenter includes rights to run an unlimited number of virtual machines.
|Edition||Virtual Machine rights||Failover Clustering|
Basic Host Setup ^Preparing the hosts to support clustered virtual machines involves a few basic steps.
- Add hosts to your domain - Other Hyper-V configurations do not require that the host be a domain member. However, to support clustering, the hosts must be domain members.
- Install Hyper-V Role - At this point, the hosts could run virtual machines. However, they cannot yet be made highly available.
- Install Failover Clustering Feature - This enables clustering on your server. One of the cluster objects that can be created is a clustered virtual machine.
Server Manager with Hyper-V and Failover Clustering installed
Network Connections ^Now you should make sure that all network connections are in place are ready to go.
- Client Connectivity - this connection should be on a subnet that is accessible by client computers and will also have access to Active Directory. For discussion, let’s say the host will connect to Active Directory using subnet 10.10.10.0 with subnet mask 255.255.255.0.
- Heartbeat - In a two-node cluster, this could be a direct connection. If you have more nodes, or want to build with scalability in mind, a switch should be used. For this one, let’s use 192.168.1.0 with subnet mask 255.255.255.0.
- SAN Connection - This connection needs to provide Gigabit speed or faster between the hosts and the SAN. For this one, let’s use 172.16.1.0 with subnet mask 255.255.255.0.