StarWind Virtual SAN Reviews

Our use case is to provide a vSAN for Microsoft Windows Server failover clusters. We are a web hosting company that prefers to purchase smaller discrete servers rather than larger and expensive integrated with SAN solutions. However, we still want to provide a high-availability environment for even our small web applications.

We use StarWind vSAN to accomplish this goal without having to use the extremely tightly validated server hardware and networking options required by Microsoft Storage Spaces Direct.

StarWind vSAN has solved the problem of cost-effectively providing a high-availability failover cluster utilizing standard server and networking hardware. We save many thousands when purchasing hardware and the vSAN has never been the cause of any downtime. So, not only have we saved money, we have beaten our internal SLAs that our previous solutions were negatively affecting.

In addition, the highly competent support alleviates stress when we do have questions. Our technology stack has improved since we have started using StarWind vSAN.

First, we have found StarWind to be a "set and forget" type of product. It really is nice to not have to spend administrative time monitoring, tweaking, and configuring a product.

Second, the reliability has been exceptional. In the three years that we have been using StarWind, the product has yet to cause us any problems.

Third, their support team is excellent to work with when we do have questions.

Fourth, the documentation on the product is exceptional, and while not necessarily part of the vSAN product, they publish a lot of helpful information on their blog.

Perhaps more reporting features on the utilization, usage, and performance of the configured high-availability images and underlying physical disks would be helpful.

We have been using StarWind Virtual SAN for three years.

We've never had to handle any problems with the product.

Beyond a three-node direct-attach, some of the cost advantages decrease a little.

The technical support is responsive and competent. If only more companies were like this...

We previously used DFS to synchronize between nodes; however, it did not provide nearly the same level of reliability and is not a true HA solution as a hyper-converged environment with StarWind vSAN.

With the excellent documentation and having their support review our configuration, the initial setup was very easy.

We deployed using our in-house team.

StarWind vSAN has saved us far more than we've ever spent on it.

If you are looking at a traditional SAN for a small cluster, give StarWind vSAN because you will save thousands without any compromise. 

We tested out Microsoft Storage Spaces Direct and priced out other competing traditional SAN options.

Our team was looking for a reliable and cost-effective solution for our VMware vSphere platform.

VMware vSAN wasn't an option due to cost and scalability issues.

Enabling storage high availability across multiple nodes was our top priority as we couldn't risk having any downtime in case a node was to fail.

We ideally wanted a dedicated set of tools to administrate and perform maintenance on our hyperconverged storage.

That solution had to be as platform agnostic as possible so that we could reuse it with another vendor.

The product provides a robust and cost-effective alternative compared to other available products.

StarWind Virtual SAN allows our team to aggregate our cluster storage in a scalable way without seeing an explosion in the licensing costs.

It let us decouple our hyperconverged storage from the actual virtualization plartorm.

As an agnostic software solution, StarWind Virtual SAN could be re-used in other projects across different teams with another virtualization vendor. That aspect was key to the success of our department as all teams were able to work together.

Data replication is useful as it enables storage high availability on the cluster.

The fact that the solution is vendor-agnostic allows it to be used with any virtualization vendor while remaining a powerful abstraction over storage.

There are easy-to-use tools for the administration and maintenance of hyper-converged storage.

StarWind Virtual SAN also let us fine-tune the desired level of replication across all nodes, allowing the administrator to specify a custom number of fault to tolerate across the cluster nodes.

StarWind Virtual SAN architecture is slightly complex and requires the team to carefully identify and study how the solution integrates with VMware vSphere.

Tooling is spread across web UI plus desktop clients which can sometimes be confusing as the team isn't always sure which tool to use during maintenance procedures.

Also one drawback, when compared to VMware vSAN, is that StarWind Virtual SAN requires a lot of network interfaces in order to provide the same data replication and node redundancy features.

I've used the solution for one year.

We have never encountered any bug or problem that would bring the cluster down.

We are very happy with scaling, especially regarding licensing.

Technical support is very responsive, helpful, and friendly.

Positive

We did not use a different solution previously.

The initial setup was a bit hard to do by ourselves as there are many moving pieces and tools to operate. However, support helped us a lot with setting everything up.

I'd advise users to consider the scalability of the project as licensing can become a problem with competitors' products.

We did ook at VMware vSAN.

Highly available HyperV cluster. Our environment includes 2 Hyper-V hosts with onboard storage running about 20 virtual machines. StarWind allowed for a redundant cluster to be configured without any extra storage and easily create an HA cluster. StarWind Virtual San functions as the primary drivers for all of our storage needs in the highly available cluster. It is used almost daily to allow for live migration of machines and failover in the event of maintenance or physical host hardware problems.

