Solved

vSphere/VMware: File Server Cluster vs FT - need some advice

Posted on 2011-02-11
6
1,204 Views
Last Modified: 2012-05-11
Hi,

We are migrating a windows 2003 File server (on a physical server) to a Windows 2008 R2 Standard that will run on a ESX cluster.

The new server has to have the same server name and IP than the old once once the data is migrated.

We would like to implement redundancy for this server we know that we can go with FT (VMware) or build a MS Cluster.

We looking for some feedback about which approach is going could be better, basically PROs and CONs about implementing the rundancy with FT vs MS cluster.

Also could someone provide some advise or guideliness about implementing a MS cluster on a vSphere 4.1 cluster. Do we have to use RDM LUNs? I assume that the cluster nodes have to placed each in a different ESX host, etc...

Thank you in advance for your help.

 

 
0
Comment
Question by:llarava
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 37

Expert Comment

by:Neil Russell
ID: 34873463
If you have an ESXi cluster with SAN storage for your VM's and full failover enabled on the cluster then why would you want to cluster the MS side of things as well? You are talking about running a cluster on a cluster?

Just have a good solid ESXi cluster with your infrastructure on it.

Don't forget about licensing when you enable failover!
0
 

Author Comment

by:llarava
ID: 34873544
I think you got it right I want a cluster within a cluster because every type of cluster is going to provide me with a different type of redundancy.

The ESX cluster is providing physical node redundancy in case of a phyisical node failure.

FT or MS cluster will allow me to failover in case of an application failure which is complimentary to HA.
 
0
 
LVL 28

Expert Comment

by:bgoering
ID: 34876283
In a nutshell -

MSCS clustering will provide for a seperate server to pick up the load in the event the server (vm) goes down that is hosting the resource, file shares in your case. IP address for the fileshare floats amongst whichever cluster node is hosting it at the time. You would not name your new vms netbios name the same as your existing box as that name would be used for the cluster resource. See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004617 for more information and links to resources on implementing a MSCS cluster on vSphere. The biggest CON for this is that there is a brief outage while the share transfers from one server to another.

VMware Fault Tolerance (FT) is fairly new technology that allows a mirror vm to run in lockstep on a seperate ESX(i) host than the vm that is hosting the application. In the event the ESX(i) host goes down the mirror vm immediately picks up the load with no down time to users. Optionaly FT can be configured to start a 3rd mirror vm on yet another ESXi host in case of failure of the first. The biggest CON is that you are limited to a single processor for FT virtual machines.

Another possibility is VMware High Availability (HA). Like FT, HA protects you against a failure of the ESX(i) host. When a host failure is detected, HA will restart the vms that were running on the failing host on other ESX(i) hosts in the cluster.

Summary - FT has 0 downtime, but is limited to a single processor. Does not protect against a failure in the OS or Application running on the vm because the failure would be mirrored on the FT vm.

HA has moderate downtime as the vm must be restarted (and possibly go through error recovery) on another host. Again won't protect against an OS or App crash, but like FT only protection is for a failure of the ESX(i) host.

MSCS has generally minimal downtime. It does protect against a failure of the OS or App of a virtual machine as well as when the hosting vm disappears because of a host ESXi crash.

Personally for maximum protection with only minimal down time I would go with MSCS + HA.

Good Luck
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 28

Expert Comment

by:bgoering
ID: 34876299
Just notice your statement "FT or MS cluster will allow me to failover in case of an application failure which is complimentary to HA"

Actually FT will mirror any application failure in near real time on the FT vm... as stated above. MSCS is the ONLY one of the three that will protect somewhat aganst Application and OS failure.

I don't believe you can use MSCS with FT (but not absolutely sure) because using rdm disks (as opposed to vmdk) I am pretty sure is still not supported with FT. RDM would be needed to set up MSCS.
0
 

Author Comment

by:llarava
ID: 34888006
Just notice your statement "FT or MS cluster will allow me to failover in case of an application failure which is complimentary to HA" - You are correct.

A couple of  questions:

1.) VMware FT  

FT replicates the active VM to a passive VM in order to provide redundancy in case of a node failure. We will be implementing FT on a File Server which will be created as follows:

C:\OS -> 1 single vdisk 40 GB
D:\DATA -> 1 single vdisk 400 GB

Then they both will be placed together within the same VM.

According to disk configuration if we want to enable FT does it mean that OS and DATA volume need to be replicated? In other words that we are going to have 2 VM whit a total of 440GBs?  


2.) MS cluster that will run over the VMWare ESX cluster.  

Are you aware of the requirements that are needed in order for the ESX server to support a MS Cluster? For example do we need to use RDM Luns for the QUORUM or the cluster shared drive where the data is going to be shared by the two VM cluster nodes?

0
 
LVL 28

Accepted Solution

by:
bgoering earned 500 total points
ID: 34888173
The disk is not replicated during fault tolerance - it is the running state of the machine. The mirror machine runs in lockstep with the primary machine and executes all of the same instructions. What VMware does is intercept the scsi I/O on the mirror machine and return whatever the I/O result was on the primary to the mirror, but doesn't actually do the I/O. In case of failover VMware quits intercepting the I/O and allows it to go through to the disk. But it is the same disk.

For number 2 you can download the appropriate detailed info from VMware from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004617 - this will point to a pdf with all of the details. The answer depends on many things, the version of windows, is it cluster in a box, across boxes, between a vm and a physical server, etc.
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Changing logon server question 5 67
Why my host server dont ping gateway ? 6 53
SonicWall blocking access to MS RDP RemoteApp 24 42
VMDK convert to VHD question 3 24
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

726 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