Highly available HyperV cluster. Our environment includes 2 Hyper-V hosts with onboard storage running about 20 virtual machines. StarWind allowed for a redundant cluster to be configured without any extra storage and easily create an HA cluster. StarWind Virtual San functions as the primary drivers for all of our storage needs in the highly available cluster. It is used almost daily to allow for live migration of machines and failover in the event of maintenance or physical host hardware problems.
Maxta Competitors and Alternatives
Read reviews of Maxta competitors and alternatives
IT Supervisor at Area Agency on Aging Region 9, Inc.
Greatly improved virtual machine reliability and accessibility
Pros and Cons
- "Highly available storage is the most valuable feature. The entire rollout is hyper-converged and requires no extra storage further than the hosts in which Hyper-V is running. Another feature that has been great is the support from StarWind in general. We have their proactive support package on the main cluster that employs Starwind Virtual SAN."
- "Management of VSAN itself could be improved. A Web UI for management would be great rather than an application installation. StarWind is testing a command center virtual appliance that I have installed in my environment."
What is our primary use case?
How has it helped my organization?
StarWind Virtual SAN improved my hyper-v deployment by making it highly available. It was easy to roll out and it is easy to manage. It has greatly improved virtual machine reliability and accessibility. Deployment of StarWind Virtual SAN has helped reduce the stress of not having a cluster that would allow for virtual machine failover if a host has a hardware problem. It is reassuring to know that all virtual machines are in a safer environment versus running on standalone hosts with no shared storage.
What is most valuable?
Highly available storage is the most valuable feature. The entire rollout is hyper-converged and requires no extra storage further than the hosts in which Hyper-V is running. Another feature that has been great is the support from StarWind in general. We have their proactive support package on the main cluster that employs Starwind Virtual SAN. The StarWind support team is right on top of all monitoring activities. If I am maintaining a physical host and it has been down for too long, I will get a notice from StarWind to confirm a problem or inform them that maintenance is being performed. They are top-notch.
What needs improvement?
Management of VSAN itself could be improved. A Web UI for management would be great rather than an application installation. StarWind is testing a command center virtual appliance that I have installed in my environment. It is very much a step in the right direction to make StarWind Virtual SAN management easier and even Hyper-V as a whole. Something Hyper-V has lacked for years is a good Web UI to manage a host or cluster. StarWind has taken upon themselves to help with this as well as manage the Virtual SAN in a single pane of glass.
For how long have I used the solution?
Greater than three years.
What do I think about the stability of the solution?
Very stable. I've had little to no problem since rolling it out.
What do I think about the scalability of the solution?
It should be easy to add a host to a cluster once VSAN is installed.
How are customer service and technical support?
Which solution did I use previously and why did I switch?
No. We used standalone hosts.
How was the initial setup?
Setup is a bit complex but StarWind has great documentation to get setup and a great support team to assist in setup.
What about the implementation team?
Implementation has been done using StarWind support and with an in-house team as we have 2 separate clusters both using StarWind Virtual SAN
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Evaluate your solutions. This is a great solution for those user Hyper-V and ready to hyper-converge.
Which other solutions did I evaluate?
Maxta, Nutanix, VMware, KVM.
Which deployment model are you using for this solution?
Disclosure: I am a real user, and this review is based on my own experience and opinions.