StarWind Virtual SAN Reviews

StarWind Virtual SAN for vSphere provides redundant and highly available storage for our VMware vSphere environment. We have two Supermicro 2029BT-DNC0R servers with VMware ESXi 6.7 and one StarWind Virtual SAN for vSphere virtual machine on each. Local SSD-s are directly attached to StarWind Virtual SAN for vSphere virtual machine and software RAID is used to make storage from them. For StarWind synchronization, we are using Mellanox ConnectX-4 adapters and directly attached cable between nodes.

StarWind Virtual SAN for vSphere has helped us to reduce complexity and is more cost-efficient than an old solution. Previously, we had separate storage (EMC AX4-5) with a fiber channel environment. With StarWind Virtual SAN for vSphere we are not forced to use vendor locked-in storage hardware, have to deal with costly fiber channel environment, and our power consumption is also reduced. Also now we have fewer hardware components to worry about and more flexibility to change storage when and where needed.

StarWind Virtual SAN for vSphere is a software-defined storage solution that has reduced administration time for storage. It's pretty straightforward to install and setup it and so far it has been robust and worked as advertised from StarWind. It does have Windows Management Console, from where you can make main configurations and monitor events, etc. and Web-based Management interface where you can make software RAID and monitor environment main characteristics like LAN and disk traffic, and so on.

When StarWind Virtual SAN for vSphere nodes go offline unexpectedly, the nodes have to re-sync disks fully which takes a long time. We had a power failure and when both nodes came online, VMware vSphere didn't see StarWind disks before I manually re-scanned them form ESXi administration console even though it should happen automatically - maybe I had to wait till all the StarWind disks were fully synchronized but that toked in our case 8+ hours.

There are no security and bug fixes without an active support agreement!

I have been using it for a little bit more than one year.

Product is stable and works most of the time on it's own.

It's scalable.

Customer service is helpful.

This is the first software-defined storage solution for us.

It took some time to get familiar with the software and I did mostly set it up myself and in the process, it was inspected and checked by a StarWind technician.

In-house implementation.

We have not calculated ROI.

Something to keep in mind is that you are not allowed to install security and bug fixes without active support agreement.

VMware vSAN financial aspects give StarWind an advantage.

