vmware 5.5 / server 2012 / failover clustering

Posted on 2014-08-07
Last Modified: 2014-08-08
Hi Experts,

We have been asked to do some work on a file and print failover cluster that is using raw device mappings for its storage.

Part of this work will involve testing that the failover of the file server resource actually works as expected.

Is there any reason as to why it might fail or any caveats that somebody should be aware of?
Question by:cmatchett
    LVL 116

    Assisted Solution

    by:Andrew Hancock (VMware vExpert / EE MVE)
    The biggest issue you may come across is whether your SAN supports SCSI-3 Reservations, for the RDM, but most SANs supported this function.

    The new Failover Cluster Wizard in WIndows 2012, verifies the requirements and compatibility of RDMs for nodes, and tests failover as part of the wizard.

    So, it's very straight foward.

    Make sure both nodes are on different ESXi hosts, and if using DRS, create an anti-affinity/affinity rule to ensure that both nodes are on different hosts....

    BUT.....why A Cluster...

    Why not use a single Print Server and File Server on VMware, and use VMware HA ?

    Same far as availability......if a host fails, VM will be restarted automatically.....

    Setup for Failover Clustering and Microsoft Cluster Service - ESXi 5.0/vCenter Server 5.0

    or is this requirement for Patching?

    Author Comment

    Dunno why i said file and print, it's only a file server cluster.  This cluster is already configured and operational, we have been asked to test it.

    The only reason i can think of that somebody would want a cluster is for patching reasons.  Like you say, it's already highly available because it is virtual machine that is protected by HA.

    A highly available print server in MS terms now is a single virtual machine that is highly available.  No longer any support for clustering of the printer spooler.
    LVL 116

    Accepted Solution

    Two methods for testing, as testing is already now completed in the Creation through the wizard.

    1. Power OFF the VM (not shutdown) Power OFF! This is a hard failure, and Node 2, should take over when failover occurs.

    2. Other Test, is to POWER OFF the HOST, the VM is on!

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Every now and then, Microsoft does something that totally impresses me. It doesn't happen often, but in this case I must say I am thoroughly impressed with Windows Server Backup. One of the long time issues with Windows Backup has been the ability t…
    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.
    Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
    In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…

    761 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

    8 Experts available now in Live!

    Get 1:1 Help Now