StarWind Virtual SAN Reviews

We have two servers in an HA configuration. The two servers having an identical configuration. On each server we have: two disks in RAID 1 (for the operating system), two arrays of four disks in RAID 5 (for virtual servers that require high data transfer speed), one array of six SAS disks in RAID 6 (for virtual servers containing a lot of data), and two arrays of six SAS disks in RAID 10 (for medium servers in terms of data volume and speed required). On the network side, SAN servers are connected to HOSTs via a 10 GB ethernet connection and between them for HB and SYNC via 1GB connections.

Until the installation of StarWind, we only use physical servers. After installing, I migrated all physical servers as virtual servers and added other new servers. We currently have approximately 30 virtual servers on only three hosts and the two SAN servers. Thus, we get significant savings from the necessary hardware. In addition, we have much more flexibility in allocating available resources. 

Having a configuration of two servers in HA, we can perform maintenance and upgrade operations without having to interrupt the operation of production servers.

From my point of view, the main advantages of this solution are the drastic reduction of the number of physical servers required and the reduction of acquisition costs for servers. 

In addition, there is less electricity consumption for servers and for their cooling and the possibility of dynamic and fast allocation of storage resources where needed. This simplifies the backup and restore process. The product has the ability to take snapshots on production servers before any major upgrade so that if problems occur you can quickly return to the previous configuration.

It would help if the manufacturer provided clearer and more detailed documentation, with explanations of how the application can be installed in various HA configurations. They should include advantages and disadvantages for each proposed configuration. Currently, you can only find information on this on the manufacturer's website, but it does not contain very detailed information regarding each proposed configuration.

It might help to add the functionality to automatically send an email to a predefined address when errors occur in the application.

We have been using StarWind Virtual SAN for more than 10 years and, in that time, without encountering major operating problems.

It is extremely stable. Currently, it is not necessary to intervene or restart the SA servers for years at a time.

It is easy to expand the storage space. The only limitation is the space that the license allows you to use in the HA configuration.

The support provided is very prompt.

Previously, I only used physical servers.

Initially, the implementation of this solution seems complex, however, once you understand how the application is designed, it becomes relatively simple.

Before deciding on the solution offered by StarWind, we also analyzed HPE LeftHand SAN Solutions, however, this was significantly more expensive.

We have a failover Hyper-V cluster and a stand-alone Veeam server. We back up our VMs via Veeam. We wanted to get our backups 3-2-1 compliant with a backup to disk backup, a second backup to another medium that was a virtual tape in our case, and backups to the cloud. 

We had a second physical server with tons of storage, so we installed StarWind. We were able to create a VTL and have tons of virtual tapes. We utilized iSCSI and were able to get Veeam to use this VTL as a destination for tape backups

In addition to Veeam being able to back up to tape now, we were also able to get the StarWind software to connect with our preferred storage vendor, Wasabi. Now, we back up to disk, back up to tape, and then ship those tapes offsite automatically to Wasabi.

The StarWind software was easy and quick to implement/setup and now our backup process is fully automated. 

Our backups are 3-2-1 compliant, which satisfies several audits and cybersecurity/insurance questionnaires. In addition, the process is fully automated.

We now have multiple copies of our backups and in the event of a complete disaster we also now have a DR strategy in place. 

Prior to this solution, we had a single point of failure when it came to backups. Now we, essentially have three targets, two of which are completely air gapped for security.

Lastly, the virtual tapes I've been told are impervious to ransomware. 

A great feature is that I basically set it and forget it, as everything is automatic. This is one less major thing to worry about.

Before, we had a lot of stock and pressure on our singular backup server. It carried a lot of weight. Now with the VTL software in place, we have three backup targets. The primary backup server is still critical but if that server were to go down, we would still have backup data intact. If our data center went down, we would still have backup data intact thanks to the offsite options. 

We can rest easier knowing our data is fully protected. The fact we have a DR strategy is priceless.

