Book Tipp: Introduction to Windows Server Failover Clustering

Hi everybody,

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.

PowerShell Script to move Hyper-V Hosts to special OU and add them to group

Hi,

as another part of my deployment scripts, I developed a small script that does following tasks.

  1. Moves all Hosts with *SVR-HV* from Computers to Hyper-V OU
  2. Creates Group for Hosts
  3. Adds Hosts to group

 

Small scripts to configure Livemigration on Hyper-V Hosts & Cluster

Hi everybody,

based on blogposts by John Savill and Ben Armstrong I developed two small scripts to configure Livemigration on Hyper-V Hosts and Cluster to save some time for configuration. I will no provide my whole script but I think the two snipes will help you too 🙂

First one you run on all Hyper-V Hosts.

The next one you run on the cluster its self. You only need to run one, depending on what suits you best.

 

 

How do you get your System Center Virtual Machine Manager really highly available

Sometimes when I’m invited to visit a customer to “optimize their high available virtual machine manager”, I normally see following configuration.

VMMHA01

 

When I ask why they say it is high available, they normally tell me that they can move the machine from one host to another. Normally i ask now “And what happens when you need to patch the SQL DB, VMM or Windows Server or the storage fail?”

Here comes the point where most people realize that high availability means other things than moving services from A to B.

So now let us think what we need to get our VMM Server high available.

On the VMM Site we need following parts:

  • two VMM Management Servers running in a Cluster
  • two Database Servers running in a Cluster
  • two Fileserver running in a Cluster as Library server
  • two Hyper-V Hosts for VM Placement
  • two Storages with Storage Replication

VMMHA02

 

When it comes to a very big Hyper-V and VMM Environment, I would suggest to run you Management Systems in a separated Hyper-V Cluster. That helps you to keep your VM workload running even when you need to take down your fabric cluster in maintenance mode.

VMMHA03

How to plan redundancy for Scale out Fileser

Hey everybody,

after I posted some of my thoughts I normally put behind Hyper-V redundancy, today I want to show you some examples how you could plan redundancy for Scale out Fileserver.

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 need no geo-redundant storage solution. Please notice, for a JBOD based Scale out Filserver you need at least a minimum of three JBODs. For converged Scale out Fileserver with Windows Server 2016 you will need 4 equal Scale out Fileserver Systems.

Sofs01

Traditional Scale out Fileserver with Storage Spaces and JBODs

sofs02

Traditional Scale out Fileserver with SAN Storage Backend

sofs03

Scale out Fileserver with Storage Spaces Direct in 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 or serverroom fails.

sofs04

With Storage Spaces Direct in Windows Server 2016 and RDMA RoCE

sofs05

Scale out Fileserver with classic SAN storage replication