StarWind Virtual SAN Reviews

We have Microsoft Hyper-V.  StarWind is configured as a two-node cluster with a Windows environment. It is crucial for the Virtual Machines that give us the resiliency of Exchange, 4TB File Servers, Networking Services, Quickbooks Server, Terminal Servers, Virtualized Spam Protection, Active Directory Services, and a few others.

We needed something that allows for better resiliency than the old way of doing things.  We have seen other choices out there but this seemed to be the best one, given our budget and the hardware we wanted to use.

This StarWind solution has enabled us to be more resilient, once it was set up and tested.

Failover happens very smoothly. Recovery and maintenance are now less stressful and most importantly, it allows our users to keep working.

Before StarWind, we were dealing with an archaic way of synchronizing Virtual machines and data between non-clustered physical hosts and it was very frustrating. Now, things are less hands-on and easier to manage and navigate the virtual environment, including maintenance while other users keep working.

We found that robust communications between clusters and synchronization were key and most valuable to us due to the amount of data we were synchronizing.

The expertise from their technicians is very helpful even in the middle of the night, with the right support plan of course. The technical documentation, the follow-up and the details noted on a per-call basis was amazing. We really appreciate that kind of commitment to our success and stability that the StarWind software brings to our business.

Built-in Notification would really help and as I understand, their new release has this now.  

A mobile app to sync up for overview and status would really be helpful.

Also, it would be helpful if the software had a few more guides and links/videos on how-to's.

An "Update available" notification within the software would also be helpful and a guided wizard to do the upgrade properly would also be nice and efficient.

A better visual of the SAN storage/actual storage and how it is used would be good, especially when it comes to where the files are located on the disk. 

We have been using StarWind Virtual SAN for the last two years.

Stability seems great and we have not had any problems with the software.

Seems very scalable, although we chose to have a two-node cluster.

This area has been the best for us, especially being new to this technology. The support team was amazing with follow-up and they are super patient.

I have not used another solution for the same purpose. This was what I picked based on my research.

Initially, I didn't quite understand the framework and what exact hardware was needed so I had to do some learning. However, once all was in place it went pretty smoothly.

We did our deployment in-house, with help from StarWind.

Return on investment for us, I would say maybe breaking even. As I said, I wish the costs were better balanced.

The cost seems a bit steep, and I wish it was less expensive.

I have looked at Nutanix and VMware.

Mainly that the costs would be less expensive.

We are using VSAN in our cloud environment to provide CSVs to the Hyper-V Group. We are using a converged environment, so we have two commodity class servers configured as a high availability StarWind cluster and then we have many Hyper-V compute nodes that access the CSVs from the StarWind cluster.

We can use Veeam to back up and replicate the virtual machine files from the CSV/cluster.

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

Creating a high availability cluster required the configuration of the cluster on our hardware and the shared space to access the files has improved my organization.

Using the StarWind VSAN solution allowed us to reduce costs by using equipment that we already owned.

StarWind has allowed us to virtualize our environment without the huge expense of a dedicated SAN, putting cluster technology and its benefits within our reach. Server downtime was a constant threat to our operation before StarWind but has never been a problem since.

Updates to server hardware are now painless and done during working hours with zero stress. We had a RAID failure a few months back, and nobody in the building even noticed and there was no after-hours time used for repair.

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

The configuration is so much simpler, with fewer points of failure to worry about. Integration with Microsoft clustering has been perfect, allowing us to leverage our investment in MS server licensing to the fullest

The product can be improved:

• There is no good way to see how all networks are distributed on the console. Besides, once they are created and highlighted, everything seems to be going well.
• If we stay with Virtual SAN instead of managed devices, it would be nice to have more automated tools to manage iSCSI connections in Windows, which can be a bit confusing at first.
  
• We would like the documentation to be more complete. Most items are covered, but if you don't know something, you may need to contact their support.
  

We are using VSAN in our company for about 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 scalability of this solution is impressive. We're very happy to use it.

The experience of work with clients/technical support is very positive. Everything is fast and available.

The initial setup wasn't difficult.

We have implemented through a group of suppliers. Their level of experience is quite high.

Will soon pay off by reducing downtime and maintenance costs.

Make sure that you understand what all of the pieces do and don't make the assumption that you can drop support once setup is complete.

We immediately chose Starwind because our system administrator had experience with this product in the past.

This product is definitely worth the investment.

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 have been using VMware vSphere as a fail-safe storage solution in a virtualization environment since 2009. Scaling options were initially two nodes. In industrial operation, there were solutions from three nodes. The storage is deployed on a 1Gb-10Gb ethernet network and HP servers with SAS and SSD drives.

