StarWind Virtual SAN Reviews

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.

Our primary use case for StarWind vSAN has been to reinforce networks for our clients in a two-node Hyper V setup by utilizing the Hyperconverged configuration. This enables us to create a failover cluster for a cheaper cost than purchasing a physical SAN (plus adds more redundancy as you technically get two vSANs as each host becomes a vSAN). The Failover Cluster then allows us to live-migrate Virtual Machines when required, for example, for maintenance, or in the event that we suffer hardware failure on one of the hosts.

It enables us to provide more solution options for our clients, with the reassurance that, when implemented, they will be efficient and stable. Unfortunately, due to the cost of it and the size of our clients, we find that we can't always use it. However, it's an option that we know is always available and one that we'd leap to recommend if the scenario can fit it. Personally, it's something I'd always want to implement, as, without it, most clients with two Hyper V hosts can only replicate virtual machines and not live migrate. 

The extra redundancy in a two-node hyper-converged setup has been the most valuable feature. If we wanted this with an actual SAN, we'd need to purchase not only one but two SANs and enable replication between the two. With StarWind, you get the vSAN replicated between the two hosts out of the box. The vSAN also offers fine-tuning options for the replication between these hosts. For example, if there was a host failure and we were to run off one for a period of time, once the secondary host is recovered, it will need to resync with the one that stayed up so that the data is up to date. You can choose whether to prioritize the replication speed or performance of the virtual machines. 

For me, the product could be improved by it being made cheaper. We can't use this as an option for some of our smaller clients. Being able to replicate RAM between the hosts would be a nice feature so that VMs could be live-migrated fully in the event of a full host failure. Currently, the vSAN offers the ability to live-migrate the virtual machine as the VHD is on shared storage, however, if the virtual machine were to be rebooted, it would lose the running configuration (e.g. memory, etc). If this could also be live-migrated, that would be gold. 

I've used the solution for two years.

We didn't have another solution previously. This was our first vSAN experience.

I tend to deal with the technical side more and stay away from the pricing.

I can't recall seeing anything else that caught my eye.

Overall, I really enjoy this product. It's easy to use and support is fantastic.

I started using this product when I had challenges with failover as one of the requirements for my client. I had to deploy the failover environment but the challenge was mirroring of the servers.

Now that I have implemented StarWind, everything is running perfectly.

The product I had bought for the client mirrors from one server to another. This means that an application installed on server A can still be accessed on server B. In my case, I had an access control system installed in one server but mirrored on the other server.

The most valuable features are easy installation, the appearance of the dashboard, the software runs as a native hypervisor component or in VM, and it does not require any deep storage and network administration or UNIX management skills.

A typical system administrator with minimal experience in Hyper-V, VMware, or Windows can do VSAN configuration and maintain VSAN operations.

This solution should be more self-sufficient, running without creating domains or failover clusters.

I have been using StarWind Virtual SAN for three months

The system is very stable.

Performance is uncompromised by the minimalistic hardware footprint, as well as the reduced deployment and management costs. StarWind VSAN brings to the table server-side flash and memory caches, log-structuring, and an absolutely minimalistic I/O path. The resulting performance is unmatched by either typical virtual appliances or physical shared storage.

I did not use another solution prior to this one.

The initial setup was easy and step-by-step, following the manuals.

Licensing is easy and the whole package is cost-effective.

I was directly recommended by the manufacturer.

For now, StarWind has satisfied my needs, as my requirement was to create a failover environment for the servers, also allowing the system to run with less administration. 

We tried StarWind because the other solutions we tried were not doing enough, and the performance of this solution was very good. The price is cheaper than other solutions. The physical server was very useful to set up a designer virtual server. 

This solution has given us real-time synchronization to make sure we don't have a single point of failure. Our company works seven days a week, twenty-four hours a day, and doesn't have the time to cut the production infrastructure.

The StarWind solution, in conjunction with our backup and disaster recovery strategy, provides improved performance and resilience. 

The most valuable feature of this solution is the support. They are excellent and you can learn a lot from the support team.

We have benefited a lot from its fast integration.

