Node

After fielding a number of questions around this topic recently, its come to my attention that there is a misunderstanding on how to implement the vSphere Storage Appliance (VSA) for certain ROBO solutions. The requirement around the tie-breaker code (VSA Cluster Service) is either misunderstood or misinterpreted when it comes to 2 node VSA deployments at remote office/branch office (ROBO) sites. Let’s be clear about it now – the VSA needs 3 votes in order to function correctly as a cluster. In a 3 node VSA deployment, this is not an... [Lire la suite]

A little while ago David posted a really handy solution for evacuating a Hyper-V cluster node on shutdown automatically. The issue that he is trying to address is that normally you should not just shutdown a node in a cluster, rather you should manually move all virtual machines off of the cluster node first.  If you just shutdown a node in a cluster all the virtual machines will be failed over using quick migration. David solved this problem by writing a PowerShell script that works with clustering to live migrate the... [Lire la suite]

If you are running Hyper-V or Virtual Server in a clustered configuration - you need to be careful about just shutting down a cluster node.  If you need to shutdown one of the cluster nodes you need to first open the cluster manager and select to either failover or offline each of the virtual machine resources on the cluster node in question. The reason why you need to do this is because if you just shutdown the cluster node (without first offlining or moving the virtual machines) Hyper-V and Virtual Server will try to save... [Lire la suite]