I would suggest that the VM's accessed by each host be on separate LUN's. OpenFiler, as of the this past may did not support SCSI-3 reservations which can wreak some havoc with multiple ESXi hosts accessing one lun.
I used it in production, successfully for over a year due to a necessity of inheriting an ill-conceived budget from my predecessor and enduring a probationary period of proving myself and my methodology to the firm. The situation I Was using it in was one VM host with three guests all of which were not at the time considered mission critical. On Fri, Nov 20, 2009 at 9:16 AM, Steven M. Caesare <scaes...@caesare.com>wrote: > Doing some testing with OpenFiler for iSCSI SAN testing. > > > > I’m presenting LUN’s via GigE links to my ESXi boxen hosting Win2K3 and > Win2K8 VM’s. > > > > So far I’m pretty impressed… and the price is right for a home network. > > > > Anybody played with it and/or have any pointers to best practices or > performances considerations? One of the things I’m wondering about > particularly is if there’s any advantages to using the Windows iSCSI > initiator as opposed to letting ESXi own the LUNs and present the storage as > local volumes to the Win boxen. > > > > Thanks. > > -sc > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~