5nine Software Vice President Symon Perriman published a book with some cool best practices for configuration Windows Server Failover Clusters. 🙂
Greate stuff and great to read.
You can download it here.
my buddy Carsten Rachfahl (Mr. Hyper-V) is presenting the CLOUD & DATACENTER
It will take place in Duesseldorf at the 12th of May 🙂
You will see lot’s of great content and speakers. 😀
Get your early bird ticketes (99€) today here.
a few minutes ago my blogpost about Microsoft Azure Backup Server went only @ Azure Community Deutschland.
To read it please click here.
today again a post out of my daily business. When I’m out in the field and I plan a new cluster, I also need to decide how many and what type cluster redundancy I need to implement. For that I have some thing like a blueprint or decision matrix in my mind which I leverage.
Today I want to give you a small view into this matrix. 🙂
When to choose a redundancy where only one or two cluster nodes can fail?
That is the most common and easiest why for node redundancy in a cluster. It means you have enough nodes in your cluster to cover one or two node failures. You would choose that cluster config when all of your nodes are in one datacenter or server room and you have no additional space or need to replicate your virtual machines.
Cluster operating with one storage
Cluster operating with two storages
Hyper-V Hyperconverged with Windows Server 2016
When to choose a redundancy where you can choose half of the nodes?
In this scenario you can lose one half of your nodes but you need to fulfill some more requirements like storage replications or direct WAN links. You would normally use if you want to keep your services alive if one datacenter, server room or blade center fail.
Datacenter redundancy with storage
Redundancy with compute and storage blades
Different locations with Hyperconverged Hyper-V in Windows Server 2016
When to choose replication?
I normally prefer Hyper-V replication only as a warm standby option. That could be an option for example when you want to secure your datacenter and have no storage replication so that you can reboot your virtual machines on other hardware.
Replications is no replacement for a cluster and I would not recommend to replicate databases, exchange server, domain controller or other applications where the vendor officially supports replication.
that’s a post I try to write since a few month. It’s related to an issue or misunderstanding which a customer of mine had.
He wanted to try to get a PXE Boot triggered by DHCP throw a virtual Machine Hosted on Hyper-V. For those of us who are familiar with vitualization, that sounds very simple because the solutions was, he didn’t tagged all VLANs on the Switch and virtual Machine.
For those who are not that familiar, I want to give you a short list what you need to do, to get traffic through you physical and virtual switches right to you virtual machines.
Physical Switch Configuration
First thing you need to do, is to tag all VLANs were your virtual Machines will have access to, to the physical ports of you Hyper-V Host and virtual Switch is connected too.
As example: You have one virtual machine in VLAN 10 and one in VLAN 233. Both need connect to your physical network. You Hyper-V virtual Switch is connected to Switch 1 on Port 12 and Switch 2 on Port 14. That means you need to tag VLAN 10 and VLAN 233 on Switch 1 Port 12 and Switch 2 Port 14.
Virtual Switch Configuration
Now you need to configure the virtual switch and that’s the point most people don’t see while working with virtualization. In nearly all Hypervisors you have an operation softwarebased layer 2 switch running. That switch needs to be configured too. That is mostly done via virtual machine settings.
In our example we need to set the VLAN Tag on the switch for a virtual machine on Hyper-V. To do so, you need to change the settings for the virtual machine network interface.
You can also configure the switch for VLAN trunking. My Bro Charbel wrote a great blog about how to configure the virtual switch in that way. What is VLAN Trunk Mode in Hyper-V?
In our example you need to know one more thing. In Generation 1 Hyper-V VMs only the legacy network adapter is able to perform a PXE boot.