StarWind Virtual SAN Reviews

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.

Our primary use case of this solution is the deployment of a highly-available Microsoft Hyper-V environment. Using the StarWind Virtual SAN product allowed us to deploy a Hyper-V cluster that provides uninterrupted failover between nodes that would have otherwise not been possible. Additionally, we have implemented the same redundancy on our dedicated file storage systems.

The Virtual SAN product has greatly improved the organization's infrastructure by allowing us to create a scalable, highly-available, and cost-effective storage system. It has integrated flawlessly into our Microsoft Hyper-V environment, which, among other limitations, previously required manual intervention to move virtual machines. Our file storage systems also benefited tremendously from the seamless failover we were able to deploy with StarWind.

The product's core feature of virtualizing our storage is by far the most valuable. The abstraction allows us to use commodity hardware, and upgrade/modify it on demand without impacting SLAs. It also provides a high degree of mobility, as the virtual SAN can be moved relatively painlessly between on-site devices and the cloud.

It's been a while since I checked the associated PowerShell module, but I would like to see an extensive set of cmdlets that could allow for easier automation as well as status management. 

No, the only bug that was encountered over the course of several years was due to our negligence in updating the software in a timely manner. Support engineers were very knowledgeable and able to pinpoint the issue quickly.

No, we can add additional nodes and hard drives at will without downtime. This is the beauty of virtualizing the storage.

Technical support has been fantastic on the very few occasions we've had to call them. The engineers aren't just well versed in the product, but also in Microsoft systems as well as storage/networking architecture.

Response times have been fast, and the support engineers follow-up consistently to make sure the issue is resolved.

Yes, we were using a non-clustered Hyper-V setup. The two main problems with that deployment that caused us to switch were:

• Single points of failure in both our virtualization and storage systems.
  The loss of one node in either system didn’t allow for seamless failover.
  

The initial setup was very straightforward and quick. The engineer used a remote session to quickly get the environment configured and provided insight into the architecture. 

Implementation was handled by an in-house team with help from the StarWind engineer.

Our ROI has been very impressive, as the only recurring costs have been the support contracts. As hard drives become cheaper and cheaper, expanding the capacity of our systems has been trivial.

As a nonprofit with a limited budget, we are very satisfied with the licensing model provided by StarWind. The initial setup was quick and mostly effortless. Additionally, the support has been superb on the few occasions we've had to reach out to them.

We were unable to evaluate other options because the dedicated SAN systems that provided the same level of redundancy were out of our price range.

The product is solid, simple to use, and well engineered. Very impressed and looking forward to future releases.

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.

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.

Our primary use case is for a distributed virtual SAN over two data centers. Virtual SAN uses three servers in two data centers.

Technically the change is enormous and the operational risk in case of disaster has been minimized. The monitoring is simple and the user interface is intuitive. The solution is stable and the upgrade was done without downtime. Now, the data is distributed on both data centers and data loss is not an option.

This solution has a very good user interface, with simple administration/management.

We find the support for NFS and iSCSI valuable. This solution is practically independent of hardware (if all of the technical prerequisites are met). It supports asynchronous replication, cloud storage, deduplication, and compression.

This product could be improved with the inclusion of new health check procedures. Operations performed in distributed file systems are complex and in case of network outage admins rarely know what is going on. Any kind of simple UI for admins is better than nothing. Something that would admins give fast, easily understandable information about status and rebuild status etc.

Technically, the solution works as described/expected.

This solution is very stable. The upgrade was done online with no downtime.

This solution can be expanded to a large environment when needed.

We were really positively impressed with the support and help they offered (purchased with the product - with no additional charges).

Their pre and post-sales support were partly the reasons that we choose this solution and overall I would rate their support as excellent.

Before we implemented StarWind Virtual SAN, we used scripts and backup software. This was more of a temporary solution than a proper solution for a production environment.

The initial setup is straightforward but we tested (evaluation) in a test environment.

Direct contact with the vendor (best option).

StarWind is best price/performance for SMB.

We evaluated other solutions including SimpliVity and VMware vSAN, but StarWind Virtual SAN was on top (best choice). This was not just because it fit our budget, but for their pre and after sales support.

We spent time evaluating this product and there is no doubt that the choice to implement this solution for production was the right one.

My advice is to call (contact) them and they will answer your questions to help you find a proper solution.

Before, we used a cluster of two Windows servers with shared storage system on a single SAN. One of them was a working clustered SQL server with database mirroring. Every part of the system was redundant except for SAN.

It was almost satisfying.

Every cluster server system we know needs shared storage system. The cluster could be fully redundant, but this redundancy is worth nothing without a redundant storage system.

We had a single SAN system. As a single system, SAN was not redundant. But we needed a redundant storage system. We always were afraid that once upon a time our SAN will stop to work.

We, of course, had backups, but it was not enough.

What we needed was the system with no data loss in case of issues and with no interruption (or only several seconds of interruption) in data processing.

We were looking for a relatively simple and not very expensive solution.

Why have we selected StarWind among other storage solutions? Actually, I don’t know why. Simply, I was looking for a solution using Google. StarWind was the first system I found that gave me hope. When I did some tests with StarWind, I stopped looking for anything more.

Now we have a redundant storage system, so our cluster system is fully redundant. We now have two clusters of two nodes Windows Hyper-V servers with StarWind VSAN working as hosts.

• It was really very easy to implement, but without support, I couldn't optimize the system, and StarWind gave me technical support on a very good level.
• A good price is also considerable.

I would like to have an easy way of automatic notification about issues, even when I'm away. The system has the possibility to send e-mails, but only in an internal mail system. Simply there is no possiblity the e-mail sender to log on smtp server. Several years ago some smtp server didn't require user to log on. But now it's impossible to send e-mail without login on. So if I had my own company internal e-mail server I could use it. Otherwise not. It's not enough for me.

OK.

It's OK.

Support is on a high level.

I've used SAN hardware before with no redundancy.

It was easy. But to achieve optimal performance, I needed support.

In-house.

No idea.

No idea.

I didn't. StarWind was the first solution I found, and after the first tests, I stopped looking at other solutions.

No.

• I've used StarWind VSAN for replicating vSphere datastores and in Microsoft SQL and file systems clusters. 

• I used one in mission-critical systems like a call center, SQL, SharePoint, etc.

My company data is essential to us, and we never lost data, so building the HA storage was our absolute priority. 

For the last six years, StarWind VSAN protected our transactions of more than 100 billions of dollars.

• Stability
• Performance
• Security
• Easy to solve problems
• Vendor support always is ready to help :) 

• Linux version for vSphere could incorporate deduplication. 
• Also, the documentation for configuring alerts in vSphere is not simple.

It's stable as a rock.

Performance is very good but the bottleneck is the network. It is good to have 10gb links. 

Very good. I've got standard support but the reaction time is always 1-2 hours. 

I used StarWind and VMware vSAN, but StarWind is 10x cheaper and gives us a solution independent from the hypervisor. This is more secure.

The initial setup is easy, but after buying, support can help you with the installation and optimization.

I implemented through my team, but support helped me optimize the iSCSI paths.

StarWind has the best price.

The version for vSphere is very cheap, and anyone interested should buy a three-node version for the test environment.

No.

Thanks support for the quick help: I think you never sleep!