StarWind Virtual SAN Reviews

Our company's needs are simple, and I like redundancy, so I was looking for the least expensive way to achieve as close to full hardware redundancy as possible without breaking the bank. 

I learned about vSAN technology, and it made sense to me to just get two hosts with identical hardware, and configure their storage as shared, providing full hardware redundancy (on top of the already partially redundant aspects of the hosts themselves), then just get a decent SAN for off-site DR backup storage (we settled on Synology's Flashstation for that), and I'm really glad we did.

StarWind's solution provided me the peace of mind knowing I had full hardware redundancy with my new servers and local storage, and it was less expensive than the VMware native license/solution would have been. 

It has been rock solid from day one. I've engaged with their expert support multiple times for maintenance sessions, to upgrade their software, and once to migrate from their Windows Server-based appliance to their Linux version once it was ready. We have only ever had one issue during an upgrade that was quickly resolved by their engineer.

By far, the best features are the cost, implementation, and support. The VMWare equivalent license upgrade would have been quite a bit more than the StarWind solution, and the only additional hardware requirements were the dual 25GB fiber NICs needed for the storage Sync functionality. 

They also worked with our preferred reseller (PCM at the time) and had our two brand new Dell hosts shipped to them first for pre-configuration, which they then turned around and shipped to us pre-configured and ready to go.

Implementation, maintenance, and support were and have been virtually painless, however, I would definitely like to see quite a bit more on the monitoring side of things. 

I would really like to be able to see a lot more of what is going on under the hood metrics-wise. It would be great to be able to see at least a little bit more. Specifically, things like performance, bandwidth utilization of the synchronization connection, and how it impacts the overall performance of the hosts.

I've used the solution for three years.

It has been extremely stable for the three years we've been running it. There hasn't been one operational hiccup and only one issue which happened during a support session performing an upgrade, which was quickly resolved by the engineer.

Our needs are simple. Therefore, we only have ever used or needed two hosts. That said, it is nice to know that it can scale to clusters if we ever need to go that route, as unlikely as that seems right now. 

The few times I've ever engaged with technical support were for upgrades, and it was always pretty painless, with the one exception I mentioned before, where we had a problem with a host that ultimately required a hard reset. We're still not sure what happened to cause it to lock up, however, once it was back up everything was fine.

Positive

I had looked at other vSAN technology in the past, however, the cost was beyond our budget, especially after factoring in the cost of the support needed, since I am not a storage engineer.

The initial setup was easy. We simply had to unbox the servers, rack them, connect the cables, and turn them on. It was that simple.

The initial setup was handled in-house - meaning, yours truly. All I had to do after firing them up was add the hosts to my existing vCenter server, migrate all of the VMs over to the new Hosts/Storage, and, once done, shut down and remove the old hosts from vCenter.

ROI is hard to quantify since we've never used anything else. That said, at least without it there would have been many thousands of dollars just for the licensing costs and appropriate support would have been even more than that. StarWind provides comprehensive support on everything, as long as you buy the hardware through them too.

I'd advise users to do their due diligence, however, StarWind's technology works as advertised, at a much lower cost than the native VMware solution. Their licensing is simple and affordable, and their support is impeccable.

We considered VMware's native vSAN technology and may have gone with it if I hadn't found StarWind while searching for alternatives.

If you are looking at a simple, affordable vSAN technology, you can't go wrong with StarWind.

We use the StarWind Virtual SAN in a HA stack. We then use readily available HPE servers (DL380DL - 26 disk) to be the hardware. This allows us to have reliable hardware with reliable software and no downtime. It also drives costs down to almost nothing compared to hardware-based SAN devices. 

Year after year costs are also down with not needing to keep hardware warranties up, due to parts being available easily. Overall, we have saved many thousands of dollars by going this way. We see no difference in IOPS or any other performance metrics. 

We have also tested the high availability a few times (once on purpose and a few not). It seems to work flawlessly.

We are able to scale our storage much easier and cheaper than we would with traditional SAN or NAS systems. 

The cost justification is very easy since the overall cost is literally support for the software. We do not keep any sort of hardware support since we can just buy hardware as needed from anywhere. This means that you have to have some knowledge of hardware if you are picking it out - or their support is more than willing to help. I like this as it allows me to pick out how resilient I want my system to be and how much I want it to cost.

The ability to use off-the-shelf standard servers to increase storage space is great. For example, we use Gen 9 DL380 servers with 26 bays. This allows us to migrate to newer hardware at any time without having to buy new shelves or head units of expensive SAN solutions (or even worse, have multiple SAN support contracts going at once in order to swing data between them). This also makes it so we can easily keep older data without immense cost to our organization. 

Training is also easy as it is just one system to learn.

We just need more integration with Veeam. Overall, I like the fire and forget model, so really there isn't an immense amount of things that I would request. 

Possibly some reporting via SMTP of some metrics would be nice to have. That said, quite honestly I get that from enough systems already and end up ignoring most of them. 

If this was something I was logged into every day then maybe I would request more features. Then again, I would be more concerned with its quality (we shouldn't need to log in daily). I'm not really sure what more to ask for.

We have been using the solution for around six years.

Been using the solution for six years and have not had it fail.

I have scaled quite large. It scales well.

Technical support seems responsive. We've only used them a few times.

Positive

We had three different systems (Dell PowerVault, HPE Lefthand, Lenovo NAS) and they were expensive to keep and more expensive to expand.

The setup takes about five minutes.

I implemented the solution myself. 

The ROI is almost immediate.

I'd advise new users to just do some homework on what they need. Pick out hardware that can support it and get a license. The setup would be about 5 minutes.

Yes, we looked at Dell PowerVault, HPE Lefthand, and Lenovo NAS.

The solution offers great ROI.

We have been using VMware vSphere as a fail-safe storage solution in a virtualization environment since 2009. Scaling options were initially two nodes. In industrial operation, there were solutions from three nodes. The storage is deployed on a 1Gb-10Gb ethernet network and HP servers with SAS and SSD drives.

To increase performance, caching technologies based on RAID controller functions were used, and later StarWind L2 Cache functionality was used. In 2020, it is planned to deploy storage that is based on new technologies: Intel Optane memory (DCPMM storage), VMware Vsphere Enterprise Plus 6.7, and 25Gb networks.

We hope that this solution will be able to provide maximum performance using StarWind VSAN for Vsphere.

This solution made it possible to make a quick start of the project on the transition from a physical environment to a virtual one in 2009 with minimal financial costs. It was possible to fulfill the requirements for reliable data storage, taking into account the transition to paperless document management with the use of digital signatures.

The scalability of the solution made it possible to increase the size of storage, without large additional costs for software. Within one series of servers, it was possible to repair equipment without stopping the use of storage in an industrial environment.

It is fast and easy to deploy to StarWind SAN for someone who is not even a professional.

The most valuable features are:

• Multipath I/O over iSCSI and Ethernet;
• Use of standard ethernet switches for storage networking;
• High availability-cluster (active-active), in a configuration of two or more nodes;
• When using new (warranty) servers, you can forget about the storage service for several years. The users will not even notice the failure of two servers out of three;
• Caching storage using RAM and SSD media;
• Fast synchronization in case of minor network failures.

For the StarWind VSA vSphere solution, I would like to see a simpler and automated virtual machine installation process in terms of network settings.

The areas where this solution should be improved are:

• Use as a node server without RAID volumes to ensure a longer period of use of the equipment and faster recovery of the complex;
• You need a separate server responsible for the main node, which is synchronized in case of failure of one of the nodes;
• Use SSD caching to write to industrial operation;
• Monitoring the status of server equipment. Programmatically bypasses the offline state of disks;
• To circumvent the speed restrictions of the network data when using virtual adapters VMware Vsphere VXNET3.

We have been using StarWind Virtual SAN for more than nine years.

The solution is stable in the case of failure of one node. When you exit more than one, sometimes there are problems choosing the main one.

Scaling to the size of the storage, thanks to the creation of a new target, does not affect the performance of the system as a whole.

Scaling by including new nodes-requires timing for synchronization.

Over a period of nine years, we applied three times to technical support. In all cases, the problem has been solved.

In parallel, the use of EMC ScaleIO. Unlike StarWind VSA, the license price depends on the amount of storage and only one copy of the data is used.

The initial installation in the version under Windows is very simple. In the virtual machine variant, you need to configure the network inside the virtual machines

Implementation was within the company.

The solution is cost-effective.

The cost of deployment is minimal, almost a product out of the box.

The cost takes into account the number of nodes, so the size of the storage is not important.

We evaluated free options including FreeNAS and Ceph. Our experience was that FreeNAS has low performance and reliability, and Ceph was complex to deploy.

This is an optimal product for large fault-tolerant solutions.

We have utilized StarWind Virtual SAN (vSAN) as an iSCSI server alternative in a Hyper-V based installation. We ran a 30-day trial license in a lab environment. The StarWind vSAN solution was used as a software-defined iSCI storage solution for an imminent SQL Server cluster installation. This allowed us for a fairly quick integration solution for our SQL Server cluster shared disk requirements, without the need to invest in a high-cost Storage Area Network (SAN) solution. 

It is a good practice to use storage performance evaluation tools, such as Microsoft DiskSPD, to evaluate IOPS metrics and perform stress testing in a lab environment with synthetic transactions for your prospective application. In our case, we conducted synthetic transactions for stress testing to prepare for a SQL server failover cluster installation.

There are various reasons that led us to pick StarWind vSAN for our implementation. 

Firstly, because it offers a robust iSCSI-based virtual server which is software-defined and comes at a fraction of the cost, as compared to buying an expensive hardware Storage Area Network (SAN). 

Secondly, because it is compatible with KVM. We do implementations based on the KVM hypervisor besides HyperV and VMware, and StarWind vSAN is among a limited number of platforms which offer native support for KVM. 

Last but not least, it offers a fully functional trial license to test the product in a lab environment in a variety of deployment options, including both Linux-based virtual appliances and Windows-based executables.

StarWind Virtual SAN (vSAN) offers a significant breadth of features. The ones which were the most significant and value-adding in our topology and implementation included the overall admin and user-friendliness of the solution and the rapid deployment times gave us a platform for a very quick-to-market solution for our SQL Server cluster-based applications. It allowed us to develop a solution in less than 30 days with less than one-third of the overall estimated cost investment compared to a traditional hardware-based SAN.

The StarWind vSAN solution is versatile and offers broad support for different hypervisors and deployment formats. During our evaluation of our on-premises setup, we did not find any significant flaws. 

One point for improvement is to increase the performance capabilities of the Windows-based executable as compared to its Linux Controller Virtual Machine (CVM) equivalent. 

Another point for improvement would be to incorporate a more granular Role-based access control system (RBAC) natively inside the software to allow for more granular administration. 

Yet another point would be to achieve tighter integration and automation with cloud-based platforms, such as Microsoft Azure and Amazon Web Services (AWS).

I have used StarWind vSAN installations in a lab environment on many occasions over the past five years; the most recent of which was during a 30-day trial run in 2024.

There have been no dropouts nor any downtime during the deployment and during the evaluation operations of the product with our SQL Server cluster instances.

StarWind vSAN performs steadily under heavy usage and can scale well if needed to support larger-scale systems. In our case it supported a significant number of clustered SQL Server instances without any issues in scaling up when needed.

The customer service and sales team have been very responsive and helpful throughout the evaluation of the product.

Positive

We have used hardware-based SAN solutions based on the IBM V5000 series. We did not switch this solution. We continue to trust IBM V5000 and V7000 solutions for higher-end implementations, where budget is not an issue. In cases of lower budget and quick time-to-market implementations, though, StarWind vSAN has helped us make good progress.

The setup was straight forward in most aspects and it was based on a well documented step-by-step procedure, which was provided by the vendor.

Implementation was an in-house one.

Make the most of your 30-day trial license, and if needed, you should contact the sales department of StarWind to extend the trial license or upgrade to a full license. 

We based our decision on previous positive experience with StarWind vSAN. Also due to brevity of time and tight project timeframe, there was no sufficient time for evaluating other options.

I would advise that you implement the Linux-based Controller Virtual Machine (CVM) during your evaluation phase, since the expected performance metrics are better, as compared to Windows-based executable. 

As per StarWind software documentation, the Linux-based CVM offers a a wide range of features, better performance, and stability, including reduced CPU usage and lower I/O latency.

The MSP that I work for brought on a client who realized they needed help with IT after the acquisition of another company. In the space of a few weeks, that client nearly doubled in size, and the aged tech in use at each location previously wasn't going to cut it. 

While we originally quoted a traditional SAN deployment for the client, they were concerned about having a single storage unit with two very distant servers. They weren't interested in buying two SANs so that each location could host one. StarWind vSAN allowed us to keep their data synced between two sites without the extra hardware expenditure.

For my MSP, this successful deployment has earned us another happy customer and another potential future sales lead. The client has expressed no concerns about the deployment since implementation in the handful of times we've reached out to them since the project wrapped up.

Additionally, we have been able to use this deployment solution for the training of lower-level staff to get them familiar with the underlying generic concepts of SANs, both virtual and physical (or at least as much as we can for physical SANs using a virtual SAN as the lab environment).

Easily the core of this solution was the utilization of stretched clustering. As the client had acquired another company some distance away, they were concerned about having a single SAN in one location or the other. StarWind vSAN allowed us to keep a copy of the data local to each site without asking the client to pay for two SANs in addition to the two new servers they needed.

On the acquired end of the company, the reduction in hardware also meant that we were able to use their existing server room mounting hardware, as a new server and a new SAN would require a larger rack to be deployed as well.

The documentation listed on the StarWind website indicated that the search result for vSAN was for Windows Server 2016. It wasn't until we got into the article itself that we saw that Server 2019 and 2022 were also supported by the same document.

While my co-workers might not place as much emphasis on this next topic as I do, I did not see any indication that StarWinds vSAN is a usable solution with non-GUI instances of Hyper-V. While it might certainly be possible, the time restraints on the project meant that my plan to roll out hypervisors with as little overhead as possible (e.g., Windows Server Desktop features) had to be placed at a lower priority, and we were never able to look into this as an option.

The MSP I work for deployed StarWind vSAN to a client over the last month. They have been quite happy with it - and with us as a result.

The client has been happy so far, and we feel confident about this solution as an MSP.

Since the solution is built for small and medium businesses, its scalability is intentionally limited.

Our previous one-size-fits-all SAN mindset often priced us out of successful sales with smaller companies.

I'd advise future users to seriously consider the higher-level support packages. These can mean the difference between hours of downtime/angry bosses and a solution before you've even finished your coffee.

While each of my co-workers on this project researched their own solutions to this project, I only brought the idea of StarWind's vSAN to the table.

We have used vSAN as an SDS storage solution with fiber channel JBOD chassis as hardware and integrated the SAN with HyperV to supply storage to VMs. 

The setup was required to expand our storage capabilities, and when looking for solutions, we wanted an SDS system for easier management of new disks and disk failures. 

Our system, therefore, consists of many disks with varying quality, which for us is the true benefit of vSAN since we now can trust different levels of degraded disks and still stay certain that we will not lose data.

We have been able to use more on-prem hardware to reduce cost and also use old disks that we do not trust enough for ordinary RAID or usage.

The storage system has been a great expansion of our capabilities to store large amounts of data since we previously relied on cloud storage which became exponentially more expensive as we expanded our data collection and our pipelines which required more virtual machines and hence more storage. 

With the web GUI available, it also became easier to monitor disk health instead of always logging in to the respective storage servers and checking status, which sometimes only was available during boot in raid controllers.

For us, the SAN solution needed to integrate well with HyperV since that is what we currently use - although we are planning to add an ESXi hypervisor which made vSAN optimal (since it is hypervisor-agnostic and we can select whatever hypervisor we want in the future without the need to redo our storage system).

Furthermore, we have a lot of fiber channel disks lying around, which we had no good use of. Therefore vSAN was great since we could easily integrate these into our storage system and also distribute block storage via fiber channel to the hypervisors and other storage-requiring servers.

The setup and documentation for the installation with the free version could definitely be improved. It took some time to get it up and running; however, when running, it worked well. 

The setup is done in PowerShell and requires quite some knowledge about how to navigate windows through Powershell. Fortunately, there were scripts available to help out. That said, the documentation was not that thorough in helping me understand the scripts. This is definitely room for improvement since it would be nice to quickly get up a demo of the SAN running to evaluate if it works as one expects, which it did in our case.

I've used the solution for two months.

The scalability is great. It integrates with all hypervisors, and disks can easily be added.

It was far from the easiest implementation; however, we got it working.

We implemented the solution in-house.

We looked into TrueNAS and Windows storage spaces.

Our company needed a Virtual SAN solution that would fit perfectly into our private cloud architecture based on Windows Server virtualization (Windows Server 2016/2019/2022) and Hyper-V without having to substantially modify its composition. In this case, it has allowed us to provide storage with geographic clusters for the evacuation of resources in the event of a disaster, allowing data to be migrated between the different delegations and guaranteeing that we comply with current regulations regarding data protection, as well as ISO 27001 and ISO 22301.

The StarWind Virtual SAN product has allowed us to improve the availability of our services, as well as their security. On the other hand, it has allowed us to make these improvements without having to make a large increase in investment, as could have happened with solutions such as those from VMWARE, Dell, etc. In this way, we have also achieved clear profitability and an immediate return on investment (ROI). Of course, it has allowed us to align with the business continuity management strategy using geographic clusters for the evacuation of resources.

The StarWind support team is, without a doubt, the best part of this product. The engineer assigned to us for the implementation showed great involvement and a willingness to work and share his knowledge with our team, which was great and smoothed out the resistance to change as well as the learning curve. The support team is available to solve any problem efficiently. The team is always aligned with our needs, and they try to give maximum performance to the vSAN. So far, the solution has shown great stability with no noticeable issues. The ease of use has helped our juniors.

The only point they should improve is the amount of documentation available for the user, especially in the first preliminary phase in which we were testing the product on our own. This problem is really solved when the team of engineers is assigned to the project since, with the willingness of the support team to provide information when required, it is very easy to move forward and solve these deficiencies. On the other hand, perhaps it can be said that it would be interesting to publish a greater number of pre-generated scripts.

I've used the solution for three years.

So far, we haven't had a noteworthy problem to attribute to the solution. We only had initial problems due to the operation error of the junior technicians while they were learning to use the tool.

The scalability for us is perfect. The solution allows us to work elastically, responding to changes in the requirements of our infrastructure according to demand. In addition, it scales easily and quickly.

In my experience of over 20 years in the IT industry, I've noticed that they provide one of the best services available today. They are very involved and proactive technicians.

Positive

We evaluated other solutions, however, it is the first one that we implemented.

In terms of the initial complexity, it would come from the previous tests in which we did not have support or all the documentation. As soon as we contracted the software and had support, everything was easy, and we had an engineer that was really valuable.

The experience of the team that collaborated with us in the deployment is undoubtedly very high. The desire to work and the availability to share knowledge are points that, without a doubt, must be valued very positively.

Replacing the previous model with a vSAN model has allowed us significant cost savings. Even if we consider the license, it will not cost much to amortize the investment.

The investment is really low compared to other options, and the stability and flexibility guarantee the security of the investment.

We looked into VMware, Hyper-V, and some other options.

The solution is really easy to implement, manage and maintain.

I used the software as a virtual SAN solution. When I tried it for the first time, I found it easy to use and working perfectly. The most important thing is that the vendor keeps developing and enhancing the solution to include more robust features.

I have three servers running VMware ESXi and used the solution as a SAN for the VMware Cluster by connecting the servers as ISCSI targets to the StarWind vSAN using a 1GB network connection peer. That helped me to run my application with peace of mind.

I am currently running servers with a hosted application for my business, and I had a problem having them online all the time thanks to of server maintenance and updates. 

That's why I used a vSAN to avoid buying a hardware SAN and use my existing servers only. The software improved my productivity by allowing me to have high availability and fault tolerance in virtualization.

I plan to invest in NVME disks where the software provides perfect integration to speed up the systems and get cache capabilities.

We like the ease of management. The management was very easy and I was able to find all that I need in the software dashboard.

The ISCSI is good. The connection using software made it easy to me to connect my servers without extra investment in hardware SAN.

I like the vCenter plugin. This allows me to monitor the SAN performance in the VMware web interface.

It offers good fault tolerance and high availability. I can update or restart the physical server without worry.

It's got great deduplication and compression. I am planning to use this feature when investing in new NVme disks.

They need to invest more in the support documents for real issues happening when integrating the solution with the hypervisor. Also, they need to provide how-to videos on social video networks about the setup, upgrades, and migration from real hardware like HPE, DellEMC, or Fujitsu to vSAN solutions.

They need to make it easy for the customers to find a solution for any error happening during migration or setup. That way, it will be more accurate and have fewer errors.

We've used the solution for ten years up until now.