The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
Mmooney wrote:Is that a yes or no? And being on an open forum like this you should expect many questions that are the same, or similiar. Hope you don't spend your billion in one place.
Thanks
broman wrote:Billion hah Anton? Is MS buying you out to build iSCSI target functionality in Windows or something?
On a serious note, a good methodology is to force CHAP authentication on the target so only the intended initiator can connect to it, comes in handy when there are too many hands in the cookie jar, like your typical IT department.
Zamar25 wrote:Is it possible to work with iSCSI Target from several Initiators, if only one at a time writes data to it? What will happen with data and FS in this scenario? Or StarWind Target blocks write operations from any iSCSI Initiators but one, regardless concurrent or sequential? I found that only one Initiator actually left files on an attached image that could be found in Win Explorer, when 2 Initiators were connected, despite they were used one at-a-time - why?
What happen with your above mentioned in the 2-st post plan to offer own arbitrator or clustering FS? Is there a free Open Source iSCSI Arbitrator or Clustering FS that you tested and can more or less suggest to try using without FS corruption risk?
I think, this question is typical enough to explain "what happen" in your FAQ, which so far just suggests use clustering FSs, but says nothing otherwise.
Yes, it did. even after 8 yearsanton (staff) wrote:Update. We do support clustered scale-out NAS (NFS or CIFS/SMB) on top of a clustered SAN. So you can run HA for high availability and failover NAS on top of it (what most gateway-style scale-out NAS vendors do). Check these HOWTOs on how to do this:
http://www.starwindsoftware.com/configu ... or-smb-nas
http://www.starwindsoftware.com/configu ... or-nfs-nas
Hope this helped