What is our primary use case?
We were looking for the two-node HCA. We found that VMware was also a solution, but it was a bit costlier for us. We couldn't bear the cost, so we were in search of other products similar to VMware. We found the StarWind solution.
Initially, we took a trial license, implemented it, and tested it for one month. Then we found that it suited our requirements, so we installed it in our production environment.
So this is how we approach the storage.
How has it helped my organization?
There are very few OEMs providing two-node clusters with software-defined storage. This is one of the beauties of this tool, even with a single node failure, it's stable and handled well. In a one-node cluster, it provides a full data store.
What is most valuable?
The most valuable feature is that it doesn't require any heartbeat node, a separate source, or anything else. It takes care of everything in just two nodes.
The management console is also handy, integrating all the information. This feature is not present in other solutions, as it's already integrated within vCenter. Unlike using vSAN, there's no need for frequent updates to JSON files or DB updates in VMware. These things are not present in the StarWind solution.
What needs improvement?
The only drawback is that it takes a bit of time during initial synchronization, especially after restarting the environment. This is a potential area of improvement.
There's a synchronization time, but it takes time. Initially, when we start the first environment deployment, it starts synchronizing between the storage. So, it is taking time. One thing is that even when you restart.
Let's assume that the synchronization is completed and the storage is synchronized. Both storages are fully synchronized, and it is in sync mode.
Now, if we want to restart both nodes, there is a case for maintenance purposes. You took both nodes for maintenance, and we rebooted it. Then, it should not synchronize again. It should be a checksum. And if there is a checksum match, there should be no synchronization again. So, one thing that should be taken care of.
Another thing is that I used freeware- the community version, free license, which we deployed using PowerShare. In that case, it was very difficult to bring back another node when one node was faulty. Let's assume that both the nodes are working fine. And we found one node faulty. And we destroyed all the volumes in that and tried to bring it back. So that was a difficult factor. The final solution is that we were not able to bring back the failed node. So, we reconstructed a new data source for that. That is another drawback.
In future releases, I would like to see the integration with VMware or some other things as a plugin model for VMware.
For how long have I used the solution?
I have been using this solution for three months now. I use the latest version.
What do I think about the stability of the solution?
I rate stability a nine out of ten.
What do I think about the scalability of the solution?
I would rate it eight out of ten.
Which solution did I use previously and why did I switch?
We used vSAN. The vSAN I used with three nodes initially, and we wanted to scale down to two nodes. Even when we inquired about the two nodes, the cost was high, and we didn't have that much budget in my project to afford it.
How was the initial setup?
Initially, we struggled. Then, we sought support using the StarWind community forum.
The response was very fast and brilliant. I want to appreciate them. They supported me very well and were very prompt. I didn't find these types of replies anywhere else.
So, these forums replied within the same day or one day. I would receive a request from them and implement it very soon. I didn't face much difficulty in implementing StarWind.
We were able to implement StarWind in about one hour, which is the same amount of time it takes to implement VMware vSAN. Overall, we are happy with the ease of implementation, and we have not encountered any difficulties.
What was our ROI?
We saw an ROI. We have saved both time and money by using it.
What's my experience with pricing, setup cost, and licensing?
I am happy with the price of StarWind.
Which other solutions did I evaluate?
I did not evaluate any other options before choosing StarWind.
StarWind is the best solution because it is the only one that offers a two-node solution.
We looked into VMware and StarWind, and we did not inquire much about other options. We found that the price of StarWind was very good compared to VMware or Nutanix.
What other advice do I have?
I would definitely recommend using the solution.
StarWind should improve the synchronization time of its product. There should be a standard operating procedure (SOP) for synchronization to reduce the time it takes.
The solution should develop plugins for third-party virtualization software, such as VMware, Nutanix, and Hyper-V.
Finally, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises