Cluster Drive not moving to the other cluster server during a fail over, or a  move to the other cluster server.

Posted on 2011-05-06
Last Modified: 2012-05-11
- Two server Hyper-V cluster server with Windows 2008.
- One SAN disk Cluster drive for the virtual file server storage virtual hard disk.
- One SAN disk Cluster drive for the operating system virtual hard disks and virtual machine configurations.

In Failover Cluster Management under Services and Applications there is a Service / Application group Virtual Machines. In this group all the Hyper-V Virtual Machines are added. One SAN Cluster Disk G: is added to this group for storage of all the virtual hard disks and virtual machine  configurations. The File server has its own Cluster Disk E: for the file server storage virtual hard disk. The operating system disk and the virtual machine configuration of the File Server resides on the other SAN Cluster drive G:, together with all the other virtual harddisks of the other virtual machines.  E: is listed in Failover Cluster Management / Storage under Available Storage. Cluster Drive G: is connected to the Virtual Machines Services and Applications group.

During a fail over or a move of the virtual machines to the other node, the File Server storage Cluster Drive E: doesn't move to the other node. The Virtual Machines and G: the main Cluster Drive do move to the other node. This results in a File Server that fails to start on the active cluster node. After rebooting the passive cluster node, the E: custer drive is moved, forced to the active cluster node and the file server can be successfully started.

It has worked before, suddenly is doesn't anymore. Something or someone must have changed something on the server. What could be the reason that the File Server cluster disk doesn't move to the other cluster server?

I'm not sure, should the disk be added to the Virtual Machine Services and Applications for it to move to the other cluster? Or could adding this disk to the Virtual Machine Services and Applications result in any other error?
Question by:NicoNL
    LVL 61

    Expert Comment

    Resource groups are independent.
    You mention 3 of them, so you need to move each - cluster group, virtual machine group and e drive group.
    also adjust dependencies so that services start PROPERLY on move.
    LVL 41

    Expert Comment

    If you con go to R2 on the hosts (either Windows 2008 R2 or Hyper-V Server 2008 R2) you can use CSV volumes instead which are a lot simpler because CSV volumes are available to each host simultaneously.

    Author Comment

    There is only one cluster group, "virtual machine". E: and G: are Storage cluster disks, no cluster group. G: is added to cluster group. E: is listed as available storage. There is no option to manualy move cluster disk E: to the other node. I can imagine that the reason why E: doesn't move along with virtual machine to the other node anymore, is that someone have removed E: from the cluster group virtual machine. I'll try adding E: to the cluster group and see what happens. Then it should move along with the cluster group just as drive G: does, which is added.

    I wish I could go to 2008R2, but there is no budget for that at the moment.

    LVL 41

    Expert Comment

    Hyper-V Server is free, so going to it is just a matter of the time to do it. Hyper-V Server 2008 R2 in functionally equal to Windows 2008 R2 Enterprise Core installation. To do the installation you will need to evict one node from the cluster, do a clean install of Hyper-V Server, make it a 1 node cluster, move over all of the VMs, upgrade the other Windows 2008 host to Hyper-V Server 2008 R2, and then join that node to the cluster.

    Author Comment

    Thanks for the tip. I overlooked the free R2 Hyper-V core version. I like the R2 live migration, CSV made possible.

    After joining the new R2 node to the cluster, I need to evict the the other 2008 node make the R2 a 1 node cluster and upgrade the 2008 to 2008R2 and join that node to the cluster, so I have 2 identical 2008R2 cluster servers? Won't I run into errors during this upgrade path, joining the R2 node to the cluster, because the two servers aren't identical, one being 2008 and the other being 2008R2? I remember having Cluster error events during upgrading the servers from 2008 SP1 to SP2, about the server versions not being identical.

    Can you use RDP and the Gui interfaces to manage the upgrade, or is PowerShell mandatory?
    LVL 41

    Accepted Solution

    You can't mix and match different OS in the same cluster, so 2008 SP2 and 2008 R2 can't be in the same cluster. You also can't mix a full Windows OS with Core in the same cluster. You will need to go to a new cluster. I do all management from Hyper-V GUI tools after I install the Hyper-V Server OS. You can also use RDP for basic OS management (initial configuration, initial network configuration, iSCSI setup).

    Author Comment

    Adding E: to the cluster group Virtual Machine was indeed needed to make it move along with it.

    Thanks for the tips about upgrading to 2008R2. I'll keep it in mind as an option.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Highfive Gives IT Their Time Back

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
    Sometimes drives fill up and we don't know why.  If you don't understand the best way to use the tools available, you may end up being stumped as to why your drive says it's not full when you have no space left!  Here's how you can find out...
    This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    10 Experts available now in Live!

    Get 1:1 Help Now