Chris,
well, so far so good. Here we are:
1) Performance. I would not say MS initiator sucks but it would be easier to tune OWN iSCSI Intiator running against OWN iSCSI Target. B/s we have control over source code. I guess other storage companies would LOVE to do the same but they are on budget and have to limit their activities with target software only (target CAN be user mode app, service or whatever but you need to have extremely hardly trained team to create high performance iSCSI Initiator. Running in kernel. No choice!)
2) Features. We're positioning StarPort as virtual storage centre and not as just iSCSI initiator. RAM disk and virtual DVD is what we have now. We'll add hard disk image volume mounting soon and virtual CDs from other formats (just have treaty with CD emulator company not to do this for some $$$) pretty soon. It's better to have single driver and single product to be used as iSCSI initiator, RAM disk emulator and DVD emulator and not to have THREE products (MS iSCSI initiator, SuperSpeed and who-knowns-whow-names DVD emulator), right?
3) Look and feel. StarPort is easier to use compared to MS initiator, we plan to provide more localizations and extend manuals. MS does not have plans to localize MS initiator and have a bit nasty UI (from my point of view).
4) Price is not an issue. You get StarPort for free if you pay money for StarWind.
Is it enough or I should invent some more reasons?
Thanks!
ChrisKinsman wrote:Can someone fill me in on why I might want to purchase StarPort as opposed to the iSCSI initiator that is provided by MS for Windows Server 2003?
Thanks,
Chris