To increase performance, caching technologies based on RAID controller functions were used, and later StarWind L2 Cache functionality was used. In 2020, it is planned to deploy storage that is based on new technologies: Intel Optane memory (DCPMM storage), VMware Vsphere Enterprise Plus 6.7, and 25Gb networks.

We hope that this solution will be able to provide maximum performance using StarWind VSAN for Vsphere.

This solution made it possible to make a quick start of the project on the transition from a physical environment to a virtual one in 2009 with minimal financial costs. It was possible to fulfill the requirements for reliable data storage, taking into account the transition to paperless document management with the use of digital signatures.

The scalability of the solution made it possible to increase the size of storage, without large additional costs for software. Within one series of servers, it was possible to repair equipment without stopping the use of storage in an industrial environment.

It is fast and easy to deploy to StarWind SAN for someone who is not even a professional.

The most valuable features are:

• Multipath I/O over iSCSI and Ethernet;
• Use of standard ethernet switches for storage networking;
• High availability-cluster (active-active), in a configuration of two or more nodes;
• When using new (warranty) servers, you can forget about the storage service for several years. The users will not even notice the failure of two servers out of three;
• Caching storage using RAM and SSD media;
• Fast synchronization in case of minor network failures.

For the StarWind VSA vSphere solution, I would like to see a simpler and automated virtual machine installation process in terms of network settings.

The areas where this solution should be improved are:

• Use as a node server without RAID volumes to ensure a longer period of use of the equipment and faster recovery of the complex;
• You need a separate server responsible for the main node, which is synchronized in case of failure of one of the nodes;
• Use SSD caching to write to industrial operation;
• Monitoring the status of server equipment. Programmatically bypasses the offline state of disks;
• To circumvent the speed restrictions of the network data when using virtual adapters VMware Vsphere VXNET3.

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

The solution is stable in the case of failure of one node. When you exit more than one, sometimes there are problems choosing the main one.

Scaling to the size of the storage, thanks to the creation of a new target, does not affect the performance of the system as a whole.

Scaling by including new nodes-requires timing for synchronization.

Over a period of nine years, we applied three times to technical support. In all cases, the problem has been solved.

In parallel, the use of EMC ScaleIO. Unlike StarWind VSA, the license price depends on the amount of storage and only one copy of the data is used.

The initial installation in the version under Windows is very simple. In the virtual machine variant, you need to configure the network inside the virtual machines

Implementation was within the company.

The solution is cost-effective.

The cost of deployment is minimal, almost a product out of the box.

The cost takes into account the number of nodes, so the size of the storage is not important.

We evaluated free options including FreeNAS and Ceph. Our experience was that FreeNAS has low performance and reliability, and Ceph was complex to deploy.

This is an optimal product for large fault-tolerant solutions.

We have a four-host VMware environment with over one hundred and forty virtual servers that runs everything on our network except for backups and video storage. We are using Dell R730xd servers filled with a combination of hard drives and SSDs, as well as some PCIe storage for high-performance VMs.

We were able to create a much faster SAN with much more storage while saving a lot of money. It cost less to build an entire new SAN based on StarWind than to upgrade our old SAN. Now, when we want to expand, we can add storage in any way we want. This allows us to find the best prices without being tied to proprietary hardware.

The most valuable feature is the fact that the nodes are Active/Active, and allow us to do upgrades on any node without any downtime. This solution runs on standard hardware and allows us to use servers and storage that we already have, as well as non-proprietary hardware that doesn't cost a fortune.

The ability to manage the SAN with vSphere would be nice. It would also be of benefit to have more vSAN-like features, like not having to worry about creating multiple volumes. It would be nice if we could designate pools, or tiers, for storage of different speeds, and then assign rules to new VMs that would automatically place them into the proper pool.

We have found the software itself to be highly stable. It just works.

This solution seems highly scalable, with the only limitations being management after a certain point.

I had some issues, early on, that ended up being hardware issues on my end. The StarWind support people were more than willing to help me out with them, and this including jumping on remote sessions to figure things out whenever I needed help.

We used Compellent (bought by Dell). When we bought it, they discounted it heavily to be competitive, and it was at the low end of what they offered. When we needed to expand it, the costs to do so seemed outrageous.

This initial setup is extremely straightforward. You install the software and then create volumes, which then show up on an iSCSI scan. Nothing complex about it.

We performed the implementation in-house.

We were able to build an entirely new SAN with much greater performance and more capacity for less than the cost of just upgrading our previous SAN, so the ROI was immediate.

