In your case, you don't have to "Select the same target and again click Connect" because you don't have more than 1 NIC per SAN. Ah - okay. I was confused partially because of the diagram, and partially because of the fact that I do have two NICs (but only one of them would be considered ...

I'm having a difficult time phrasing this differently, but I'll try. In the first document, you linked to (http://www.starwindsoftware.com/configuring-ha-storage-for-live-migration-on-windows-server-2012) under "Connecting Targets" (this is for the iSCSI Initiator) it says: "Click Dis...

Sorry - I wasn't clear. The initial disk setup is fine - each machine has one NIC for heartbeat and one for heartbeat+data. When I'm talking about these configuration steps, I'm specifically referring to the iSCSI initiator setup as in the first document you linked to.

Okay - in the first document, under "Connecting Targets", it says: "Click Discover Portal. Enter an IP address of each StarWind Server in the appropriate field of the Discover Target Portal dialog. Click OK." But while that says "an IP", there are 4 addresses there. Fro...

I'm sorry, but I'm having a hard time figuring out what info on those docs is applicable in our case. The majority of them seem to reference Hyper-V, which we're not using. I'll keep going through them, but so far I haven't seen our situation in these guides. Thank you. ETA : Ah - my apologies. I ju...

Also, I'm a bit confused - if I set up the HA image, it's (kind of) mirrored between the two devices, correct? So when I set up my iSCSI connectors, do I point them at the primary target, or the secondary, or set up MPIO and point to both?

I've installed the free version of Starwind iSCSI SAN to test and see if it would be usable for our purposes and therefore whether we should purchase it. We're trying to set up a Windows Failover Cluster for our HPC Head nodes, so we need two shared locations - one for the witness, and one for the H...