StarWind Virtual SAN Reviews

We are using StarWind as a two-node Hyper-V Cluster in order to have a highly available virtual environment. The two servers are interconnected with 25GB network cards. 

We then have our VMs installed on Hyper-V using the shared storage. Virtual machines will then instantly fail over to the other node in the event of a server hardware failure. StarWind keeps both of the disks mirrored to ensure no data loss. This has worked with no issues over the last year on many clusters that we have set up using StarWind. 

StarWind has been straightforward to configure. As a company, we have been able to install many StarWind clusters with no extra hardware required, meaning less hardware to maintain. The software is also cost-effective vs purchasing dedicated hardware SANS. 

We now have a defined config that is easy to replicate and works well with no downtime or maintenance required. 

StarWind support has been great in helping resolve other issues not caused by their software.

Shared storage between two devices is great. It was done seamlessly. StarWind has been straightforward to configure and installs StarWind organize a time and configures the software using their best practices. As a company, we have been able to install many StarWind clusters with no extra hardware required, meaning less hardware to maintain. The software is also cost-effective vs purchasing dedicated hardware SANS.

StarWind support has been great in helping resolve other issues not caused by their software.

A central management console may be nice to see all nodes.

I've used the solution for more than one year.

This has been very stable over the last 12 months.

We did not previously use a different solution.

Licensing used to be good. However, the pricing may have gone up in recent months. 

We did look at other hardware solutions.

The product is for clients who require high availability of their servers, from file servers and domain controllers, through to line of business applications.

I've done installations of two-node HA clusters running Windows Server Hyper-V. With the HA cluster we then ran virtual machines, both Windows Desktop, Windows Server, CentOS and Ubuntu. We have installed on pysical servers with both DELL PowerEdge and HP Proliant server hardware (Windows clustering requires exact server hardware to be matched - so two-node DELL, and two-node HP).

As an MSP, stability is important for our clients. StarWind's virtual SAN solution has allowed us to have an always-on architecture allowing survivability of hardware failure. We install it for all clients who need high availability of their virtual servers on-premise.

Given the high availability of the server cluster, we were able to reduce separate physical servers onto one hyper-converged cluster - this saved in OPEX and CAPEX costs immediately, along with licensing costs of the Windows Server licenses.

We have multiple sites running StarWindws Virtual SAN, which have been running for years without any issue.

The thing that impressed me the most about the product is the technical support from the vendor. Everyone knows the benefit of high-availability clusters, but setting one up and reading the documentation is an enormous task in itself.

With StarWind Virtual SAN and the installation support, we have high-availability clusters running within a couple of hours. This has been repeated over and over on many customer sites, so they have their process perfected in this regard.

The documentation could be clearer in terms of explaining the installation, although I will make two comments on this.

The high availability of virtual SAN is by its very nature not a simple drop-in thing, so the documentation will understandably be complex.

Secondly, the installation process is completely guided and done remotely by StarWind certified installation engineers, who handle all aspects.

Given the above, the only thing I can really say needs improvement is that I am not keen on the pricing per storage tier model, however, understand this is a common model charged.

I've done multiple client installations over five years.

No, there was no other solution that we have tried.

Consider how much space you will need as pricing is per node and data.

No, we found the price point compelling, which led to immediately trying StarWinds versus traditional SAN costs from DELL and HP, etc.

Overall it has been a great product and company to work with for the past five years and many more to come.

StarWind vSAN is used to provide highly available storage for a VMware environment within a large factory complex. The storage solution needed to be hardware independent and capable of being moved to no Dell hardware when or if required. The customer had already decided upon and purchased a specific Dell hardware solution, prior to deciding that they would like the features and benefits of high availability storage and or the benefit of a hyper-converged infrastructure.

The StarWindvSAN solution stretches over two Dell VRX Blade chassis and provides synchronous replication of data for us.

