none
Hyper-V Server 2008 R2 - Enabling Failover Clustering with current workload RRS feed

  • Question

  • Hello Hyper-V experts,

    This definitely falls under a "general" question, but I am trying to avoid some common pitfalls and I'm hoping that some of you have some excellent advice for me to save time/headaches.

    I am tasked with turning a poorly configured 2-node Hyper-V "instance" into a true failover cluster.  Basically, "Company A" has 2 Hyper-V servers (Hyper-V Server 2008 R2...Core) running completely independent of each other.  There is a fibre switch and a SAN behind them, but no zoning is performed in the fibre switch and also (naturally) the LUNs are not shared between the two servers, but rather statically mapped individually to their respective server.

    My task is to correct the LUN mappings, create zoning in the fibre switch, and enable failover clustering.  There are about 15 VMs running between the two Hyper-V nodes, both Windows and Linux.

    The Hyper-V servers themselves have 4 NICs, but they are configured in the worst possible fashion.  Each NIC is configured as its own virtual switch and virtual machines are just spread out all over the place between the various virtual switches.  Obviously, I will need to create a Live Migration network, a host management network, a *new* virtual switch for the VMs, and a cluster communication network (i.e. crossover cable).

    Based on past experience, when I make these changes, I am going to not only lose network connectivity to/from the virtual machines, but I am expecting that I'll also have to readdress each of them.

    Am I correct in this assumption that each VM will have to be readdressed individually?  Are there other pitfalls/problems that I need to look out for from the Hyper-V side of things or in general?

    I am not a big fan of "changing the tire while I'm driving down the road", but that is what I've been tasked with for this customer.

    Thanks in advance for any advice that you may have for me.

    Friday, May 15, 2015 3:40 AM

Answers

  • If you want to make your life much, much, much easier, get a third server. Install Windows Server 2012 R2 on it with Hyper-V configured as you want it to be and create a single node failover cluster using the shared storage.  Trying to 'fix' things using just current hardware will be very, very messy and prone to lots of issues.

    Since you want to change the NICs to a more manageable configuration, that means those systems are going to have to have some downtime.  Schedule the movement of the VMs during maintenance periods, using something like VeeamZip to quickly move the VM from one of the old systems to the new system.  After the VM's files are on the new system, set them to be highly available, reconfigure the networks, and update the integration services.

    I would first create a 'messy' VM on your existing environment and perform a trial move on it to document the steps needed.  That will take the stress out of moving your production machines over.  Once you have moved all the VMs off one of your existing nodes, rebuild it to Windows Server 2012 R2, add Hyper-V configured as you want it to be, and join the cluster.

    Rinse and repeat.


    . : | : . : | : . tim

    Friday, May 15, 2015 3:35 PM