StarWind Virtual SAN improved my hyper-v deployment by making it highly available. It was easy to roll out and it is easy to manage. It has greatly improved virtual machine reliability and accessibility. Deployment of StarWind Virtual SAN has helped reduce the stress of not having a cluster that would allow for virtual machine failover if a host has a hardware problem. It is reassuring to know that all virtual machines are in a safer environment versus running on standalone hosts with no shared storage.

Highly available storage is the most valuable feature. The entire rollout is hyper-converged and requires no extra storage further than the hosts in which Hyper-V is running. Another feature that has been great is the support from StarWind in general. We have their proactive support package on the main cluster that employs Starwind Virtual SAN. The StarWind support team is right on top of all monitoring activities. If I am maintaining a physical host and it has been down for too long, I will get a notice from StarWind to confirm a problem or inform them that maintenance is being performed. They are top-notch.

Management of VSAN itself could be improved. A Web UI for management would be great rather than an application installation. StarWind is testing a command center virtual appliance that I have installed in my environment. It is very much a step in the right direction to make StarWind Virtual SAN management easier and even Hyper-V as a whole. Something Hyper-V has lacked for years is a good Web UI to manage a host or cluster. StarWind has taken upon themselves to help with this as well as manage the Virtual SAN in a single pane of glass.

Five Years

Very stable. I've had little to no problem since rolling it out.

It should be easy to add a host to a cluster once VSAN is installed.

Excellent! 10/10

No. We used standalone hosts.

Setup is a bit complex but StarWind has great documentation to get setup and a great support team to assist in setup.

Implementation has been done using StarWind support and with an in-house team as we have 2 separate clusters both using StarWind Virtual SAN

12-24 months.

Evaluate your solutions. This is a great solution for those user Hyper-V and ready to hyper-converge.

Maxta, Nutanix, VMware, KVM.

We are currently running a Microsoft environment. The Virtualisation stack is currently hosted through Microsoft Hyper-V. We are using local storage and hosting our storage via Starwind Virtual SAN for our production systems.  

Currently, we are only running a two-node cluster to serve our Hyper-V storage. Both nodes are directly connected. This little two-node cluster currently supports all of our offices across the country.  

Our business has a heavy reliance on the systems and systems uptime of 24/7 is required.

Starwind has significantly improved our performance in comparison to our previous environment. Our uptime and our internal SLAs are great. Over the years, it has not failed us once. 

Their support has been amazing and is always there for us when needed. We have worked with various support members over the years and every single one of them knows the product without needing to escalate. Being Hardware agnostic has also helped us a lot to maintain our systems and update to new hardware without worrying about the usual compatibility issues.

Starwind is very easy to configure and even easier to provision.  

Even better is how simple it is to maintain and patch without any downtime.  

Over the years we have updated both the operating system and the hardware on several of our nodes without any downtime incurred.  

The cache features that are available have significantly improved our performance.  

The ability for us to manage all of our nodes from the same console makes systems administration very easy.  

Tasks such as adding, removing, and expanding volumes are very easy.

Starwind Virtual SAN has fulfilled all of our requirements. There is not anything additional we require. The product does everything we need and more.  

If there was one thing we could request, it would be the ability to shrink volumes. For example, we want to be able to decrease in the size of the volume. We understand this is not a limitation in the product as it can potentially cause more problems by leaving things behind. Also, even though we cannot decrease the volume at this time, it is easily addressed by creating a new volume with the appropriate size and migrating data over to it.

We have been using Starwind since 2015.

The solution is very stable. We have not had a single outage or drop due to Starwind.  Software has never crashed or not performed as specified.  Our uptime is only disrupted by server maintenance and scheduled periods.

The product is very scalable as you can add as many nodes as you require along with additional hardware.

In over 20 years of working in the IT industry, I have never encountered better support than I have with the team at Starwind. 

We previously used Microsoft Storage Spaces.

It was as if we didn't need to do anything. Starwind was there from the start to help us provision.

We handled the initial setup all in-house.

I would strongly advise companies to engage with Starwind very early in the design process as they can help with finding the appropriate path. The pricing model is very simple.

We evaluated HP SAN, Nutanix, and Dell Storage.

We needed a reliable shared storage solution for our VMware vSphere Essentials solution so we could implement vMotion and High Availability features. We decided to utilise a vSAN solution to reduce costs after looking at the price of external storage solutions.

