I have used a VIrtual STARWIND server on a older esx server, and performance was o.k. In testing, i find the Starwind actually works VERY well. Puts the server in maintinance, and allows for safe shutdowns, without the esx server doing scsi/ISCSI scans and such. Little workaround makes the HA/DRS stop fully funcioning. It is more a Soft iscsi issue, than a ESX or Starwind issue. Every esx server - Maintinance mode first. Once starwind is up, then turn on every esx server.Ĥ. Every ESX server has to be off, prior to starting the Starwind server.ģ. My workaround - as it would be in a production environment is.Ģ. I run 4x ESX Servers, and 1 physical Win2k3 Server w\ Starwind running (home lab- evaluation is thy friend)ġ.
Starwind iscsi target free#
I myself am running the Starwind 4.0 free san. It isn't particuarly clear though where the error lies - with ESXi/VSphere or with Starwinds. I notice that the Starwind engineers hang around these forums quite a bit so, hopefully this info will be of use. Rescan the adapter again in VSphere client and the ISCSI volume will show up again and the datastore will once again be accessible. Remount the image and name it exactly as it was named previously (before you removed it) When you lose the connection to the device, remove the device from Starwind (Right click, remove)Īdd a new device to the connection, choosing the option to remount an existing image. Rescanning the ISCSI HBA adapter in the VSphere client, just doesn't help.at all. I have dug around and found the following Ĭhecking the starwind logs for the connection after a reboot you do see a LOGIN_REJECT line. However, it does seem odd that after a reboot connection to the ISCSI volumes is lost. I am 'so glad' that someone else has also been having this problem! I get exactly the same thing, albeit in my home test environmentįirst of all, I appreciate this isn't a 100% real life comparison given that all the components of my VSphere and ISCSI environment get shutdown when I'm not using them. Our qa and uat environments are available to external clients so i need something I am confident I can restore easily in case of troubleshooting or sudden unavailability. We have one serving 1.2tb been up for 217 days and one serving 800gb been up for about 180 days so they are solid and stable but still have reservations of putting into an environment that requires higher uptime. Our openfilers have done well since I set them up. My novice linux skills keeps me from wanting to move something like this into a rock solid environment. This is troublesome since although the iscsi host should never need to go down you never know when you may need to restart it for something.Īnyone experienced this or have any suggestions? We are using openfiler for other projects but the two issues there, a) lack of good performance monitoring tools and b) no real way to backup and restore in case of disaster (aside from just copying the config). Even though the target is listed in the storage adapters I have to manually remove the iscsi target's ip, remove the static mappings and then re-add it to storage adapter and re-create the data store. I tried refreshing the storage pools as well the storage adapter. It seems if the san for whatever reason is restarted the esx servers will not pick it up again once its back online.
Starwind iscsi target software#
I am using version 4 of the software but am finding an issue. We have 14 x 300gb 15k drives in an md1000 that came from our exchange server configured in raid 10 i am wanting to share between two qa/uat esx hosts. I have been testing this as a cheap SAN solution for our development environment.