What is our primary use case?
We used Starwind to provide HA ISCSI storage to a Hyper-V Cluster for VM Storage. This was mounted through MPIO on Windows for both nodes, using data locality for high levels of speed and performance.
The devices are connected via fiber over a 10-mile line, over an isolated subnet. This has been great, as we've been able to shut down an entire site and have the machines not notice any difference. This was done over our existing network, using an isolated VLAN to have traffic be in its own area with no other issues.
How has it helped my organization?
Starwind made it easy to deploy fully redundant, highly available storage at a low cost. We were unable to find a solid replacement for our aging HP Lefthand solution, and Starwind stepped into that fantastically.
Prior to this, based on a design issue, traffic for storage replication was served on the same network as ISCSI traffic. This had the expected issues you'd think, leading to bad performance. Starwind doesn't allow this by default, and as such forced our architect to realize the mistake and worked to get it set up better, with Starwind support.
What is most valuable?
The support has been top-notch. The engineers you get are knowledgeable and are able to solve issues right out the gate, which is huge for us. We don't get finger-pointing between vendors with them either, as they own issues and take care of them from the beginning. The installation and setup were done with a dedicated engineer, who went through the system step by step and made sure our techs understood the process while getting a great setup out the gate. This was all handled via Zoom, which was a nice thing to not worry about it.
What needs improvement?
It would be nice to see a new UI for the windows client, as it is not the easiest to find settings. However, we normally don't have to.
I do see a lot of info about them now offering a VSAN-like software that is a Linux VM base for VMware. I'd like to see this same option available for Hyper-V, or at least make it more apparent the differences between the two.
I would like to see more US-based resellers. Working directly with the company was fine, but we prefer to have local resellers available as needed.
For how long have I used the solution?
I've used the solution for two years.
What do I think about the stability of the solution?
It is as stable as the Windows OS it runs on. Take that as you will.
What do I think about the scalability of the solution?
It appears to scale horizontally well, as you're able to keep data locality present and it will allow you to pick which data is replicated or not.
How are customer service and support?
Support is easy to get a hold of, and usually first-call resolution.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used HP Lefthand/StorVirtual, which was end-of-life.
How was the initial setup?
IT was straightforward, as it was vendor-led and handheld through. They helped us every step of the way.
What about the implementation team?
The implementation was vendor-led, and they were highly available.
What was our ROI?
The ROI we witnessed was within 7 months, due to hosting on our system.
What's my experience with pricing, setup cost, and licensing?
The cost isn't too good to be true. If you're able to use commodity hardware, it's worth a look.
Which other solutions did I evaluate?
What other advice do I have?
Give it a shot. They may not be the biggest, however, they're able to play in the field.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.