In our environment, we have a 3-server VMware vSphere Essentials Plus solution that consists of 16 x HDD and 8 x SDD on-server storage. The solution is attached to 1GB network for production but we also have 10GB network connections available for direct-connectivity between servers.

The StarWind vSAN solution was implemented as a hyper-converged solution meaning that everything runs on the VMware vSphere solution. 

The StarWind vSAN solution was implemented according to our project plan with minimal outages to existing workloads. We have had no issues with the solution and it works very well with minimal administrative effort.

Recently, we had a memory failure that caused one of our VMware servers to crash. Due to the shared storage provided by the StarWind vSAN, all virtual machines on the failed server were able to failover to another server. Our helpdesk didn't receive any user complaints during the time that this happened. Once we resolved the issue, the shared storage resynched itself automatically.

We now have the ability to run critical workloads on the VMware infrastructure and have already proceeded to migrate active directory and SAP Business One workloads onto this platform.

We have found the solution surprisingly simple to use. The management console allows us to monitor the solution and we have configured email alerts to alert us about critical issues. These alerts have been proven to work in an actual failure scenario, for example, when we had a memory issue with one of our servers that caused the entire server to crash. The management console also allows us to monitor the solution performance and provides us with access to system logs.

The level of support provided by StarWind both during pre-sales and post-implementation has been excellent. The solution validation session with StarWind engineers was one of the best we have experienced and the vendor has also demonstrated a willingness to create a long-term relationship.

The solution is also quite flexible. As an example, other vSAN solutions that we looked at had more stringent requirements regarding mixed HDD/SSD storage which wouldn't have worked in our environment.

The main thing I would like to see improved is the level of documentation. I had some initial difficulties understanding the solution which could have been solved via additional documentation aimed at newcomers to their solution. Although the solution does admittedly have many moving parts, I found that internal knowledge transfer to my peers was not that difficult. Hence I'm convinced that better documentation would have helped.

I would also like to see a better system implemented for obtaining updates for solution components. The system at the moment works on a request/response model.

We've been using this solution since the start of this year (2021).

The solution has proven to be reliable with the need for minimal administrative effort. During an actual failure with memory on one of our servers, everything worked exactly as planned. We didn't even receive any issues/complaints from users via our helpdesk.

During the solution validation session with the vendor, we spoke about benchmarking the product. After performing the recommended tests, we were satisfied that the solution would meet our performance needs (both in terms of storage and networking).

We haven't had any issues with the solution so have had no need to request service/technical support. However, our experience during our project makes us believe we are in good hands if we ever need anything in the future.

We did not use a different solution. We initially implemented our VMware vSphere Essentials solution using direct storage and didn't have access to features such as vMotion and high availability. The StarWind vSAN solution allowed us to implement shared storage and pave the way to migrate critical workloads onto the VMware infrastructure.

We complicated the initial setup process a bit because we wanted to perform the design, implementation, and migration ourselves. This led to some difficulties in terms of initially understanding the solution. StarWind helped to fill in the gaps and our implementation and migration went completely to plan with little need for downtime. We were able to implement the solution on two servers while keeping our workloads running on the third server. We then migrated the workloads and built the remaining server.

We wanted to perform the design, implementation, and migration of the solution ourselves. We asked for help where needed during the design stage and found the vendor was very knowledgeable and could quickly answer all of our questions. We performed the implementation ourselves and then conducted a solution validation session with the vendor. During this session, the vendor validated that everything was configured according to their best practices and also performed some advanced tuning. We also had an open-ended discussion about how to operate the system. This solution validation session was one of the best I have ever experienced.

The level of support from the vendor throughout the entire project has been excellent and they have been more than willing to develop a long-term relationship. 

We were price-sensitive and wanted to minimize expenditure on additional hardware. The ability to utilize vMotion and High Availability features in our VMware infrastructure has already repaid the cost of the solution.

We found the StarWind vSAN solution was cost-effective compared to alternatives. You should talk to the vendor (or a good partner) about your needs because there are some differences in price based on your environment. We also recommend purchasing support.

In our case, we purchased StarWind vSAN for vSphere Essentials Edition which included 1 year of standard annual support and maintenance.

We initially looked at several external shared storage solutions and found them to be cost-prohibitive. We then evaluated vSAN solutions from HPE (this was discontinued) and the native solution from VMware. The native solution from VMware had fewer moving parts than the StarWind vSAN solution, but was more expensive and didn't provide the required level of flexibility that we needed regarding mixed HDD/SDD storage.

We strongly recommend that you develop a good relationship with the vendor (or a good partner). In our experience, they played a key role in the success of the solution.

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.