The licensing is pretty simple, and the costs are straightforward. Once you buy the license, you are free to build your own hardware solution based on your needs.

We looked at EMC and HP, but both were also much more expensive than a system we could build ourselves based on the StarWind software.

Unless you need a lot of special third-party integration with other systems, it is a great low-cost solution that gives you whatever level of performance you decide, based on your hardware.

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.

We use it for data redundancy and failover.

Instead of having to maintain two completely separate systems:

1. The cluster where all the data processing is happening.
2. Maintaining the SAN clustering.

Now, we can do everything in one location, because the storage and processing are all happening on the same cluster. It has reduced our overall maintenance and overhead by having to only maintain physical boxes for one cluster instead of having to manage physical boxes for two clusters. 

It also has reduced the amount of switching, network connections, etc., because the converged StarWind Virtual SAN allows us to connect high-speed network interfaces between different boxes instead of having to connect SANs via the network, then connect those two clusters together.

StarWind is more cost effective because it is converged storage. Instead of having to pay for a full-blown SAN, as we did in the past, and having to maintain that SAN as a separate cluster, we now can use local storage on each individual node. So, it reduces the cost and overhead drastically.

NVMe is sort of the future, because it's so fast. In our next round, we will use NVMe drives exclusively for our main storage. Then, we will probably use two and a half inch SSDs for our nearline. 

The most valuable feature is the ability to lose a node and not have my systems go down.

If there are domain controllers inside the cluster, there needs to be some sort of logic allowing them to boot independently so all the rest of the domain clients can gain the authority they need to come online. We made that mistake at first. We have since moved one of our domain controllers out of the cluster, so everything can obtain whatever authentication it needs on the initial boot. Ultimately, Microsoft says they support it, but we would like to see all of our domain controllers running within the cluster, too. We don't want to have additional hardware just to run domain controllers.

The stability is excellent. I have had a couple of stability problems, but they weren't related to StarWind. They were related to some power problems that we had in the data center. Once we had those sorted out, everything has been smooth as glass. I did follow their advice in getting network interface cards, and we put in some very fast 40GB network cards. This has helped us a bit because everything happens very quickly, and StarWind support even helped me on the management interface to team the 10GB connections. So, the stability has been phenomenal.

Scalability has been very easy, so far. We have had to resize some of the drives. The most complex thing which we have had to deal with was that one of the servers needed more than two terabytes of space, and it was an MBR formatted drive. I found some tools that allowed me to convert from MBR to GPT without having to reformat the drive or lose data. Then, we were able to expand that, too. Those are normal Windows management tasks, but we were able to do them within the StarWind environment without having to use anything besides one third-party tool for the GPT conversion. That part of the scalability has been excellent because we can just allocate disk space wherever we need it. 

Overall, we have about 200 users. For simultaneous users, who are on all the time during business hours, it is probably closer to 60 or 70.

When I've had a problem, I have had someone respond almost immediately. If not picking up the phone and helping me right then and there, it's within approximately 30 minutes. They have been able to help me with every single type of problem that I have had. They have also helped me with entirely different stuff in the server environment, which has helped me tremendously. I pay for that extra support, and I'll upgrade it each time because it's so helpful.

I recently ran into a problem where all my user profile disks were full, and it was not clear to me how to enlarge that user profile disk. Their support person, Artem, just jumped in with me, and within ten minutes, he'd provided me everything I needed for the PowerShell commands. He enlarged the ones that he could. For the ones that were in use, he showed me how to do it. So, when they were no longer in use, I went ahead and enlarged them. Then, I mounted each of them and expanded them to use the space. If I hadn't had him, I'd have had three users who were down today since this just happened yesterday. 

Today, all three of them are fully functional. If I hadn't have had that quick response and willingness to help, it would have created some headaches. Instead, their support works really well. I'm very pleased with the StarWind technical support. It is excellent. I have the Premium support. I have never worked with a company who is as responsive and helpful with everything I run into.

Knowing that I can call the technical support and get a senior level technician if I need it any time is a huge thing. Because if I have to wait until business hours to get a consultant, I have to make an arrangement in the schedule with them, and if it's after hours, you will lose 24 to 36 hours in there. With Starwind, I can get help almost immediately, so its a no-brainer.

I would do the ProActive, except that I have a contract that does not allow me to have third-party monitoring installed on any of our servers. 

The Premium support (or Pro support), which is what I have, is worth every dollar. The ProActive support has the same people running it, so I am sure it is good, too. Unfortunately, I can't take advantage of it because of the contractual obligations that I have.

Our SDS software before StarWind was a SAN. It wasn't converged storage. It was a full-blown, normal SAN configuration.