The console is something that I feel could be improved. There is nothing technically wrong with it, but it can be jazzed up and/or made to be a little more intuitive. Perhaps introduce a few right-click options, as that's my general go-to approach as opposed to searching for specific menu items.

I also feel that when dealing with a magnitude of tapes perhaps better formatting or color-coding will help locate or identify tapes easier than scrolling through the list. Also if the lists' real estate on the screen could be increased that would be helpful as well. 

Other than that, I have no complaints or issues with the software.

We have been using StarWind Virtual SAN for six months.

I haven't had any issues with the app becoming unusable. It's very stable and I have yet to experience a problem with it.

The software can be upgraded with each release, so it's very scalable. 

The technical support is amazing. Five stars. They are quick to respond and are able to handle issues very quickly and provide great feedback and explanation. 

We did not use another similar solution prior to this.

The initial setup was very straightforward and simple. I had the support team guide me along the way but the setup process was intuitive and there was nothing confusing about it. 

I implemented it through their support team. After we purchased the software, they helped set us up. They were very knowledgeable and fast. We had tape backups working in minutes. 

I don't have exact figures in terms of ROI but I can say the product was well worth the cost.

The cost was ultimately low to implement, which allowed us to be 3-2-1 complaint.

We did not evaluate other options.

After we purchased the software, we were able to contact support right away. I would suggest you take advantage of this, as they are quick to respond and got my software up and running literally within minutes.

We decided to migrate our infrastructure from Terago Cloud to a Tier III datacenter. It was primordial for our company to have redundancy at every level. It was not an easy sell to make that move and I needed to prove to management that we could have a very secure environment.

I needed to have a software that could create a fail over between my hosts that would work well with VMWare 7.0. After researching several company we made the decision to go with Starwind.

Of course, once we had everything in place, we made a test failover. It failed. I went back to Starwind and this was fix within one phone call. Missing configuration. The following test was successful.

The fact that I can now count on a true failover solution is what is most appealing. Also, it was easy to test the solution to make sure it worked. How many companies out there install software without testing it?

It was easy to get organized and test to be sure it was performing to its full capacity. During the failover, only a few seconds of downtime were seen, proving to me that I can count on StarWind during business hours and know that they have our back at the Host level. Who can afford downtime?

Without a doubt, it would be support. Either we were sending an email to our Rep or simply calling in to open a case, a returned call could be expected within the hour. Always courteous and helpful. Those guys know there products and surrounding, like VMWare. They also keep on following up until you say that all is well.

We were having issues with our vCenter when we first deployed, and we had to call back technical support a few times. Each time was a fast and professional service that was offered to us.

This is a tough question. One that I wouldn't have put in here for the simple fact that I decided to write a positive experience with Starwind.

Now, if I want to be picky, I could simply say that the price is not cheap. I started with the basic package, for 4 TB. Than I had to purchase to go up to 8 TB. It does look now that I will have to pay the remaining fee to purchase unlimited data. Should I have done so first, maybe but things change very rapidly and what wasn't needed not too long ago is now. SO overhaul, price. I would also need to pay extra to be able to have support during the weekend, otherwise, you have support only from Monday to Friday. Can be inconvenient if your business work 24 hrs shift Sunday to Friday.

We have been using StarWind Virtual SAN since the rebuild of our infrastructure in August 2020.

So far so good and since it is running directly on VMware, I do not see any issues in the future either.

With the right licensing, I do not see any issue with scalability.

The installation was straightforward but it still was a new product for us and we didn't know how it was going to integrate with VMware 7.0. At this time, I am seeing a few issues with 7.0, so I wasn't sure if we would have any problems during installation. Nevertheless, StarWind support is what is making me write this review today. Compared to any other company we may have called, no other is as fast and as good to get the problem resolved.

This was our first installation.

The installation was fairly straightforward. Although the first test didn't work for us, only a phone call was required to make this work. We have successfully tested the solution and can see first hand that it work great!

We did in-house with the help of Starwind tech. If you want to make sure it work properly, this is the way to go and their support is fantastic.

N/A