I wish there was online support because email return takes a long time and a faster solution should be found.

We have been using StarWind Virtual SAN for less than six months.

We have been using the product for a short time but have not seen any glitches.

The drives have been resized. This caused the loss of data and we noticed that you need a third-party vehicle. StarWind Training could do this. Scalability was very good in this respect.

Installation is not too complicated, but there should be more auxiliary resources. We used virtual and physical servers in the application. We have created a large number of virtual servers.

It took about three months from placing the order to fully up and running.

The StarWind team can do the installation together and help. You learn a lot from the support team. The installation takes a long time but the result is excellent.

Even though we got rid of our SAN, we are still getting higher performance for significantly less outlay, dollar-wise. It is more efficient on the management side. The technical advice and support is quite good.

The price is more affordable than other solutions. The product is excellent in value and benefit.

Overall, the Starwind software, support, and implementation was great. I would highly recommend it.

The solution can be used for configuration and management as well as a backup repository.

I have used it for Veeam Backup and Replication and VMware NFS Datastore and it has really worked well.

One point to highlight is how easy it is to configure and manage. You don't really need to be an expert. However, it is important to know the storage concepts.

Simply by following the intuitive interface, you can configure your devices. Following a tutorial, you get the basic administration you require.

The process of choosing this product was not very difficult. It fit what we were looking for and it fulfilled the technical requirements for the project. As for the IT department, the management and monitoring have been very easy since the solution's dashboard is very simple and user-friendly.

In the implementations that I have carried out with StarWind, something that is noteworthy is the way in which it impacted the processes based on the way the solution was chosen to how it was implemented.

They need to improve the speed of the interfaces, thus allowing for better traffic on the network. They should continue with the development of protocols such as LACP that allow aggregation and maximal connectivity.

As for the V2V converter, it would be a good option to develop it not only as a converter but as an option for the migration of virtual machines between platforms, creating integrations with Azure, AWS, and GCP. 

It could even be a way to migrate machines between HyperV, VMware, Nutanix, and other virtualization and hyper-converged environments.

I've used the solution for four years.

We had indeed tried a different solution, however, we opted for StarWind. Qnap did not have everything we needed at the moment.

The cost-benefit ratio is really well balanced.

We looked into Qnap and Synology.

This is a very user-friendly product that works well overall.

Our primary use case is hyper-convergence and storage virtualization.

Our configuration has eleven servers installed. Three of these are SQL servers, five are installed as application servers, and on the remaining servers, various small services are hosted. These include web servers, RDP servers, and so on.

StarWind vSAN for Hyper-V consolidated the last three servers into a failover cluster for load balancing and increased availability. This made it possible to transfer the specified services to virtual machines.

Initially, it was not planned to use virtualization, but at some point, I realized that it was necessary. I had no opportunity to install any shared storage and in this case, the StarWind Virtual SAN solution was perfect.

I did not have any type of failover cluster. StarWind vSAN for Hyper-V solves the problem without any kind of hardware lock-in and with its low impact, easy to configure vSAN solution. This made it possible to create a failover cluster with high performance without significant costs.

The most important features for us are:

• StarWind vSAN requires two nodes, which can be completely switchless, and it doesn’t require any additional equipment to get started.
• StarWind works on the iSCSI layer.
• StarWind requires at least two 1 GbE networks.
• StarWind works either on top of a hardware RAID or a software RAID.
• There are only three servers in our installation and it was great that I didn't need to buy any additional network hardware.
• The iSCSI protocol is quite simple to configure.
• The requirement for two-gigabit adapters also avoided additional costs.
• In particular, it was important to me that the implementation of the StarWind vSAN solution did not require reinstalling the operating system or reconfiguring the RAID.
  

It would be nice to add the ability to use raw partitions instead of file containers.

I think that using equal partitions would improve performance by eliminating the additional file system necessary to host the container

I have been using StarWind Virtual SAN for approximately six months.

I did not face any critical issue for our main purposes.

Very positive. As far as I understand, it will be very easy to scale.

Technical support is very competent in matters not only of the product but also of the features of the hypervisor and the operating system on which the installation was performed.