We switched to StarWind because we were upgrading everything all at one. We ran into budget constraints which would make building a new SAN almost impractical, if not impossible, to fit it into the budget. Secondarily, the SAN required a lot of maintenance, and we were looking for a less expensive solution. We also wanted something that would not require so much technician time.

Previously, we had two full-time people taking care of the SAN, cluster, etc. Now, we only have one. So, StarWind cut our technical labor force in half (cutting this cost in half), and we didn't lay anybody off. We were able to nicely redeploy resources.

The initial setup is mildly complex to fairly complex.

For our implementation strategy, we virtualized some of the physical servers, and we already had several virtualized machines. Therefore, as soon as the StarWind environment was set up, I just imported the virtual machines, bringing them up and online. We did a few network configuration tasks to make sure everything worked, then we were good to go.

It only takes me to maintain it once it is up and running. I have a backup person who handles stuff if I go on vacation (or whatever), but it only takes one person to maintain everything.

The StarWind support team goes through it and does the installation with you. It was super easy for me. I learned a lot in the process, but they set it up. The deployment took three hours from beginning to end with just the StarWind support and me.

This solution has helped maintain high performance and data high availability on minimalistic resources. 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 Log-structured Write Cache (LWC) feature speeds things up for us. Our performance is better than it was on the SAN. However, I don't know if it's directly related to the LWC or whether there is lower latency between the onboard storage and what was the SAN. I'm sure that it helps performance, but I wouldn't know a metric to measure it, specifically.

With the support that I receive from StarWind, it has saved me at least two full-blown, paid Microsoft tickets. For each of Microsoft ticket, we pay about $600 USD a piece for it. While this is not a big cost, it eliminated a headache for us. In addition, we saved on technical consultant costs.

For pricing, you have two things that come into it: 

1. The cost of the hardware.
2. The software licensing pricing. 

When we did all the analysis for StarWind, it was approximately 20 percent less than any of the other solutions that we looked at. This wasn't our only criteria, as you don't want to buy the cheapest thing, then find out you have a problem. Also, StarWind isn't the cheapest solution out there, but it is certainly cost-effective relative to the major players. I haven't seen any difference in quality overall. StarWind works as well as any of the major players would have for us.

The scalability limitation for us is its licensing. At some point in the fairly near future, we will probably have to upgrade our license so we can store eight terabytes instead of four. We are currently at four terabytes, but we're starting to knock on the door of that capacity. Going forward, we will probably pay for a license upgrade, then we can add more capacity. We just haven't done it yet.

We looked at StarWind Virtual SAN vs VMware vSAN and StarWind Virtual SAN vs Microsoft Storage Spaces Direct.

With converged storage, we studied a lot of solutions and went into them all. We looked at Microsoft's solution for converged storage along with some of the other ones. StarWind had better pricing and deployment strategy. It also didn't have as many hardware requirements, which allowed us to spend some extra money on things that we really wanted, like 40GB network cards.

We read everything we could find when evaluating the solution. When you are doing something this critical with so many users who will be working on it all the time, you can't afford to tinker with it. We not only went and read all the reviews on StarWind, Microsoft Storage Spaces Direct, and VMware vSAN, but we put them in some trials and tested everything on our test network. StarWind was the one that we ultimately decided would fulfill our requirements. Happily, it has lived up to our expectations.

Of course, the support was a huge bonus. You don't know that until after you have put your money in, but once we had purchased it, we found out how good the support was all the way around.

We have plans to increase the usage in the future. As we need data processing capability, we will add more nodes. As we need more storage, we will obviously upgrade the storage licenses. We will need more storage before we need more nodes because we are only using a fraction of our total processing power at this point, but we are slowly starting to fill up on disk space. The time frame for upgrading our disk space will probably be in six to eight months.

We run everything from accounting, databases, email VMs, SQL Servers, etc. on it, anything that someone would expect on an enterprise environment.

We are in the process of installing OS native management tools now. It should make things easier. The Admin Center looks like a good tool.

Follow their recommendations on hardware configurations. The faster you can put in the components, the better the experience will be.

I always recommend everybody do their own research. If you do your research, you will find out that cost-wise StarWind will be more competitive. In terms of form and function, from personal experience, their converged storage system works very well and is extremely reliable. What is most important to a lot of consumers is how good the support is behind the product. While you can research it, you never know until you spend your money. Experientially, their support is some of the best I've ever worked with, even though they are based outside of the US. You're not dealing with Indian accents. They speak very clear English, and there are not the communication issues that you have with non-Western countries.

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.