Microsoft File Services Failover Clustering in ESXi 4.1

[jvidalll]

Helllo,

I have a virtualization environment with 5 hosts ESXi 4.1 on location A and two hosts ESXi 4.1 on location B, all with high availability that is the host 7 ESXi 4.1 are highly available.

I need to configure a Microsoft File Services with Failover Clustering in ESXi 4.1

I want to create a Microsoft File Services with Failover Clustering with 3 virtual machines that are 2 VM on location A and 1 VM on location B.

Cluster Geographic VM is supported on vmware?

What is the maximum nodes in the cluster in Guest VMs?

Thank you,

jVidalll

[a_p_ · Accepted solution]

Welcome to the Community,

Only 2 node MSCS is supported in ESX(i)

Take a look at http://kb.vmware.com/kb/1004617 for the MSCS documentation links.

André

[jvidalll]

Hi André,

Thanks for the reply.

Ok - Only two node MSCS is supported in ESX

So I can have 2 node MSCS in ESX and 1 physical node? in total 3 nodes - 2 VMs and 1 physical -  Is supported?

It is supported geographically?

Thanks you!

jvidalll

[idle-jam]

only 2 nodes setup is supported. as long as the two location comply to the needs of MSCS like gigabit and etc, you're good to go ..

[bulletprooffool]

Unfortunately, VMware will only support the 2 node scenario.

If this is dev / staging, I gues syou could try doing this with Raw Device Mappings - but you will not be supported in case of any issues.

[jvidalll]

OK, All right.

Understands only 2 nodes.

Question:
I can create 1 node at location A and 1 node at location B.

So cluster geographically is supported?

Tks,

jvidalll

[a_p_]

From the documentation (see my first post) you can see that the supported MSCS type is the one with the quorum on a shared disk. There is no reference to a "Geographically Dispersed Cluster" if it is this you are asking about. Anyway, the questions with a setup in different locations would be equal to to the ones for a standard installation: bandwith, latency, ...

André

[jvidalll]

hello

Thank you All

jvidalll