we are running a 2003 physical cluster and now we want to migrate this to a 2008 vm cluster.
any advice on this? I assume to do 2008 VM clustering, vmotion will not work right?
please advice
Thanks
Windows clustering is not supported with VMotion, HA and DRS.
---
MCP, MCTS, VCP, VMware vExpert '2009
Application cluster has several limitations...
No VMotion, no snap, no VCB, ...
See also:
Andre
Furhter to this if you are running ESX 3.5 or lower windows 2008 clustering is not supported as ESX 3.5 does not support SCSI3.
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth VCP / vExpert
VMware Communities User Moderator
Blog: www.planetvm.net
Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts
ok when I upgrade to vsphere. 2008 clustering will be supported right? so both vms needs to be on the same host? should I be using RDM disks?
If you want you 2008 cluster to be supported - http://vmguy.com/wordpress/index.php/archives/1019
---
MCP, MCTS, VCP, VMware vExpert '2009
Yes you need to use RDM with scsi controller of the type -
1. virtual - if your nodes are on the same base ESX.
2. physical - if your nodes are on different base ESX.
NUTZ
VCP 3.5
(Preparing for VCP 4)
And a FC based storage back end,
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth VCP / vExpert
VMware Communities User Moderator
Blog: www.planetvm.net
Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts
What about using iSCSI inside the guest and connecting to iSCSI volumes for shared storage that way? At that point it is a guest level configuration that is essentially out of VMware's hands and so it shouldn't impact support.