StarWind Virtual SAN is essentially hardware agnostic, allowing us to build out a specific hardware layer based upon the customer's unique requirements, specifically around Dell VRX blade was the most valuable feature of StarWind vSAN. It is a pleasant change to encounter a company who are willing to be flexible over an implementation utilizing their product and varying slightly from their normal design specifications. They also helped us qualify the product against the customer's constantly changing requirements.

The solution allows for highly available stretched vSAN technology, independent of hardware vendors was the primary selling point of this platform. We have had a scenario where one of the server rooms, in this case, the primary where all of the virtual machines run, fail. The virtual machines are key to the management of a production facility that employs hundreds of staff on a rostered basis. In the event that the underlying infrastructure is no longer able to serve data the hourly cost and loss to the company in exceptionally large.

The ability to continue to be back up and running within minutes definitely saved the company hundreds of pounds.

As a company grows the ability to be able to deep dive into the minutiae of system performance becomes very important. Being able to see at a glance which systems are consuming IOPS/shares is very important indeed. 

The gathering of monthly consumption and performance reports for future dissemination to concerned parties is also very important. Unfortunately, StarWinds vSAN doesn't offer this functionality, however, it is something that would be greatly welcomed should they choose to develop it.

I've used the solution for two years.

We have had no issues regarding the stability or availability of StarWind vSAN. As such, my views are it is a good and reliable product.

It would be apparent that the solution will scale quite well. However, our actual capacity requirements for the implementation we performed are very small. As such we are unlikely to require future scalability.

We had one incident for which we required the help of their support. Our questions and queries were answered within an hour of their being raised. Overall, we have been very pleased with the response.

Positive

For this specific scenario, the customer hasn't considered the benefits of using this technology and it had not been a requirement.

The initial configuration was very simple. We utilized StarWind's expertise and recommendations when implementing the solution.

StarWind, the vendor, was involved directly with the implementation. This was accommodated remotely.

We have not measured ROI.

I'd advise users to go with StarWinds's design recommendations and utilize their technical support. It will help you get the best out of the product.

No other options were considered. This as hardware had already been purchased.

Our initial requirement was to have instant failover to another node in the cluster. Starwind Virtual SAN (vSAN) allowed us to meet the organizational requirements. It is installed on two of my Production servers for use in a Hyper-V cluster for a few years. 

Our initial requirement was to have instant failover to another node in the cluster. Starwind Virtual SAN (vSAN) allowed us to meet the organizational requirements. It is installed on two of my Production servers for use in a Hyper-V cluster for a few years. 

Starwind support was excellent in setting up all the connections between the servers and doing the configuration. Performance has been excellent with no issues. 

I don't even notice it's there. Since installing and initial configuration, I have not needed to engage with support.

The instant failover, with vSAN copying data to the second node, allowed for the continuous availability of our applications. By far, the best features are implementation and support. 

From our research into other options, an equivalent installation would have been quite a bit more than the StarWind solution. We did have to invest in another server and improve the connections between the nodes. This implementation now far exceeds our previous setup, which, in hindsight, was convoluted. 

So far, for our use case, I haven't noticed issues with the product. 

The few times I've ever engaged with technical support were during the initial phase of the implementation. However, I would absolutely like to see a lot more on the monitoring side. The information currently does not give any performance of the VSAN. 

I would also like to see the activities occurring on the nodes, bandwidth, replication and synchronization. Diagnostics information or alerts on the state of systems could also be implemented to give more visibility. 

I've used the solution for over two years.

We use the solution for HA storage for HVs.

We are an SMB that can't be bothered paying tens of thousands of dollars just to get a proper HA storage for a two node failover cluster. Therefore StarWind's vSAN was financially attractive from the start.

The reviews you can find all over the web incentivised us to research this solution deeper (e.g. just check all the great posts vom Kooler on Stackoverflow), leading to us actually implementing it.

We were coming from an S2D implementation which already gave us a ridiculous amount of headaches (bugs, performance stalls, "we know what's best for you" automatisms) in addition to being slow and annoying to administrate/debug while also having the most annoying documentation ever to be created by mankind. These solutions rush out some code and ship it and never fix anything (but break it every few weeks with patches).