Product updates are not that frequent (two-three times per year). Also, it concerns me that back-end OS (we are using StarWind Virtual SAN for vSphere and it's built on top of CentOS 7) is not updated every time the update is coming out. For example, our installation is more than half a year un-updated, and there are many updates available for CentOS. StarWind support does not recommend installing them independently.

We are using VSAN in our private cloud environment to provide highly redundant CSVs to a Hyper-V Cluster. We are using a converged environment so we have two commodity grade servers setup as a highly available StarWind cluster, then we have numerous Hyper-V compute nodes which access CSVs from the StarWind cluster. 

We are able to use Veeam to backup and replicate the VM files from the CSV/cluster.

We use off the shelf 10 GbE SPF+ modules and off the shelf 10 GbE switches.  With MPIO, we were able to create a redundant network infrastructure to support our SAN network. 

We were previously using Microsoft Storage Spaces Direct, but that product was unreliable and practically unsupported by Microsoft. We were able to leverage our previous hardware capital investment and converted our infrastructure to use StarWind VSAN. The migration process was simple, and afterwards, we had a highly reliable SAN system. 

We've always wanted to deploy a software-defined storage system, as proprietary SANs do not meet our requirements. They are expensive and very inflexible. StarWind has been excellent.

The highly available feature between two nodes works without any issues. We have practiced DR scenarios and our CSV/cluster has always stayed online. The software has the ability to "elect" a master after a failure of one or two nodes, then it will resync after that without issue.

The management interface on the software is very simple. It is insanely simple compared to most SANs. The interface is also powerful when used to complete tasks that an IT administrator needs to complete.

The ability to use off the shelf hardware (servers, RAID cards, SSDs, etc.) is also invaluable in terms of cost and flexibility. 

A duplication feature inside of a CSV would be very useful. I'm sure there are a lot of duplicated blocks on a CSV that have 75 VMs of Windows Server.

StarWind relies on the underlying OS to manage the "SAN files" whether that would be a RAID volume, software RAID (such as LVM), etc. It would be useful if StarWind could incorporate the actual physical drive management inside of the solution, similar to Storage Spaces Direct.

A web interface for management and StarWind SNMP MIBs would also be very useful.  

One year.

The solution is very stable.  We have tested storage network outages with failure of one or two nodes. The solution is able to stay online or repair itself with ease. 

The storage is as salable as your underlying storage. If you are using hardware RAID cards, then you are somewhat limited for expansion, etc. It is still much better than proprietary SANs. 

Support has been very good. I regularly schedule off hours support sessions and their team has never complained. 

We previously used Microsoft Storage Spaces Direct but had numerous reliability issues with the solution. It was definitely not ready for a production environment. 

Setup was somewhat complex, but StarWind works with you the entire way and handles nearly all of the setup. 

We worked directly with StarWind. The experience was excellent. 

Less than one year. 

The premium support from StarWinds is a must have. The ability to have access to a storage engineer 24/7 is a must for a production environment. 

We had thought about proprietary SANs, but those didn't fit our requirements for cost and flexibility. 

We had a need for some high speed I/O in our data center to run some specific high demand virtual machines. We currently have an older SAN unit, but it's slow, since it uses mechanical drives. Therefore, we decided to obtain a bunch of Intel SSDs and attach them directly to the two virtualized hosts, then I used StarWind virtual machines as the controllers to tie them together into a VSAN. After that, I moved the VMs over. Once everything was hooked up and talking to each other, it works fine.

It is more of a perceptual thing with the users. The system that we moved onto it is our ERP system, which handles everything. It handles our orders, workflow, and shop work orders. It was by far the slowest, clunkiest system that we have here. When we put it together the StarWind Virtual SAN, and we moved it onto the flash drives, everything seemed to run a lot faster. I went from a drive system that peaked out at 2000 IOPS to a system that could now do over 200,000 IOPS. It was absolutely a night and day difference. Everything is just snappier. When you open windows, they instantly pop up. It is not sitting there, twiddling its thumbs, waiting for stuff to come up, which is huge. It seems user systems and interfaces have gotten so slow over the last 10 to 15 years. When things happen fast and snappy, it is a huge bonus in the user's eyes.

The software just works. That is what I like about good IT software. I rarely, if ever, have to go into the StarWind servers. I go in every couple weeks just to check if there are any Windows updates for it. However, for the most part, it is all hands off. It just works. It just does its job. I don't have to mess with it. I don't have to monkey with it or do anything. I am going into our backup system more often than I am our VSAN controllers. I have to go into the email on Office 365 to change things around (or figure out why somebody lost emails) more often than I have to worry about StarWind. 

In the IT world, anything you can just let run is amazing.

• The control panel is nice. It gives you a lot of good feedback as to the status and health of the VSAN. 
• The synchronization is very nice. 
• I like its flexibility. It is more flexible than most VSAN solutions that I have seen. For example, you can run it across two hosts. You don't need a third host observing it.

For improvement, I would like to see how the software determines which networks to use for which purpose. It seems like the naming terminology changes a bit from here to there. When I access the console on the computer, where is it going in through:

• The computer's connections?
• The heartbeat connection?
• The iSCSI connection?

It is a little odd as far as making sure those networks are isolated just for their function.

On the console, there is no good way to see how all the networks are allocated. Other than that, once they are set up and allocated, everything seems to run nicely. I just don't want, e.g., my heartbeat network bleeding into other things, like the iSCSI.

For this market, in general, it would be nice if I could go to a website where they had all the pricing listed comparatively, then maybe I could shop around.

It just works. I don't even know if there is a new version of it out there. I haven't checked if there's a new version, though I should probably upgrade it. Now, that I have the system sort of pulled apart, I am in the middle of upgrading everything. I moved our ERP system back on to our old SANs for a while. Now, the whole StarWind array is cleared off to be pulled apart and have new drives put in, I should probably look at whether it is all at the latest version.

It has good scalability. You can add in almost anything that you want. The only oddball thing is with the three-tiered licensing. If you are looking to do anything highly scalable, such as replace your SAN, which is what we are doing now, you might as well go straight for the enterprise version. Just save yourself the headache of anything else. However, if you have a small project, and only need a couple VMs on some high speed stuff, you can use the free version or standard version. The standard version has the support, which if you are in corporate IT, it would be foolish not to get it.

The times that I have called the StarWind ProActive Support, they were immediate and right there. I have had no issues with their support. When I call them, I am talking with somebody in very little time, and the people that I have talked to have all been incredibly knowledgeable. They knew exactly what was going on.

The only issue that I had was, at one point, we had a power failure which took out our main power system. The battery system powering our whole data center and the main switch (or something) blew out, so the whole thing wasn't delivering any power, even though we had it coming out from the wall. It took down all our hosts, just dirty, with everything running. When we brought everything back up, we had a hard time getting the VSAN to reinitialize properly. So, I gave the support a call. They went through it, and we found because it went down like that, we had to step everything and ensure the first one comes up, then the second one, then sit and synchronize them. Afterwards, we sent things out for it to rescan the array, then once it got up and running, everything was fine again. However, that was the only time that I was on the phone's screaming, "Help!"

This is our first VSAN solution.

It was a little bit complex with VMware, because it seems like they are a little more used to Windows Hyper-V.

The initial setup didn't take long. The only hang up was I didn't have some of the networking in place. I had to get a pair of ten gigabit network cards to run between the two servers for iSCSI links and the synchronization (the heartbeat). Once I got those in place and plugged together, then it was pretty quick and easy. 

Once the solution was up and running, it was pretty good. There were some extra scripts that we had to run on our end. 

I do all the maintenance myself. Now that it is deployed, maintenance is approximately once every two weeks. It is not even StarWind, it is checking on the Windows machine that it's running on. 

Recently, we have been in the middle of a project to completely retire our mechanical SAN and replace all those drives, each of which are about a quarter terabyte. We want to replace them all with four terabyte drives (SSDs), then move everything to a giant StarWind Virtual SAN controlling it.

I did the deployment mostly myself. However, with the purchase, I was able to receive some help. Therefore, I brought StarWind in just to check things over, ensuring everything was good. That is when we tweaked the scripts a bit, so if the servers were to reboot, it would tell the machines to rescan for the iSCSI connection once it came up.

As for implementation strategy, I had always kept StarWind in the back of my head in case I had a need to use it. When we had a need, I decided to make the suggestion. I went onto Spiceworks, where I knew some people there from StarWind. While I don't know if they are full representatives, they definitely spoke highly of it. So, I hit them up, saying, "I'm looking to do this. Is this thing possible?" 

One of the guys from Spiceworks put me in contact with a StarWind sales rep. When I described my project to them, he said, "Yes, it's easily done. All you have to do is this and that." He pointed me to some documents on their network to read through, and it was simple from that point. It's like, "I could do that, and I could probably do this all myself."

I got the free version at first. Then, I got the thing up and running, for the most part, without any help, aside from the reboot scripts. 

I tested it on a couple like dummy VMs, checking what happens if I reboot a machine. Everything worked beautifully. It was totally transparent. I never lost my network connection nor storage. So, I saw it was a win. Later on, I got the actual licensing, and this is when the guy came in to check over my installation, etc. Everything worked at that point and has been running ever since. That is when I moved the ERP system over on one weekend and have never really looked back.

This solution helped maintain high performance and data high availability on minimalistic resources. For example, with our ERP system, we went from an old spinning rust array to a all-flash array. Because StarWind allows that and for it to be a VSAN for high availability, if I lose a host, the ERP system will still continue to run. If I have to put a host into maintenance mode, and move all of its processing to the another, I can do that because it is transparent. StarWind doesn't care. When I get the host powered back up, the array resynchronizes, and everything runs as normal. So, it works, as far as high availability. Like any other good system, it is transparent. Behind the scenes, it does what it's supposed to do.

I was so impressed by what I saw, because at first, you set it up for free. I set it up for free to see how it worked, because I was losing nothing but time. After I set it up, and everything worked, I was like, "Okay, I don't need anything else for this. Let's get the licensing and go."

The pricing is more than reasonable.

The licensing is a bit weird. If you license the standard version of StarWind, it allows you four terabytes. Then, they have a pro version, but with the pro version, the only difference is it doubles the terabytes to eight. However, that is just one drive size upwards in an array. You are first going from two terabyte drives to four terabyte drives, then you will soon be going to eight terabyte drives and upwards, for SSDs which are coming out.

Therefore, it is weird that they have the middle tier in there, their pro tier. Then, they have their enterprise, which is unlimited. I can see their licensing better structured if their lower tier either had less drive space or the middle tier had more, by maybe a factor of four rather than doubling it. 

From a sales and marketing point of view, the difference between going from pro to unlimited is unclear. It seems like, "Why not just go unlimited? Why even have the middle tier there?"

I did explore VMware's native VSAN solution. However, its biggest limitation is it requires three nodes. We have two very heavy duty host servers and getting a third one would have been costly. Each server is roughly around $25,000 USD. Therefore, getting a third one, so we could run a VSAN using VMware, was a bit prohibitive. This is why I went to StarWind in the first place.

Go for it. Just set it up and follow the instructions. Start with the free version. Make a test bed and play around with it. Then, see how you like it and how it works. because it works. There is nothing hard about it. Once you get it working and understand how the system is implemented in your data center, then everything else is dotting i's and crossing t's. You can get the official licensing for the support or any larger array sizes that you may need. You can allocate and tell it to transfer things as you normally would, as it is a very impressive system. It is probably one of the things that I have been happiest about in my environment.

The Log-structured Write Cache feature works works transparently, so I haven't really noticed it. I assume it helps with application resiliency and performance since it is working.

NVMe over Fabrics would definitely be incredibly fast. It is something that I don't have the architecture to even consider here, but it does sound very cool and fast. I have worked with NVMe drives and SSD systems, and the interface is much wider and faster than your typical, older systems, like SATA and SAS, which were meant for mechanical systems. It would be very impressive, and I would like to get a chance to work with something like that to see its performance.

I was not even aware that there was a way to integrate the solution with server OS native management tools, like vCenter. We are using the vCenter appliance, which is Linux based. It doesn't seem to integrate things too well into it, even though it is the recommended way that they have us doing it. If there is some plugin, or something for it to directly integrate, I would be totally up for that.

The primary use case is to provide a virtual storage for our data and virtual machines. Not having a budget for a physical SAN, we use what we have to get the best of what we have, this is primary reason for using this VSAN.

I don't have to stay late at night. Prior to using this VSAN, if anything happened to a server, everything went down. We couldn't do anything, and that was a nightmare. There was even a time where all the data on the server got wiped. People were unable to work for half a day.

We did have a backup. We had to go to a third party to get a hard drive, have it shipped, and upload the data back into the server, then foster continuum. It happened like that twice before they said, “Enough is enough, what are our options?” 

We had the option of a physical server, but the cost would have been $25,000 or $30,000. So, we had two servers that were underutilized, and they were good servers, old but well-maintained. Therefore, we sat with the IT company, where I'm employed, and they said, "You can either go with a physical server or a VSAN, Virtual SAN." We were like, “Okay, tell us about the VSAN.”

They mentioned, “You have two servers, buy more hard drive, RAM, and CPU." Those are things we could easily do. “Then, you will have the VSAN mirror one to the other, and whatever you have in one will other copy to the other.” For instance, if we lose a physical server, CPU, etc., it provides peace of mind, is cost effective, and we are able to use our existing infrastructure. 

The most attractive feature is, as a Virtual SAN, the data on one is copied to the data on the second. We have two in tandem. So, the data on one is the same as the data on the second one. If we need to do maintenance on the server, it doesn't necessarily have to be after hours, or recommended after hours. If I need to do something in an emergency, I can stop the sync and know that one server has all the information, do what I need to do, and sync them back.

Once we resolve the syncing issues, a first sync of about 4TB of data was done in under 30 minutes. The ability to have the office run and do emergency backup repairs without the company being down was a feature that I liked about this VSAN.

Initially, when we first started, the sync was horrible. It would take about 13 hours. However, they have since then improved on it. It also depends on the pipe. We had a small pipe back then. So, we would do things at around 8:00 AM, then by 4:00 or 5:00 in the morning (the next day), everything would be back on. Once we upgraded the pipe between them, within half an hour, it was synced.

StarWind made us understand that we had a small pipe and our drives were not SSD, but SATA. All these things contributed because they have tons of clients. Thus, if we were the only ones having this issue, then we had the issue.

Once we made the changes, we saw amazing improvement on the way it synced. Instead of 13 hours, it took five to ten minutes for it to complete. For improvement, there should be simpler, user-friendly training about how the system works. I have dabbled in it, but if I need to do anything I'd rather pick up the phone, call them, and say, "This is what I need to do," and they're more than happy to help. While they do have help documentation, there is a relatively steep learning curve.

You need to take into consideration the amount of data that you are syncing as it will come into play: The amount of data that needs to sync between the two devices and the amount of data that the pipe has to read right. 

With data verification, I would like to know how does the solution perform validation of data being synced between two VSANs. If data is corrupt, how does it determine that I'm not going to sync something because it's corrupt? How does any software determine that the data is bad. Then, how does it fix it? Because if we get corrupted on one server, we don't want to transfer it to the other server.

The product is stable. If we receive error messages, it is usually regarding the underlying technology since we are using servers which are 11-years-old.

If I am concerned about upgrading on my older system, I can schedule time with the support team and they will do the upgrade for me.

The solution is really scalable. They have various models. We told them the maximum data that we have and found the right one for us. We can grow, as it expands. It is not a one size fits all.

We have 41 people who can access data which resides on the VSAN.

I like the ProActive support. All the guys that I have spoken or dealt with are professionals. I find this very important. There hasn't been anything like, “Hold on, let me check with my colleague.” They know exactly what they were doing and are consistent. If guy A connects to my computer, he does step one, two, three, and four. There hasn't been any poking around where they shouldn't. 

Being able to call someone who is knowledgeable about the situation and circumstance is important. They also followed up to say, “Have you resolved the issue? Is everything okay?”

The ProActive Support gives me peace of mind because I am a one man shop, but with the technical support behind me, I feel like more than just one person. We spent two to three hours, depending on what we have to do, always on the phone, and they do not push to end the call. It feels like they are assigned to me until the end of whatever we are doing, which is important to me.

Since the beginning that is how the support has been. That is why we stayed with them. It's not that expensive. I have nothing but good things to say about them. All their work is documented. I receive an email afterwards documenting all the steps that they did.

We did not have a solution before StarWind. A consultant recommended this solution. We were also looking into physical solutions, not virtual.

I didn't build the system for us; I manage it. We had someone else do the build. If you spoke to him, he would tell you the build was easy. Give him the instructions, then he just created it. 

The deployment took two and a half to four hours. We did the deployment in the evening, and it was fully operational before we left. The deployment was done by a single person who did the connectivity and configurations, though there were some things that I had to do to build the virtual machine.

I am the only person needed to maintain, though I occasionally contact StarWind ProActive support, when needed. It is a low maintenance solution. It is as good as your infrastructure. Like every road, the foundation of the road determines the asphalt you put on it. If you have a good foundation (SSD drives), then it works well. The issues that we had were based on server error messages, because sometimes when people were downloading stuff, they'd say, "It is too slow." However, once we built a bigger pipe, we could see the change.

In hindsight, the Virtual SAN was meant to be a stop-gap solution. Make sure what happened before, if a server dies, we have business continuity. That was the goal. It so happened that the business continuity and stop-gap became a lasting solution which we continue to use because it works well.

There was a third-party consultant, who fine tuned it, but our guy created it after downloading the software. He has done it multiple times. If you were to ask him, he would tell you, "It's a walk in the park."

Our experience with the third-party consultant was excellent. The guy who I dealt with is a system admin. He is the one who informed us about the solution. He had deployed it for another client and thought it was just the right size for us, so he recommended it. 

There was an implementation strategy. We had all the data in a hard drive. After a crash, we had all the data in a backup drive. Once it was restored, we configured it on one server, then we transferred the data from that server to the VSAN occupied part of the hard drive array. After that, we built the other one on the other server, then the sync started. It was a phased in implementation.

You need to ensure that you have the right technical resource to implement the solution. Our guy was knowledgeable and a teacher. He imparted knowledge telling you why he was doing what he was doing and consulted you before doing it. He had a plan and submitted a proposal, which we looked at it. It showed what he needed and how it was going to take to get done. Therefore, the technical resource is very important.

This solution has helped us maintain high performance and data high availability on minimalistic resources. We have saved about 80 percent (versus purchasing a physical SAN) and peace of mind, which is important.

The pricing is fine for the work that it does. I have had no issues. When we bought it three to four years ago for what we needed, it was literally cheaper than the alternative which was ten times the amount and took up physical space. 

The license is reusable. We can always rebuild it and apply the license. Then, boom, we get new servers, apply the license, and we're back up and running.

We are not using the Log-structured Write Cache feature nor are we using NVMe.

We have not integrated this solution with server OS native management tools. We are just interested in business continuity. If the server blows up, we will still be in business. It does what we want, and we are happy with it.

As of now, since it does exactly what we want it to do, so I do not see where we would need to use features that we are currently not using. We were sold on the fact that we could use our existing infrastructure, and it syncs data if we lose one server. 

StarWind Virtual SAN might not be for everybody. We had the underlining technology, so it worked for us. Give it a try. You can't go wrong, because one of the things they told us is that if you no longer use it, StarWind would credit us a certain amount against a different solution that they had. It was a win-win for us.

StarWind Virtual SAN, along with two Fujitsu Primergy servers, forms the backbone of our hyper-converged solution. This storage, network, and compute solution is used for our Hyper-V cluster. From this cluster, we run all of our virtual servers, which in turn run our business-critical infrastructure. This includes domain controllers, file servers, database servers, application servers, and everything to support it.

We once operated with a physical SAN, several servers, along with the networking equipment and the required fiber-channel infrastructure.

StarWind Virtual SAN allowed us to eliminate the need for any physical SANs. We also got rid of the expensive fiber-channel equipment. Now, we just have two servers that form the StarWind nodes and that's it!

All of our storage, networking that includes 1GB and 10GB Ethernet, and compute power are all housed in the StarWind Virtual SAN solution. 

It's simple and very reliable.

The most valuable feature is the reliable storage replication, which enables me to create a robust infrastructure to run our business.

Presenting Cluster Shared Volumes (CSVs) from StarWind Virtual SAN to Hyper-V simplifies my storage management and reduces costs vs having a physical SAN.  

The solution has matured and I have no points for improvement.  

We have had StarWind Virtual SAN for nearly nine years.

I've now been using StarWind Virtual SAN for over nine years. While I have had underlying hardware go bad during this time, the Virtual SAN never failed. I have replaced an entire hardware node with zero downtime. It's rock solid.  

Prior to adopting StarWind Virtual SAN, I had multiple Dell Equallogic SAN devices.  When it was time to replace the Equallogic with new hardware, the costs were unjustifiable after learning about and evaluating StarWind Virtual SAN.  

Communicate with StarWind, they will work with you and your team to size a solution that works for you.  

Our organization was using physical storage platforms where we were facing slowness issues, and the cost of a conventional platform was high. 

We heard about the solution from one of our partners, and we got a demo of the product. 

The core features of the product resolved our issues, like high availability and integration of the solution with the virtual platforms. 

The StarWind Virtual SAN solution is cheap compared to conventional physical storage platforms. StarWind Virtual SAN is a good product when it comes to virtualization.

StarWind Virtual SAN helps us to improve our organization as most of our infrastructure is on the virtualization platform. 

StarWind Virtual SAN helped us in the integration with the virtualization platforms. By using common X86 servers instead of pricey proprietary hardware, StarWind Virtual SAN lowers the cost of storage infrastructure.

It is straightforward to configure, monitor, and administer the storage infrastructure with StarWind Virtual SAN's intuitive administration interface.

When their data storage requirements increase, enterprises may quickly enhance storage capacity with the help of StarWind Virtual SAN without having to pay additional fees for specialized storage gear.

There are different features that helped our organization as compared to conventional storage platforms. These include:

Scalability. Without the need for any downtime, enterprises can simply grow their storage infrastructure using StarWind Virtual SAN by adding new servers or disks to the current infrastructure.

Flexibility. A variety of deployment options, including hyper-converged infrastructure, two-node cluster configurations, and conventional SAN designs, are supported by StarWind Virtual SAN.

Performance. The usage of RAM and SSD caching, as well as the capability to offload storage traffic from the network using RDMA technology, allow StarWind Virtual SAN to operate at a high-performance level.

Cost-effectiveness. By using common X86 servers instead of pricey proprietary hardware, StarWind Virtual SAN lowers the cost of storage infrastructure.

Usefulness. StarWind Virtual SAN offers a straightforward and user-friendly administration interface that makes it simple to set up, keep track of, and administer the storage infrastructure.

The interface of the management console of the StarWind Virtual SAN is complex, and it's difficult for the novice user to interact with the management having less knowledge or training in the product. 

The troubleshooting guide of the product is also for the technical resources. 

The product needs to improve its features in terms of customer support and the management interface. The improvements in the management interface for the product help the user to work with the storage node having less knowledge or interaction with the product.

I have been using the StarWind Virtual SAN solution for the last six months.

The solution is being used to simulate physical SAN scenarios in a ESXi environment as a platform to demo various solutions to clients.   

StarWind SAN is an amazingly versatile product that eliminates the need to acquire an expensive physical SAN.  

In addition to ESXi, StarWind VLAN can also be deployed in other various platforms such as Hyper-V, Citrix Xen, and Linus KVM.  

StarWind vSAN allows us to start with a two-node resilient system that can be scaled up, down, or out. Even the free version of the product is very feature-rich. 

The product has improved the ability to mimic physical SAN environments to demo scenarios and troubleshoot problems. Customer response and satisfaction have greatly improved. 

StarWind SAN is an amazingly versatile product. We do not need to acquire an expensive physical SAN. In addition to ESXi, StarWind VLAN can be deployed in other platforms (Hyper-V, Citrix Xen, and Linus KVM). StarWind vSAN allows us to start with a two-node resilient system that can be scaled up, down, or out. Even the free version of the product is very feature-rich.

We like that it has the ability to mimic physical SAN environments. We able to scale up, down, or out and has an enterprise-level feature set.       

The configuration can a bit cumbersome. There is a CLI learning curve for which limited documentation exists.

I've been using the solution for two years.

The product is highly stable and available on multiple platforms.

This product is ideal for an SMB.

Technical support has been good.

Positive

We previously used Synology, which was going to EOL.

The solution offers a super easy setup.

We set up the solution with in-house staff with storage expertise.

The product offers a super low cost of entry.

We've also looked into VMware. 

We added vSAN capability for Hyper-V. We had a three-node standalone that used Microsoft Hyper-V and we wanted to convert them into a hyper-converged solution instead of formatting the servers and losing the windows licenses and installing VMware with the high cost of licenses (especially since we have two CPU sockets on each host). 

We used StarWind Virtual SAN with was a cheaper solution while leveraging the existing all-flash standalone servers. 

The installation of StarWind Virtual SAN was pretty easy, and the configuration was done in no time.

We were looking for a cheap vSAN solution that worked with Hyper-V. StarWind Virtual SAN gave us the capability to have shared storage between hyper-v hosts without buying external storage or using VMware instead of Hyper-V. 

Using this solution improved our organization to take advantage of existing servers while we had a very low budget. 

While we have a worldwide issue in the supply chain of servers, this was a very essential solution that helped the organization meet the application team requirements for the new solution installed.

We can turn Windows Hyper-V nodes into a hyper-converged solution. 

I like the high availability and redundancy of the Hyper-V nodes.

This solution does not have any specific hardware or disk requirements that can be found in VMware, for example.

The solution was very easy to use and configure the three-node failover cluster - and you do need to configure the multipath and the network interfaces prior to the StarWind software installation.

It provided a way for replicating data and a way to have HA, which was very straightforward to set up.

The documentation is good. However, if compared with competitors, it could be enhanced and made more professional.

Other products like VMware vSAN have a bigger user base and more forums. It will take more customers to use Starwind Virtual SAN to change this. For example, You can find more PowerShell scripts on internet forums, and GitHub related to PowerCLI (VMware) than you can find StarWindX Powershell scripts. 

Reporting capabilities of StarWind vSAN are also limited compared to VMware, which is considered a more mature product in the market.

I've used the solution for six months.

It's been so far, so good regarding stability (we've had no issues).

The performance provided by the solution is good for SMBs and specific departmental solutions.

We are using VMware vSAN on other solutions, and we are still using it, however, it is better to use VMware only as a hypervisor (obviously). Also, the hardware requirements are very costly to be compliant with, while using StarWind Virtual SAN there are no hardware or hypervisor requirements.

The initial setup is straightforward and easy to perform.

The setup is pretty easy for any mid-senior administrator.

StarWind Virtual SAN is a cost-effective solution.

Support also is very good.

We evaluated the following other options:

• Using traditional architecture by buying external storage and connecting it to the three existing nodes 
• Using a VMware solution. However, this will lead to losing the Microsoft licenses, and VMware costs more than StarWind Virtual SAN

It is good to have diversity in this market, and StarWind Virtual SAN is a good solution.