Make sure to look for the next package that they offer for the licensing part. Adding Drives will happen faster than you hope it will.

StarWind came highly recommended and rightly so.

We have Microsoft Hyper-V.  StarWind is configured as a two-node cluster with a Windows environment. It is crucial for the Virtual Machines that give us the resiliency of Exchange, 4TB File Servers, Networking Services, Quickbooks Server, Terminal Servers, Virtualized Spam Protection, Active Directory Services, and a few others.

We needed something that allows for better resiliency than the old way of doing things.  We have seen other choices out there but this seemed to be the best one, given our budget and the hardware we wanted to use.

This StarWind solution has enabled us to be more resilient, once it was set up and tested.

Failover happens very smoothly. Recovery and maintenance are now less stressful and most importantly, it allows our users to keep working.

Before StarWind, we were dealing with an archaic way of synchronizing Virtual machines and data between non-clustered physical hosts and it was very frustrating. Now, things are less hands-on and easier to manage and navigate the virtual environment, including maintenance while other users keep working.

We found that robust communications between clusters and synchronization were key and most valuable to us due to the amount of data we were synchronizing.

The expertise from their technicians is very helpful even in the middle of the night, with the right support plan of course. The technical documentation, the follow-up and the details noted on a per-call basis was amazing. We really appreciate that kind of commitment to our success and stability that the StarWind software brings to our business.

Built-in Notification would really help and as I understand, their new release has this now.  

A mobile app to sync up for overview and status would really be helpful.

Also, it would be helpful if the software had a few more guides and links/videos on how-to's.

An "Update available" notification within the software would also be helpful and a guided wizard to do the upgrade properly would also be nice and efficient.

A better visual of the SAN storage/actual storage and how it is used would be good, especially when it comes to where the files are located on the disk. 

We have been using StarWind Virtual SAN for the last two years.

Stability seems great and we have not had any problems with the software.

Seems very scalable, although we chose to have a two-node cluster.

This area has been the best for us, especially being new to this technology. The support team was amazing with follow-up and they are super patient.

I have not used another solution for the same purpose. This was what I picked based on my research.

Initially, I didn't quite understand the framework and what exact hardware was needed so I had to do some learning. However, once all was in place it went pretty smoothly.

We did our deployment in-house, with help from StarWind.

Return on investment for us, I would say maybe breaking even. As I said, I wish the costs were better balanced.

The cost seems a bit steep, and I wish it was less expensive.

I have looked at Nutanix and VMware.

Mainly that the costs would be less expensive.

We use StarWind for storage on our Hyper-V cluster. We started with their free offering in a test environment and found the performance and stability so attractive that we built a three node cluster using Dell 720s and ten gigabit copper ethernet. It has now been running continuously for four years with essentially zero downtime. As it approaches end-of-life we will be migrating to their managed appliances.

We were originally in a legacy environment of stand-alone servers. StarWind has allowed us to virtualize our environment without the huge expense of a dedicated SAN (the typical choice in the past), putting cluster technology and its benefits within our reach. Server downtime was a constant threat to our operation before StarWind, but has never been a problem since.

Without question, the support. StarWind has been a valuable technology partner for us from the beginning. On the rare occasion when we have had a problem, or have simply needed to do an upgrade, they have provided first-rate support. Anyone who has dealt with common off-shore support understands the frustration in dealing with incompetent and difficult to communicate with support staff. This is not so with StarWind, as their support staff is comprised of true experts who can also communicate clearly. For highly technical products this is essential.  The best part about their tech support though, is that you probably won't need it much!

On the technical side, the performance has been excellent.  I have never found a reason to regret not going with a traditional SAN. The configuration is so much simpler, with fewer points of failure to worry about. Integration with Microsoft clustering has been perfect, allowing us to leverage our investment in MS server licensing to the fullest. Updates to server hardware are now painless and done during working hours with zero stress. We had a RAID failure a few months back, and nobody in the building even noticed and there was no after hours time used for repair. It's the best!

