Why I love ESX soo much, don't have to worry about M$ shared volume issues with failover of VM's and accessing .VMDK and .VMX files from the same volume, updating them and likewise.
Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] Cell:401-639-3505 From: Andrew S. Baker [mailto:[email protected]] Sent: Tuesday, July 20, 2010 8:14 PM To: NT System Admin Issues Subject: Re: iSCSI and shared volumes Time for plan B. :) You have correctly surmised the problem. -ASB: http://XeeSM.com/AndrewBaker Sent from my Motorola Droid On Jul 20, 2010 7:30 PM, "Mark Smith" <[email protected]> wrote: I have a few 2008 R2 servers that are stand alone (not clustered) Hyper-V hosts. They are connected via iSCSI to a single 5TB volume on a DELL/Equallogic PE6000 iSCSI target. The idea is to have the VM's for all the Hyper-V hosts in one volume on the PE6000 and have all the hosts access that same volume simultaneously. I am having a problem in that when one host writes to the volume the other hosts don't see the changes. Should this configuration work as I'm intending or do I need to go with clustering in R2 and use CSV (Cluster Shared Volume) ? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
