There are no updated versons (guess author is waiting for V8 to be released) but nobody really consideres MS target as the candidate for production. For a few reasons: 1) it's a single point of failure (yes, you can cluster it
but that would require a configured Windows cluster which is in need of an own shared storage, so what's use in MS target then? + it would be active-passive scenario) and 2) MS target does not RAM or flash caching and no
I/O acceleration so is DOG slow (even with R2 and flash cache you cannot host VHDX from MS target on a cached storage spaces). From the StarWind side it's active-active and clustered on it's own and does I/O acceleration.
+ MS has no clustered file system like VMware has (VMFS) so is actively pushing SMB 3.0 as a storage for VHDX thus MS iSCSI target is fading in darkness. It cannot be used to feed shared storage to Scale-Out File Servers and
for us it's one of the production scenarios.
So basically comparing StarWind and MS target is "apples to oranges" (c) ...
Adam Błaszczykowski wrote:Hi,
I found an old article on blog that compares performance of StarWind iSCSI target vs Microsoft iSCSI target on Windows 2008 R2. Here is link to this article
http://blogs.serioustek.net/post/2012/0 ... art-1.aspx
Do you know if there is newer article that compares performance and functionality of StarWind iSCSI target with Windows 2012 or with Windows 2012 R2 ?
Best Regards
Adam Błaszczykowski