The initial tests were easily implementable (without begging some sales folks for a POC, due to a free version being available) as well as proper documentation that you actually like to read due to it having been typed by a tech (and that also isn't behind a pay/registration wall).

As close to perfect as the documentation is, do read the blog posts to the two-node HA setup as well. Some minute details were only found in those.
There are no showstoppers, and not many things in general, just a few hints here and there.

The install itself is easy as pie. The config file is properly documented (you can do most things via GUI, just some things are set in the main config file).

Do help yourself to the iSCSI Powershell commands (Windows defaults from MS) when implementing. It is way more attractive than clicking via GUI.
(New-IscsiTargetPortal, Connect-IscsiTarget etc.)

Some things must be done via GUI though, since iSCSI has been implemented way back and "making scripting available" wasn't that widespread for developers back then. This being a Microsoft topic, not StarWind though. They would have had to make their very own iSCSI implementation otherwise.

For testing, you should use a proper tool like https://docs.microsoft.com/en-...
since "Windows copy from within the VM running on the test setup" can be flakey.
Not as in "the results aren't valid real world performance if you check with the Windows copy within a VM" but rather "non-scientific" since you can't extract much data from that process aside from size/time.

There is a visual bug with a specific part of iSCSI. It's Microsoft's fault, and, as usual, has never been fixed in over 15 years. Just don't panic if you experience it.
https://www.dell.com/support/k...
https://social.technet.microso...

Price-wise this is very attractive. The support is great (little that we needed due to the good docs) and I would expect you to reach a very good performance just like we did.

The next-best solution from my research back then - that you would actually want to use, so no S2D or anything - would have started at 7X or 8X the price. Since StarWind's solution has served us very well over the last two years already, I would recommend it.

To respond to the "how it has improved our organization," in a nutshell: it has provided very stable and performant storage-level HA which allows for live failover of VMs (as long as the compute doesn't die as well).

We like the ability to be installed and used on the same host, so we get the max performance possible.

It is easy to set up and maintain, resulting in a happy admin and low TCO/good ROI.

It offers good performance and stability and also makes for a happy admin.

It provides HA for our failover cluster storage where anything can go wrong up until compute, the thing still chugs along like nothing ever happened.

The upgrades are also very easy to implement. It's basically "click click click" once everything has been shut down and you're back up really quickly.

Feature-wise we are only waiting for the release of a "planned disaster" feature that would allow us to patch a hypervisor node without having to take the full storage offline.

ATM (20220609) is still necessary, since taking a node offline without properly activating the maintenance mode on the vSAN would trigger a full sync of the vSAN nodes.

This is fine and a good thing since it ensures data integrity. However, there is something in the making that would ensure integrity without a full sync after a node goes down, which, as stated above, one could "abuse" to patch (and boot = take down) the hypervisors during business hours 😁

Other than that, the thing is rock stable and chugging along without issues.
We are an SMB so we "only" have around 50 VMs on our FO cluster, which is a medium load for SSDs.

If you plan to go more to the "max" side of performance use, do proper testing!

I've used the solution for two years.

It's rock-stable.

So far, we only had visual issues in a specific place due to Microsoft being a PITA and never fixing any bugs they bring in (this one being over 15 years old).

It scales very easily.

Depending on your setup, their actual SAN might be a better fit for you, however, that's for your very specific case to decide.

We really only had contacted the support for the final checkup after setting it up ourselves, so that they could verify everything is running as it is supposed to.

That was great, so our experience has been great overall.

Positive

We previously used Microsoft S2D. It had bad documentation, offered bad performance, and had bad GUI and bad CLI.

The setup is very easy, and they offer very nice documentation and blog posts.

We did the implementation all in-house, self-taught by their great docs.

Since our HVs already run with Windows DC we had S2D included in the cost.

However, the operational costs were high. I'd easily say the invested time over a year with S2D would be $20-30K while StarWind's vSAN now took like $500-750 (yes, less than $1K!) over two years. 😎

Even if you add the license cost (which is cheap even with our 3-year premium support package) it is a no-brainer.

There is the "invisible" cost of you reading the docs, however, that comes with every solution. At least with StarWind, you have tech-to-tech documentation that you can actually use.

The pricing is very fair!

We looked into VMware and others. They usually had a way higher cost or worse performance or worse GUI/documentation, or all of those things together.

I'd advise others to use the free license to test it. The doc is also public. This is the way.

We have a two-node hyper-converged system set up. Our main electronic medical record system runs on top of this system. We can fail over to one host, which lets the virtual machines run on the other. We can perform maintenance and move the virtual machines back. As a medical facility, it's important for our products to be up and available. This system allows us to do that. We have plans to purchase an additional host this fall, which I hope to be able to add to the VSAN. I believe there's an additional purchase to do so, however, I'll look into that when we get closer. 

StarWind allows us to move virtual machines from one physical host to another, which greatly reduces the downtime required for maintenance. I've been with the organization for about four months now and came in not knowing anything about StarWind. To become better acquainted, I asked if StarWind would give us a 'demo' of our current system. They showed us how our configuration was set up and helped us make a couple of suggested changes. We have since restarted one of the hosts without any trouble on the StarWind side at all. 

It's very stable and is easy to use. The system failovers properly on its own without too much worry. Support has been amazing. I wasn't at my position last year, but we had a hard disk in a host machine fail last year. Through a series of unfortunate events, a VM failed. StarWind support helped the technician pull the system back up and even assisted with restoring the VM, something he didn't have to do. I've since read other accounts of service like this. The community and KB articles are also very valuable. In any event, I know I can get help with this system.

I'm actually really satisfied with Starwind. Their product and support have been top-notch. They even have a version that is free, though it is a command-line only. 

As for additional features, perhaps some integration in with systems like IT Glue.  A way to push the configuration into IT Glue in the event of an outage or just for documentation purposes would be nice.  

Overall, however, the product does what it is supposed to do. Adding features for the sake of adding something may not be terribly appropriate in this case. The system just plain works.

My organization has been using StarWind for several years now. I'm new to my company and have been learning how the product works.

We've had no stability issues with the product.

Currently, we have this running on two nodes, however, I believe it can be scaled up significantly. For our limited purposes, I have no concern about scalability.

Amazing! They've gone above and beyond with helping us when we had hardware issues last year and again this year when I asked for a demo of how things are set up.

Positive

We did not use a different solution.

While I wasn't around for the initial setup, I performed a handful of test installations to become more familiar. StarWind has a wonderful KB article that covers the process, step-by-step.

It's my understanding that it was all done in-house. The configurations are exactly as the KB article mentioned above has it spelled out.

We can keep our electronic medical record system running while we do maintenance. We've used Starwind for several years, so the investment has covered itself.

Pricing is simple. You can buy a support package that gives you access to updates to the software or you can buy premium support, which expands the time in which you can get help from the company.

I was not around when the decision to use StarWind came about. I don't know if there are other 3rd party vendors like StarWind. 

We were looking for physical tape backups to protect against DR situations but were concerned about the fact that it would require the manual intervention of changing the tapes and sending them offsite as we could easily forget. 

Luckily, I came across  Starwind VTL which is the same as having a physical tape library without the hassle of changing tapes. 

The whole process is automated and we have the option of choosing between multiple cloud storage providers such as Amazon, Wasabi, Azure, etc. It's been six months and it has been working well without any issue with the jobs completed within 24 hours which meets our RTO. 

In regards to the cost, we ended up saving a few thousand dollars as well due to the high cost of the physical tape library.

With Starwind VTL, it eliminates the need to manually change and remove tapes and schedule them for offline pickup which users would not have the time to do.  It is also cost-effective as having a physical tape library would cost thousands of dollars. 

In addition, the virtual tapes can be uploaded to the object storage of your choice with object locking/governance which gives you an extra layer of protection.  

Furthermore, having virtual tapes locally and on the cloud provides an additional layer of protection in addition to our normal backups that are performed. 

The cloud replication feature is most valuable as it copies the local virtual tapes from our on-prem storage to object storage where we can set object locking and governance.  This is a great feature in case something happens to our on-prem storage. 

Also, since it's virtual tapes, there is no manual intervention of changing tapes and scheduling them to take them offsite which is another additional cost. The support team is also good as they were able to resolve the majority of issues during the initial implementation.

There needs to be more visibility on how long the cloud replication will take as there is no current ETA.  

Also, there is no date/time column so you don't know which is the latest tape that has been uploaded to object storage.  

You also cannot search by tape name so you have to scroll through the tape list if you ever need to cross-reference.  

Another shortcoming is that the tapes do not remove from the list once they've been deleted via the retention policy so you would have to manually remove them.  

I've requested all of these in a feature request with their R&D so hopefully, they will be included in future releases.

We've been using this solution for over two years now.

We did not have a previous solution. This was an add-on solution to our existing backup solution.

The pricing is very reasonable compared to a physical tape library.  

We evaluated the physical tape library, however, it was too costly.

The initial setup will take time, however, their implementation team will assist all the way through.

The primary use case we had was covering with StarWind vSAN was to provide customers with a redundant solution that was able to guarantee flexibility. In terms of physical storage, we can aggregate in order to provide a redundant, replicated solution. At the same time, we were looking to keep the total cost of ownership as low as possible as the customer may have multiple venues to cover with the same schema of the system. 

With StarWind vSAN we were able to set a simple 2-node cluster leveraging the internal disks to create a replicated vSAN - eliminating any SPOF at a reasonable price.

StarWind, compared to other competitors in the market and in the same range of price, allows us to design system plans with the resilience of enterprise-grade storage, however, we are able to use smaller storage even at the consumer level. This makes us more competitive as the total price of the offered solution was comparable to a usual non-HA system yet with all the resilience features that StarWind is bringing with its product. This combination of low price with enterprise-grade HA features is key in the market.

There are tons of valuable features that StarWind vSAN brings to the table. It is very difficult to choose one to be raised as a role model.

The unique capability to create a vSAN on a 2-node cluster while all the other competitors will require users to have at least an external witness to set the Virtual SAN.

The service team is very collaborative and skilled and followed us from the implementation to the go-live of the system constantly.

The license price is one of the cheapest in the market.

The price is the key aspect (yet not at the expense of reliability and stability). It is not so easy to find an aspect where StarWind can improve their offering or any additional feature they can include for the price they ask. 

I know that StarWind can scale out easily, however, I wasn't in the position to test that. I would like an automated installation/configuration despite the fact that their service is very collaborative, a customer should be able to deploy the solution by themselves. 

I've used the solution for more than one year.

Unfortunately, I wasn't able to test the scalability aspect.

As it was driven by StarWind reps, it was running very smoothly.

There's nothing to finger point on the StarWind team. They were great.

We also evaluated StorMagic, VMware vSAN, and Datacore.

We are an SMB IT consulting company with an infrastructure department. 

Before 2019, we had been deploying HP StoreVirtual VSA in order to deliver a typical 2-node hyper-converged cluster. Since the publishing of EOL/EOS for HP StoreVirtual we had been looking for a suitable replacement. 

We looked at and deployed various solutions - from StorMagic, Open-E, NetApp, and EMC. StarWind was the easiest to deploy. It was very inexpensive, offered the best support, and was hardware agnostic. After several deployments, this has been the best 2-node hyper-converged solution accepted by all engineers on my team.

StarWind Virtual SAN has given us the ability to bring a stable and functional 3rd party 2-node hyper-converged solution to our SMB clients. 

The typical roadblock with SMBs is the cost. It is very difficult to convince an SMB of the value of redundancy, highly-available hardware configurations, up-time, and quality vendor support until an emergency happens and solutions are needed ASAP. 

With StarWind, we are able to present best practices to SMBs and since the price point is attractive, we can more efficiently convince SMB clients to make the investment in best practices before a disaster happens.

The top-notch support before, during, and after deployments are better than any other vendor I have come across. There is very little wait and very little pain to get an engineer who is very knowledgeable about this product to assist us.

The fact that it is hardware agnostic gives us the capability to customize the solution according to the client's needs and budget.

We are in the middle of converting our own infrastructure to StarWind Virtual SAN since we are so satisfied with the ease and function of the environments where this product is deployed.

The only way I can see this product needing improvement is the consultation level of the StarWind sales and engineers. For example, the method of management of the StarWind environments that have been deployed has been a downloaded management console program. This downloaded program which needs to be installed on the network of the environment was the suggestion of the deployment engineers. 

I would like to see more consultation on a web UI management console.

Our first deployment was in 2019.

No deployments have ended badly. All are still running without issues. It is very stable.

The solution is hardware agnostic. Storage can be added if licensing is increased. It offers above-average scalability. 

Customer service is the best part of this product. The customer service and support I have received are unmatched by any other vendor.

Positive

We used HP StoreVirtual. The switch was needed as it came to its end-of-life and end-of-support.

The initial setup is very straightforward. Anything complex is done by the StarWind personnel.

Our implementation was a hybrid of vendor-team and in-house. The vendor team has a very high level of expertise.

The ROI is for our clients. There is less downtime, less troubleshooting, fewer issues, and fast speeds. 

The setup is simple and the cost is attractive.

We also evaluated Open-E, StorMagic, NetAPP, and EMC.

I'd advise users to initiate lots of communication with their support staff. Their responses are quick and sufficient.

We use the solution to create a highly available server cluster. 

I currently have two physical servers running 25 virtual machines in a highly available cluster. StarWind Virtual SAN enables this without any extra hardware and any kind of hardware vendor locking. 

We use the vSAN product to run a production cluster but also a secondary cluster that houses low-level and testing servers. StarWind vSAN is used to cluster everything together into a solid hyper-converged structure that requires less hardware, less energy, and far less maintenance.

I have been able to do more with less hardware. StarWind vSAN allows us to create a hyper-converged server cluster on a friendly budget without being locked into a specific hardware vendor. 

The product, server, and support are top tier. Their proactive support is on top of every little anomaly in the vSAN. The product is fairly simple to get running and operates with little overhead. 

It makes setting up a high available environment easy and very manageable. Everyone from sales to support are very engaged and proud of the product.

The most valuable aspects are the support and the high availability.

They offer top-tier support. The support staff is knowledgeable and very willing to help. The proactive support option is unlike any support I've ever dealt with. If anything gets out of sorts, the team is on top of it with an email.

Achieving a highly available environment can be hard to execute and lead to a hardware vendor lockin. StarWind is hardware agnostic and supports as few as two hosts to create a fully functional, hyper-converged, highly available server cluster at a fraction of the cost of other vendors.

A good area of improvement would be at the level at which StarWind vSAN is managed. Currently, the StarWind management console is a bit clunky to navigate and isn't the most user intuitive interface. It gets the job done, however, following guides and documentation is highly advised to make sure things are being set up correctly. 

Another area of improvement would be the ability to manage your entire setup using StarWind software. Hyper-V, for example, still needs to be managed using a manager and failover cluster. Combining these into the StarWind product would be a game changer.

I've used the solution for five years.

The solution is very stable. It's been running for five years with nearly no problems in the software itself.

You can start with just two nodes and scale from there. It's very helpful.

The technical support is A+.

Positive

We did not use a different solution previously.

The initial setup is straightforward. The support helps with the initial setup. I had to rebuild a cluster once and support also assisted with that process.

We handled the setup in-house with the manufacturer.

The product offers a very straightforward cost model versus its competitors.

We did also evaluate VMware, Nutanix, and Scale.