What is our primary use case?
I purchased a StarWind Hyper-Converged Appliance from StarWind in order to fulfill a multitude of needs for my end client. Chief among them was that the system would be a rather small installation.
Compared to a traditional configuration using three Servers and a SAN, the StarWind HCA allowed me to provide the user with two Server boxes that could handle their redundancy requirements in a fraction of the space and with a significant cost reduction.
The installation called for using a VMware vSphere that would house about a dozen VMs with redundancy for every component involved in the system. The reduced size of this installation also made it possible to install the HCA alongside the existing servers so that they could be removed at the client's leisure when they were comfortable with the new installation.
How has it helped my organization?
StarWind Virtual SAN, and specifically its implementation in their StarWind Hyper-Converged Appliance, gave us a competitive advantage in the bidding process. This is specifically true for smaller installations where the economies of scale of having a centralized SAN and compute-only boxes don't have a chance to kick in.
In addition to the StarWind solution allowing you to save on the hardware by only requiring two boxes containing all components, it allows us to avoid the unfortunately expensive solution provided by VMware for their own virtual SAN solution.
What is most valuable?
The StarWind Virtual SAN provides a clever and unique solution to the Computing Split Brain problem. A split brain occurs when two machines in a redundancy scenario have lost their connection to each other yet have maintained connection to the clients. This causes both devices to think they are running as the master, and their configurations will drift apart from each other, making reintegration all but impossible. Instead of using a third client as a witness, they have solved this problem by creating a secondary heartbeat signal to be carried on an independent hardware NIC, thus solving the problem.
What needs improvement?
The only current drawback that I see for the configuration as it stands is that it can be a little complicated to configure compared to other, more traditional solutions.
If it were up to me, I would focus on streamlining a vSphere appliance for configuring the virtual storage machines.
I would also like them to invest time in reducing the complexity of the startup and shutdown procedure. Currently, it requires you to jump in and out of virtual environments placing storage components on or offline, and all steps must be done in their proper order, or you can create an issue. It seems to me that this could be integrated into an add-on for vSphere that could handle the details of the startup/shutdown procedure more gracefully and with less manual intervention.
For how long have I used the solution?
We've used the solution for about two years.
What do I think about the stability of the solution?
I did not experience any stability issues
What do I think about the scalability of the solution?
This solution has the ability to scale into very large systems. However, it really shines in the small to mid-size range.
How are customer service and support?
Customer service gets back to you promptly and is highly knowledgeable.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
In most instances, I have used a regular vSphere running a SAN and multiple compute hosts. I haven't precisely switched. I'd say that you need to provide the right solution for the end client, and in smaller installs, specifically, the efficiency gains in space and cost of the StarWind Virtual SAN can be hard to beat.
How was the initial setup?
The initial setup for the StarWind Hyper-Converged Architecture I purchased was largely done either by StarWind or with their assistance. If I had to do the whole thing myself, it would have taken me quite some time based on the complexity. They do have good documentation and videos, so it would not have been an insurmountable task.
What about the implementation team?
We mainly did an in-house implementation.
What was our ROI?
I didn't calculate ROI. I can only state that it was about 30% cheaper for the end client than the alternative.
What's my experience with pricing, setup cost, and licensing?
Do your comparison shopping, and if you are working on a small system trying to ensure redundancy, that will almost certainly bring you back to StarWind.
Which other solutions did I evaluate?
For the application, I compared it to a regular vSphere SAN. However, I did not compare it to other Hyper-Converged solutions. At the time, it was pretty clear that they had a long track record and a good reputation which aided in deciding on them as a solution.
What other advice do I have?
Before you deliver this to an end client, make absolutely sure that you provide adequate documentation about how to start up and shut down the system. That part can be a little bit tricky and requires you to do things in the proper order.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.