I'm actually in the process of writing an article on this, which will be
online in a few days.
The trick is to have your virtual machines on separate clustered disks,
when you add a new VM, the cluster service checks at what clustered disk
the virtual machine is hosted. It will create "Service and application
groups' based on what disks these Virtual Machines are found.
Example:
server1
server2
are on iSCSI Cluster Disk 1.
server9
server8
are on iSCSI Cluster disk 2
When creating/importing vm's into cluster manager, it will create two
groups, the first containing server1 and server2, the other containing
server9 and server8.
A mistake that would be easily made would be to expect each VM to be
assignable to a node. Since we are using shared storage, that is of
course not possible. Therefore the groups rather than the machines can
have node affinity.
If you have created separate groups as described above, you'll find that
in the properties of the -groups- it is possible to select a particular
node to be the 'preferred owner'. This way you can 'balance' the usage
of resources on you fail over cluster.
As said: I'll have a more in-depth & details article available soon on
my website. Until then, I hope this explanation answers your question!
/ ) Regards,
/ /_________
_|__|__) Paul Weterings
/ (O_)
http://www.servercare.nl
__/ (O_)
____(O_)
John wrote:
Quote:
> Hi all,
>
> If I have 12 VMs on two nodes Windows 2008 x64 Enterprise servers and I
> configued it as A/A failover cluster, does that mean that I only need two
> service and application group which each group hosts 6VMs (one 6VMs active on
> node1 and another 6VMs active on node2 )
>
> What if I go for A/A/A cluster with three nodes, does that mean I need three
> service and application groups (which each group hosts 4VMs (one 4VMs active
> on node1, one 4VMs on node2 and one 4 VMs on node3)? How do I configure
> PREFERRED OWNERS between them? any suggestions?
>
> Thank you!
>
>
>
>
>