I have not used other solutions before.

The initial setup was not difficult. I received help with the first installation from technical support.

The vendor team helped with the initial setup and I rate their level as very high.

I think that purchasing StarWind Virtual SAN Professional Edition would be optimal for most.

As an alternative to StarWind vSAN for Hyper-V, I considered Microsoft S2D, but I had to abandon it due to the fact that it does not support hardware RAID.

I have not been using the product for long enough to objectively name the features that should be added in the next release or would not suit me in the current release. The functions that I needed to work on do not cause any complaints from me.

We have set up a dual StarWind SAN with a fault-tolerant volume for our critical virtual servers in addition to some non-fault-tolerant volumes for less critical virtual servers in both our corporate HQ and one of our large divisions. The corporate site is using Hyper-V and the other division using VMware ESX. Between the two sites we have 15+ physical servers with over 150 VMs running.

Our corporate site uses Dell servers w/SAS drives for the two StarWind nodes and the division site built two white box type servers using NAS-specific SATA drives. Both solutions have been outstanding.

The StarWind SAN solution has provided numerous benefits to our organization. First of all, the fault-tolerant volume has saved us twice from hardware failures maintaining the volume without any loss of service or data. In addition, having a centralized SAN has provided outstanding flexibility to our virtual infrastructure. Setup and management of the system are very easy and customer support has always been very responsive and thorough. Management of the StarWind system is mostly non-existent because once it is set up, it just runs.

The fault-tolerant volume has been wonderful and provides peace of mind. We have experienced multiple hardware failures at one site and the fault-tolerant volume worked exactly as expected with zero downtime. I really appreciate how easy it is to use the software and set up a fault-tolerant volume.

If there was one feature I would like to see it would be a built-in subsystem for managing UPS backups shutdown procedures providing a way to initiate VM shutdown on all host servers, shut down the host servers, then put the fault-tolerant mirroring in standby, and finally shut down the StarWind SANs. 

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

Stability has been rock solid. The only failures we have experienced have been in hardware, and the fault-tolerant volume worked exactly as expected.

Scalability is great.

Customer service has always been excellent. 

We previously used Openfiler then moved to Open-E, and finally Starwind. I would highly recommend StarWind and have in many cases, including for our corporate HQ when we were acquired.

Setup was easy and support is always helpful with any questions or even to walk you through the setup if you are a novice. 

We implemented using our in-house IT.

Before we purchased StarWind, we evaluated several software solutions and a couple of hardware solutions. In the case of the software solutions, StarWind was the clear winner in performance and ease of use. In comparison to the hardware solutions, it was a lot more economical.

We fully evaluated Open-E and StarWind. StarWind was both easier to set up and manage, and it also outperformed Open-E.

StarWind has been an excellent solution for our virtual storage needs. There are features like remote replication that we don't currently use but could provide excellent disaster recovery for a remote site.

This solution provides us with high availability and failover with fault tolerance across two nodes. Implementing a highly available environment made way more sense to our company using StarWind’s Virtual SAN than other SAN or virtual SAN solutions we looked into over the past few months.

It allows me to configure high availability and failover clustering with some fault tolerance, at a cost point that doesn’t break the bank for a small business budget.

Doing failover testing, things have worked pretty flawlessly.

The support for two-node implementation was great.

I would like to see some additional, and possibly clearer, implementation videos with some slower and possibly more detailed descriptions of what the various steps of implementation are for someone who is unfamiliar with high availability and failover clustering in Windows.

I have been using StarWind Virtual SAN for two months.

This is a very stable solution.

Scalability is excellent.

The technical support team is very knowledgeable.

I did not use another solution prior to this one.

The initial setup was straightforward.

I was able to implement this configuration following a couple of online guides from StarWind and a couple of third-party articles. I also had the StarWind support team available to me if/when I had any issues.

We implement this solution in-house.

Within days, maybe weeks. How much is uptime worth?

There are two tiers of support and in my opinion, support is worth the cost.

I did not evaluate other products before choosing this one.

My advice for anybody who is considering this solution is to give it a try.

Implementing a UPS along with it is a good idea.