Very few aspects of this solution need improvement. Sometimes documentation on their site can be out of date, and it is always good to check with support to make sure that whatever you are looking at is current. The good news here is that this is very easy to accomplish. If we stay with the Virtual SAN instead of the managed appliances it would be great to have more automated tooling around managing the iSCSI connections in Windows, which can be a bit confusing at first.

Zero. It runs like a rock.

The current non-managed solution is limited to 3 nodes.

Their customer service at every level, both in terms of our account and technical support is very good. Everything has always been timely and first-rate. I have learned many things about not just StarWind but also Microsoft clustering, iSCSI, and even Hyper-V from Starwind support staff. They are true geek pros!

Before StarWind we were still in a non-virtualized environment of standalone servers with disparate hardware.

These are complex products to set up by nature. StarWind's excellent support makes it easy, but we were able to get our test setup running in just a few hours by reading documents and their forum.

We implemented with our in-house team and StarWind support only. Their expertise not just with their own product but with Microsoft clustering and Hyper-V was amazing. We didn't need any other support to get the job done.

It has paid for itself many times over in reduced downtime and maintenance costs.

Make sure that you understand what all of the pieces do and don't make the assumption that you can drop support once setup is complete.

Yes, we looked at Nutanix and several traditional dedicated SANs.

Make sure that you understand your performance requirements clearly. Learn how to measure your performance needs in your existing environment BEFORE you shop, so that you can be sure that you are looking at the right solution. In all of the planning that goes into making the correct decision on these types of products, understanding performance (and not just making assumptions) is the most neglected part. There is no quicker way to over or under build your solution than to not have real performance numbers for planning.

In our company, we started searching for a cost-effective SDS solution to include in our portfolio since there aren't many reliable and affordable alternatives around. 

For testing, we've set up a small VMware environment with a couple of VMs and connected to StarWind VSAN through Fibre Channel. This is a common environment for most of our customers, who tend to be SMBs, and their environments go from one to six hosts and one block/file storage, on average. 

However, the most frequent pain point is managing and delivering storage for different applications while maintaining reliability and performance. That’s where StarWind comes into play.

We have come to the conclusion that it fits nicely in small/medium environments that, despite their size, still need a swift and reliable storage delivery while being affordable. 

In smaller markets, like the one we operate in, there’s not much money hanging around to spend on software, especially when SMBs have budget constraints and must choose between keeping IT staff or improving the infrastructure. That said, spending $100k+ on VMware vSAN is madness. 

StarWind VSAN offers an interesting alternative that is both enterprise-level and cost-effective without compromising companies' budgets. Having a free version is also a nice, welcoming sign of commitment.

Being hardware agnostic is a must and definitely scored points for us. Despite our portfolio being a little selective, it was nice to see that our hardware options were also supported and there would be no surprises in the future.

The simple (a little dated, yet easy-to-use) GUI was another good thing. We’re in 2024, and most SMBs can’t afford IT-specialized teams, so they rely on service providers like ourselves to keep things running. 

VMware/Hyper-V compatibility has got us all covered since our customer base all runs on one of those two players. However, after three months of testing, we still haven't tested replication features. We'll do it soon.

The GUI deserves a little love. It is simple and works fine. However, the overall design is a little bit dated. 

Updating the documentation would be welcome, too, since there are docs that point to Windows Server 2016 as the latest version, and the vSphere guide comprises 6.5, while we’re currently on 8. 

Being ZFS-based, it would benefit so much to have deduplication and encryption. Immutability would also be a nice addition as it is a hot topic on data protection, and the solutions that offer it are either too convoluted or too expensive.

I've used the solution for three months.

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.

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.

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.

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.

We've used the solution for about two years.

I did not experience any stability issues

This solution has the ability to scale into very large systems. However, it really shines in the small to mid-size range.

Customer service gets back to you promptly and is highly knowledgeable.

Positive

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.

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.

We mainly did an in-house implementation.

I didn't calculate ROI. I can only state that it was about 30% cheaper for the end client than the alternative.

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.

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.

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.