The Windows Server Storage Spaces Direct (S2D) technology allows you to get the desired result, but this technology appeared only in the 2016 version. In the earlier Windows Server 2008 software, this technology does not exist, this was the reason for choosing StarWind. The …
Previously, we used Storage Spaces Direct from Windows Server 2016 to create a failover cluster on 2 nodes, but this does not work with all types of raid controllers, and this only works in the datacenter version, which is very expensive for our tasks.
Verified User
Technician
Chose StarWind Virtual SAN
I selected "Windows Server" since I couldn't find S2D in the list... S2D just sucks overall. Crap UI. Crap CLI. Megacrap documentation. VMware is very expensive...
StarWind Virtual SAN offers more fine-grained features and better performance and stability as compared to the Microsoft Windows Server iSCSI storage server on Windows Server 2019. It also adds the significant benefit of supporting not only HyperV but also VMware and KVM. This …
Verified User
Director
Chose StarWind Virtual SAN
We evaluated several alternatives, including Microsoft Storage Spaces / Stormagic and Nutanix AHV. StarWind Virtual SAN stood out due to its cost-effectiveness, ease of deployment, and ability to deliver high availability without requiring expensive proprietary hardware. Unlike …
StarWind VSAN provided a cost-effective solution without compromising on essential features. The straightforward setup and management were crucial for our IT team’s efficiency. The excellent customer support and proactive monitoring were significant factors in our decision. Its …
We have not checked any other competition, as StarWind struck us as a well known, reliable and quick to implement solution with hardware agnostic properties.
We were initially utilizing HPE Lefthand OS as a virtual SAN which was then set to EOL. We evaluated a number of solutions including VMware vSAN and settled on StarWind. StarWind provided a better value, easier and more intuitive interface, and wasn't wizard driven.
StarWind Virtual SAN is the most flexible and reliable system I tested. Although there are other good systems in the market this is the most flexible allowing integration with many Hypervisors
Verified User
C-Level Executive
Chose StarWind Virtual SAN
StarWind Virtual SAN is fit for the purpose we are using it for and
other vendors are for their focus
StarWind in our experience has a better pricing service and customer support. Additionally, only 2 host machines are required to setup the VSAN compared to 3 machines minimum recommended by VMware vSAN. This allowed us to save money on the licensing costs,hardware costs, and …
Again, support! I don't care how good your product is, if you lack good support you don't have a complete solution. Try and get that from HP or Dell. So support was a big factor for us. The ROI is just too huge to not be a factor here. Their solution for us was 4X less than the …
StarWind saves countless thousands when compared to standard SAN products and offers reliability and support that a vSAN like MS Storage Spaces Direct cannot offer.
I like that StarWind Virtual SAN allows for heterogeneous hardware and not tied to one specific platform like Nutanix. In other words, we can use Dell or HP, or any other name brand with the proper specs to meet the basic criteria for a proper StarWind Configuration with Fast …
StarWind Virtual SAN for vSphere allows you to use two node setup and still provide highly available storage compared to VMware vSAN which requires three nodes minimum, also with VMware vSAN you have to use certified hardware and you have fewer options to choose from. StarWind …
Selected for its high availability and failover with fault tolerance across two nodes. Implementing StarWind's highly available environment made way more sense to our company than other SAN or virtual SAN solutions we looked into over the past few months.
We also tested Microsoft Storage Spaces Direct (S2D). StarWind vSAN was hands down, the easiest to configure. It wasn't the cheapest but it is worth the money. FreeNAS has a huge learning curve to it and requires specific hardware to get support for it. Proxmox is a similar …
For companies that have 4-5 or more servers, StarWind is a great solution to provide high availability for a low price. It can scale up very nicely for larger implementations to more like 15-20 servers with ease. Although we haven't used it for even larger environments, it's doable. What its not appropriate are really small locations that have 1-2 servers. Unfortunately no one seems to have a good HCC solution in this space.
Windows Server and Active Directory is very robust and stable, it has been a staple in every IT environment I have worked in during my career. Junior to Intermediate admins can learn Windows Server easily, the user interfaces make administration tasks very easy as well as the documentation available through a vast amount of resources. There are other Operating Systems available with no GUI which has a smaller attack surface, faster update installation and reboot time. Windows Server does have the ability to remove the desktop experience, however it is not something I have had experience with and I believe most administrators choose not to remove it.
the StarWind Virtual SAN allows us to use Starwind Management Console to confirm health of the sync
The High Available nature of the deployment means we can fail over VMs without end users noticing any downtime
Their support is proactive alerting when firmware updates are needed (including iDRAC firmware) or when there are any warnings in the event logs, and schedule a time to remediate the issue with you.
Complexity: StarWind Virtual SAN can be complex to set up and manage, especially for organizations with limited IT resources
Limited protocol support: StarWind Virtual SAN supports a limited number of protocols, primarily iSCSI and SMB3
Limited scalability for storage-only deployments: In storage-only deployments, StarWind Virtual SAN has a limit of 32 nodes per cluster
Lack of reporting and analytics: StarWind Virtual SAN has limited reporting and analytics capabilities, which can make it difficult to monitor and troubleshoot performance issues
Limited backup and recovery options: While StarWind Virtual SAN provides some basic backup and recovery options, it lacks advanced features such as snapshot management, backup scheduling, and offsite replication
Microsoft needs to minimize the update frequency by making the product more secure. It can become very exhausting trying to keep updated if you don't have a dedicated support team. It can become challenging where the business is unable to allow downtime for reboots as part of the update process.
Prone to security and audit vulnerabilities.
The operating system needs more CPU and memory resources compared to other options such as Linux.
Understanding the licensing model can be abit confusing.
Comes with a standard firewall, but not the most secured one available. Would suggest using a more secured firewall as part of your antivirus software.
Due to the number of vulnerabilities and the operating system being a target for hackers, anti-virus software is a must.
StarWind Virtual SAN is a great solution and is now an integral part of our network of servers. The product is superb and the support has been amazing. It's perfect for our organisation and we won't be looking to come away from it any time soon!
I've carefully reviewed the servers and services currently running on Windows Server 2012, and given the opportunity would renew them as is going forward. There are two systems I currently have in place, one is a very large Linux implementation for a large ecommerce site, and one is a very large backup solution front ended by FTP servers running Linux. Neither are well suited for Windows, but the overall network infrastructure is and will be Windows Server for the foreseeable future.
Overall I like the usability of StarWind Virtual SAN because it is a "Set-up and forget" software. Once you correctly have set up the parameters, StarWind Virtual SAN pretty much rolls by itself. The biggest fact that one needs to keep in mind, though, is that the licensing for StarWind Management Console needs to be purchased separately, and while managing StarWind Virtual SAN through the paid Management Console is really easy and is well documented, going the free or - in other words - PowerShell Template route can be taxing if you are not that deep into the topic. You need to be especially careful with it if you switch from paid to free because using the templates incorrectly can cause issues, we had a similar occurence, where we needed to re-provision the SSD cache and the StarWind Support (Yaroslav) helped through remote support and a switch to the Free version afterwards.
Anyone new to IT could easily use the familiar Desktop Experience (GUI) version because we all know how to use Windows, whether a client or server version. Once an IT user is more comfortable with the operating system, they can move on to the Core version, which is the way to go in almost all situations.
The solution has been tested under constant usage for 5 years now and there (knock on wood) has yet be an outage. There were instances if human error during the operation and the StarWind reliably intervened, either through a synchronization or reporting of a degredation of interfaces, e.g. the heartbeat interface.
The software delivered exceptional performance until now with very fast write and speed rates, around 900MB/s through a 10GBit connection on a virtualized fileserver. It meets our demands without any problems whatsoever and we are a very media heavy environment with TBs of raw data.
Their support team is dedicated to providing top-notch customer service and is always available to help with any questions or issues that may arise. Their expertise and responsiveness have proven invaluable in ensuring the smooth operation of our virtualized environment. With such excellent support, we feel confident in our ability to utilize this product to its fullest potential, and we highly recommend it to others.
Microsoft's support is hugely wide-ranging from articles online to having to contact them directly for the more serious issues. In recent years when I have contacted them directly, I have found the support o be excellent as I have found myself connected to very knowledgeable people in the field in which I needed the support. The online support available is vast and I tend to find most of the time that there is always someone out there who has had the same issue as me in the past and knows something about how to resolve it! This is the advantage of using industry standard and long-established systems such as Windows Server.
Overall the setup was easy, we did require some help from the technical support team but other than that, we followed all of StarWinds prerequisites and everything else just fell nicely into place with hardly any downtime. The downtime was only due to moving VMs from our previous cluster over to the new StarWind storage cluster.
Make sure that you have detailed processes in place for every server instance you plan to install/upgrade, if possible get the base OS loaded and Windows Updates applied ahead of time, and if using a VM take a snapshot prior to installing each role, as well as along the way.
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.
They are different experiences, and while the other solutions offer enterprise-grade stability and, in some cases, address Windows server shortcomings (such as patching), they all do the trick, but the other solutions require a deeper technical background/configuration of items at the command line, which some people are not fully comfortable with.
The software is very scalable storage wise. The storage is provisioned through config files, which are created either through PowerShell scripts or the Management Console on the paid version. After that the storage is provisioned through iSCSI. In our case, in case of expansion, we would have to run the PowerShell scripts and do another full synchronization to update any remaining backup nodes, but the procedure is clear and even easier via Management Console, just expand the RAID array, punch the new capacity into the console and start the synchronization!