StarWind HyperConverged Appliance Reviews

We were able to consolidate four of our Hypervisors (with no redundancy) into two HCA servers with High Availability. We now have replication across both servers and fewer servers in the rack to power and we are all-flash now.

We also implemented the 10G ports on the StarWind Servers, beginning our step into a 10G backbone. This allowed our rack to become significantly less crowded with cable management.

Our HVAC is having to run less and I am sure there are some cost savings associated with that as well.  

It has brought us to another level in redundancy. We have two replicated copies of our data on-site in HA, which we then backup locally and then offload a copy to the cloud.

We also went with the all-flash solution, so our IOPS jumped exponentially.

In addition to that, we have started to implement a 10G backbone with the StarWind HCA being the first in it.

The most valuable feature they have is their support. We opted for 24-hour monitoring and support, which has already paid for itself. I had decided to move cables around and when they saw it, they and reached out to me to get it corrected.

On top of that, during our initial configuration and migration, they were able to work through any issues that may have come up, mostly due to the specific legacy equipment that we were trying to migrate to the new servers.

The command center is a nice piece of software that lets us view our entire setup.

They have a pre-install questionnaire and it asks about network addresses and such. I made the mistake of thinking they were asking about my current setup. They received that information and applied it to the new servers. When they arrived, I noticed it before we patched them in, which would have caused several IP conflicts.

I think that the pre-installation questionnaire was a little confusing and ambiguous. I could have asked for clarification but I just filled it out and sent it. It would be nice if they were just very clear on what they were asking for.

We are new to StarWind HCA and have been using it for about four months.

Stability-wise, we have had no issues as of yet, whatsoever.

This solution is very scalable. We bought it with plenty of room for expansion as well, so we don't have to worry about outgrowing it anytime soon, but if we do, it is a simple no-downtime, procedure.

Technical support is their best feature!

The initial setup was both straightforward and complex, but their support handled everything.

Implementation was through StarWind and was a great experience.

I was able to bring the price per year down by going out to a five-year plan. That works for our situation, it may be different for yours.

We evaluated Nutanix and Dell HCI.

We are an SMB that hosts our ERP on-site. Our infrastructure is shared with a group of inter-related companies, so uptime is critical since several entities rely on our core services. StarWind HCA is the core of our network and hosts all of our critical VMs. We needed a cost-effective HA solution that was easy to manage, as we have a very small IT department that is concentrated mostly on business process improvements. The last thing we need is complex systems to manage taking our focus away from that.

We went from a vSphere compute cluster with an external SAN made by a company that is in perpetual financial trouble and have shifted business focus several times. Not only was our traditional SAN expensive, but we also had no confidence in the vendor. StarWind HCA is commodity hardware, so we eliminated the proprietary hardware issue. 

We also substantially reduced network complexity by eliminating that standalone SAN. That reduced complexity has allowed us to concentrate on improving other areas of our network.

Proactive support has been great, you will receive an email from StarWind soon after their telemetry service sees anything out of the ordinary with either the StarWind services or any critical issue related to your cluster of VMs. The appliance support goes beyond my expectations by helping with some Hyper-V issues that may not be directly related to the StarWind services.

The most valuable feature is its simplicity. It really isn't any more difficult to manage than a standard Hyper-V cluster.

Communication could have been improved during the implementation process. I've also been looking forward to further development of their management console which has been slow to materialize. StarWind is promising full cluster management and backup integration in a single-pain-of-glass console.

Possible new features could be CSV-level snapshot capability, Veeam integration, and maybe a more straightforward setup. Granted, you don't have to worry about setups with the HCA, but if you want to implement StarWind vSAN in a lab to test it is a tedious setup process.

We've been running our StarWind HCA for about two years.

Technical support has been willing to help and train even on simple questions.

We previously had a vSphere cluster with a standalone SAN. We wanted a less complex solution.

The initial setup is really easy. StarWind handles it.

In-house with StarWind help.

The HCA price is all-inclusive (setup, hardware, support, warranty), except for your standard Microsoft Server licensing.

We evaluated Cisco and DataCore.

The StarWind HCA solution provided our company with a turnkey hyper-converged platform that strengthened our processing and storage capabilities by greatly expanding our RAM, processors, and flash-based storage.

It also enabled us to take advantage of VMware vMotion technology. This allows us to transfer a virtual machine from one host to the other without interrupting production, which is critical in our manufacturing plant.

I haven't had to make any software related changes since the solution was implemented.

By having multiple servers, we are able to perform maintenance on one server while the other is still operating. The speed of the flash drives helped with performance, and the support that StarWind offers is very professional and accommodating.

We had to engage with support several times during the migration as we made licensing changes, and moved virtual servers from the old host to the new ones. The response time was quick and although there was a bit of an accent, I had no trouble understanding as the work was being completed.

The presence of built-in storage saved the company from having to purchase a separate storage array and related network equipment. When we looked at the costs for a storage array, they were somewhat higher than the solution from StarWind.

Knowing that the virtual machines will continue running in the event of one of the servers failing provides peace of mind. Also, having support readily available in the event of a problem helps as well.

We were impressed by all of the redundancy built into the solution to protect it from failures.

My only concern was with the terms and conditions of the proactive support. Our legal department didn't accept them, so we weren't able to take advantage of it. Having the heartbeat monitor working would save some time, by getting issues resolved by support as soon as, or possibly even prior to them happening.

I would request that the terms and conditions be reviewed and made more acceptable to corporate security so that we could finally turn on the proactive support feature, as it is included with our support agreement.

We have been using the StarWind HyperConverged Appliance for six months.

There have been no issues with stability since the solution was implemented.

It seemed that we would be able to increase the scale as needed.

The support at StarWind was very knowledgeable and was able to resolve any issues on the current call.

Our previous solution was a single server and it was out of support.

Its initial setup was complex, but that is why we had support from StarWind look after it.

It was implemented mostly by StarWind in coordination with our in house team.

The setup cost was included in the support.

We considered solutions from Dell and Nutanix.

We used this solution to upgrade a bunch of old stand-alone servers to a cluster. There were at least eight different servers, some up to ten years old, running production loads on Hyper-V. Since everything worked, it was hard to get budget approval. Finally, we got someone to listen and we were able to get momentum on this project.

We got the three-node cluster in, and moving everything over was easy with no downtime to the approximately 400 users. Now that everything is on a cluster, the redundancy helps IT sleep at night. We have had to do some maintenance and there has been no interruption. 

Our environment went from a hodge-podge of Hyper-V servers of various ages and capacities to a simple-to-manage three-node cluster. The three nodes are interconnected, so we didn't even have to invest in additional network infrastructure.

There is redundancy, so if one node has an issue, the users have no idea and everything stays functional! There is a noted increase in speed both on the production loads as well as the backup (Veeam) being much easier to manage and running significantly faster.

Power consumption is down, so there was less need for UPS capacity and cooling as well. 

The configuration we purchased was built on Hyper-V, so there was no additional training for staff. The rest of the management tools are on Windows, so anyone with a little bit of IT background should be able to figure it out.

The full suite of redundancy gives a nice sense of security for the whole environment. Support has been stellar and we're notified of an issue before we even knew about it. We worked with support to get parts replaced and delivered the next business day and there was no downtime to the users!

I think some performance metrics would be nice to see, especially on the storage side. Since we have a decent amount of storage on our cluster, 80TB, knowing what our IOPS and typical usage is would be handy. There are times where something 'feels' slow so it would be nice what was happening on the storage side.

I do wish that if we needed more compute capacity, that we could do it without needing to invest in a lot of network equipment. That is hardly StarWind's fault, but just something to think about. 

We have been using the StarWind HyperConverged Appliance for between six and nine months.

If we had smaller needs, the amount of expansion would have been more. We went fairly large since we only get money once in a blue moon. There is some additional storage scalability, although not a ton.

We can add plenty of RAM. If we wanted more CPU then sure, those could be replaced! 

We had one issue with a part failing, and we were informed by support before we even knew. The part and on-site engineer was dispatched. It was a redundant part, so there was no impact on anything. Nice to know they are all over it!

Nothing in the HCA realm, just stand-alone Hyper-V machines. 

The initial setup was very easy. Support ran through everything remotely and we were up in a few hours. It was nothing we probably could not have done ourselves, but it was nice to have an expert do it and have it up. 

We implemented purely in-house.

We didn't have any issue with pricing or any of the sales process. If anything, we were difficult with changing what we wanted to include on the HCA all the time. Sales rolled with us without any issue. 

We did look at moving hypervisors and HCA platforms but passed because the amount of change to management would have been a lot for the current staff.

We are very happy and the number of incidents and stress has been greatly reduced. 

We are an MSP that offers IT services to SMB companies in our area. We wanted to branch out and start offering hosting services in the form of offsite backup and server. To achieve this we needed a highly available cluster of servers. We started off designing a typical cluster/SAN setup but decided that we wanted the simplicity of hyper-converged architecture instead. In researching HCA we found that StarWind offered exactly that as well of proactive monitoring support for the cluster. Having an extra set of eyes on the health of the equipment was a huge selling point.

StarWind has given us the ability to have a failover cluster without the complications of a SAN network. We are able to offer extra services to our customers that we haven't been able to in the past. Small companies can be wary of the large cloud providers so having a StarWind HCA cluster we were able to give our customers the ability to grow into the cloud while also staying with a company they have worked with and known for years. With StarWind's proactive monitoring we can go about our day helping our customers and not have to worry about our cluster's health.

The most valuable feature is its Proactive support. They monitor the health of the cluster and hardware and reach out if they see anything out of the norm. They will then work with us through the entire resolution process whether it be a hardware issue or an issue with the StarWind vSAN services. If the issue turns out to be hardware related they will then work with the hardware manufacturer and get any replacement parts needed. Their techs are also very knowledgeable and have always been able to resolve any issues without any kind of long drawn out escalation process no matter the time of day.  

Multi cluster support for their Command Console would be very beneficial. Currently, you can only work with a single cluster at a time. The console is new so I expect much growth in this area in the near future. The other area that could be improved is the tech support locale.  Currently, all of their tech support is located in eastern Europe so if you have any issues understanding thick accents it may be a little frustrating. With that being said they have never got frustrated with me asking them to repeat themselves, they've always been very patient.

We've been using it in full production for about seven months.

Stability has been good. We've had one issue with the StarWind service locking up causing full sync to be performed. During this sync, there wasn't any noticeable performance impact by our users.

If you provide your own switches instead of doing their direct connect option you should be able to scale this solution very well. If you go direct connect you are limited to 3 nodes.  Adding additional storage should be easy if you have available hard drive bays.

Tech support has been fantastic. Always willing to help no matter what time of day/night.  I've never had to have an issue escalated as the first contact tech has always been able to solve any issues/questions.

This is my first venture into the HCA world.

StarWind performed most of the initial setup for us. We racked the equipment and then they remoted in and configured everything. We did not have any existing VMs to migrate so it was a simple setup.

Cost is very reasonable and shouldn't catch anyone off guard if you've looked at other HCA devices.

We also looked at Nutanix, HP Simplivity, VxRails, and Scale.

We are a small to mid-sized Eye Clinic that in 2015, had to upgrade our Patient Management & Billing system. Deciding to stick with our current vendor, we migrated to their “cloud” product, which is a hosted RDS Farm solution.

Our two-year experience on their “cloud” was coupled with numerous outages and continual slowness issues on a weekly basis. In 2017, we decided to bring the system back on-premises and so we began looking for a solution to run it along with our other virtual machines.

Fault-tolerance was the primary requirement in our search and having worked with VMware vSAN in the past, we knew that it would be a viable solution, albeit one that would exceed the budget. That's when we discovered the StarWind HyperConverged Appliance, a two-node highly available solution that fell within the allotted budget.

We purchased the StarWind solution and it ran flawlessly for two years, then in late 2019, the unthinkable happened. Our clinic caught fire and the building and all of its contents were destroyed. Knowing we had offsite backups, we just needed the hardware to restore our servers.

In contacting our StarWind account rep, they completely understood the circumstance we were in. They accelerated the order, build, and shipment of the new two-node appliance. As management worked on obtaining an alternate building to restore the service of treating our patients, the servers were delivered to my home so that the restoration process could begin.

The StarWind engineering and support staff were a tremendous help as they assisted in the restoration process. Knowing that StarWind will drop and do what’s needed to help a customer in dire straights has won us over as a faithful customer for life.

Thank you, StarWind!!!

Having a two-node, fully redundant host appliance solution that has been 100% reliable makes it easier to sleep at night.

In our experience with StarWind, the support has been by far the most valuable feature.

When we purchased the StarWind HyperConverged Appliances, they shipped with the Windows-based vSAN solution. Since then, they have released vSAN for vSphere, which is based on a Linux VM and would save us money as we would be able to get rid of the two Windows Server Licenses.

In the future, it would be nice to be able to migrate from the Windows vSAN to the Linux vSAN without having to do a full restore from backups.

We have been using the StarWind HyperConverged Appliance solution for four years.

We were running out of storage on our on-prem servers, so originally the HCAs were brought in to combat that and relieve some of the load on the veteran machines. Our file servers, along with one of our file storage, have moved to the HCA. I have put our Exchange server on it and the backup of the domain controller is on it as well.

We are using the latest version. We just implemented the HCAs. We added clusters and have moved some of the old virtual machines onto these new HCAs.

To have someone looking at the alerts when the network, or at least when the HCAs go down, this means I don't have to keep checking the clusters and virtual machines to make sure everything is playing ball. It's peace of mind that I don't have to keep checking and administrating that. Eventually, I will have a lot more use from it. I'm right at the end of the setup stage, but I'm still allocating resources from these HCAs into the virtual servers. So, I have not gotten the full run out of these yet.

I have seen improvement in my system’s performance. Our Exchange servers are behaving a lot better. Our system is a lot quicker. We were having delays before, where emails were taking two to three minutes. That is a lot longer than you would expect. Now, sitting on its own allocated HCA, it is almost instant. Therefore, email service has improved. The original use for this was just to increase our storage capacity, which it has done very nicely. I suppose we won't have to look for storage now for a long time.

The support is the most valuable feature. The support has been amazing. It's around the clock. One of our hard disks accidentally ejected without me knowing or being onsite. They called and told me about it before I had a chance to see it myself.

It has helped to increase redundancy and failover capabilities. The cluster is there, so I now have four levels of failover. If one of my machines goes down, there are two pairs of redundancy machines, so it fails over onto the next one.

The most important virtual servers have gone onto these new HCA. This is automatic so if one of these goes down, then the cluster would just take over and allocate to the next one. Even if I'm offsite, which I am quite a bit, we're still up and running.

The only real flaw that I have seen so far is this hard drive that was accidentally ejected because when it was received and added back into the RAID. There was an error there. It was not added back into the RAID correctly, so I have an outstanding hard disk. Apparently, a guy just knocked it with his hand as he was in my office, so it was just a small eject. He said that he didn't crash into anything. That is the only thing that has reared its head. The support team was straight on it. I have people coming out this week to replace it because remotely they couldn't add it back into the RAID. I think maybe the HD got corrupted.

I have all the ports I need in the back. When you're sitting them next to each other for replication between HCAs, it's quick because it has these dedicated iDRAC cables in the back. However, this means I can't have them in separate locations. We could run it through the network to replicate the regular gigabyte Ethernet, but that would be quite slow, especially with the setup. I don't really know how you would change this because I've got a large site. My original on-prem server is quite far away just in case there is a fire (or whatever), so the other one could pick up the redundancy. Having them next to each other defeats the purpose slightly if there was damage localized here, because I would lose both of them at the same time.

We have been using it for about three months now.

We did not install it straightaway. We were waiting for a couple of bits, so it was a late install.

The stability is good. I have had no downtime nor issues. You don't have to maintain it.

The only time I heard from the actual support was when that hard drive went down. As that was caused by a physical thing on our end, I can't really say that was a stability issue.

I sort of overbought on the storage needed for what I thought we would need in the future. The scalability is there. One of the main reasons I went with StarWind is because we can just keep adding. Possibly, in the future, our other sites will get added as well to have one centralized system. Though, I've not asked them about the specifics of what that would entail. But its scalability is definitely there, and hopefully, we won't need it for a long time. We might though as we have used a lot more data than I thought we would use so far.

As it stands, this is the setup that we will be using for a while.

They are great at monitoring.

The Proactive Premium Support has helped to free up an employee, as I'm the only one here at this company. It's a big company with a few schools attached, and obviously, my time is critical. I probably would've been knocking my head a lot longer than necessary, but Boris knew what he was doing and jumped straight in. We had a couple of hiccups and he knew what he was doing every time.

Transfer time was a big time saver when we were migrating the data server, because it was huge. Originally, it was only hooked up to the one gigabyte per second Ethernet going to the domain switch, then back. Because that would have taken forever, support talked me through how to do this another way, step-by-step.

I'm not 100 percent that we have the Proactive Premium Support. I'm fairly certain that we have the Proactive Premium Support, but it could be that I've just been dealing with the standard support. In which case, it's amazing. If it's the Proactive Premium Support, then it's great as well. It's around the clock, very friendly, and informative. While I've only spoken to Boris, he never seems to sleep.

It fits into our racks very nicely. Before, we had a couple of data modules which were plugged in. They were huge, bulky, and heavy. They didn't fit in the racks. This is the replacement to those data modules. It was by looking for an alternative that I got turned onto StarWind in the first place. StarWind’s support system, along with the way it plays nicely with Hyper-V and the existing setup, makes it nice and tidy. I've had no overheating. The fans have been nice and quiet as well. The ventilation is on point.

My reseller, Softcat, tipped me onto this solution. I asked them for data storage plugins and this is what they suggested. They were the one that turned me onto StarWind.

It's exactly what I was after when I started looking for these type of appliances.

The setup of the actual hardware was straightforward. Adding it to the existing network was complex. It would have taken me maybe a week of work to get the end result, instead having my hand held through the whole process was invaluable. It saved me a lot of time.

There was lots of different sessions involved with the deployment. If you put them altogether, it took probably a day as we had to stop and break. I had to go do other things and Boris also had to do other things, so we did the deployment in bits. 

The implementation strategy was loose. As long as it was off hours, so I could switch a bunch of machines off, that was essentially it. As long as I had this approved from Boris, that was our strategy. I looked at what resources we needed on which virtual machines. Then, I made the decision on what to transfer over, moving the most important things over.

I had Boris (from StarWind) for the setup, and he was amazing. We have the Proactive Premium Support, since we paid extra to get it. I probably wouldn't have been able to set it up on my own to get it to play with our existing network and on-prem setup. The support guys were sending me photographs and explaining some of the basics that I probably should have known. They have been great.

Kudos to Boris. He has been great, supportive, friendly, and dedicated. 

I am the only person using and maintaining the solution.

It's not really in place of anything that would be costing us. We just had to upgrade because the storage was basically kaput. Savings-wise, I don't think it will save us any money, but it's not going to cost us anything more either.

We might see ROI from time saved. But I'm the only employee, so it'll probably take awhile to cover enough of my time to make that money up.

I was quite hesitant to buy these, and I don't know why. There is a bit of a start-up cost. Having never used HCAs before, I was reluctant to buy it. I would suggest that you jump in and do it, as I wish I hadn't wasted so much time.

We did look at other options, just not HCAs. We looked at static storage to plug straight in.

I spoke to Softcat about alternatives, but they said StarWind was getting glowing reviews from very similar networks across education. So, I felt that I would give them a try. Their presentation was really good, and they seem friendly and very knowledgeable. Essentially, that's what I needed - someone to help me move through the process since I hadn't added HCAs before.

Compared to other solutions out there, StarWind was cost-effective. For example, we would have had to buy at minimum as much as these HCAs cost us going forward, if not more. 

The biggest lesson that I learned was I should have started as 1st Line Support. There was a situation where our old network manager had to leave quite suddenly, and there were definitely holes in my knowledge. So, I learned quite a lot just through the setup, Boris talking me through different types of connections, and some Hyper-V stuff. I suppose that I also learned a lot about HCAs in general and how they fit into network clusters since I hadn't touched on clusters before.

I would rate it a 10 (out of 10). I'm very happy. It's exactly the solution I wanted to the problem, then extra on top.

I'm a value-added reseller for Microsoft. I do some other stuff on these HCAs too, but that's the easiest way to describe it. 

I'm providing a remote workspace for a special, select subgroup of clients who are running a pretty specific product called Infor. I'm pretty experienced with hosting and supporting this particular product, so I decided to also wrap a value-added reselling business around it so that I could give them a full remote workspace, instead of just support for their product.

We're running virtualized workloads for 300 or 400 users at this point. Our goal is to have them log in every day in and run all of their day-to-day work on these virtualized workloads.

The solution has probably saved me 100 hours of implementation work. 

In terms of support, we're probably on the low end of requirements because we don't have a lot of advanced stuff going on. We just have virtualized workloads, so once they're configured they're done. But we've had a couple of longer support cases, and over the course of a month, it has saved me, on average, six to eight hours. That's as a one-man shop. If we grow and we start adding more HCAs, I imagine that that time saved increases pretty linearly. The support is really a convenience. I could always schedule my own time to take care of issues, but if there's a minor storage or networking issue, it's nice to bring someone in. 

The major way it has changed our organization is that we came from a four-node, pure Microsoft setup, where we were using Storage Spaces Direct. StarWind is able to run on two nodes, so the hardware cost is quite a bit lower. They include support, so I don't need to keep someone on call in order to handle storage issues. And the fact that they were able to over-spec us for a reasonable price has meant that, over the past six months, I haven't had to worry about overhead and I haven't had to worry about budgeting any more systems. We have enough headspace to expand another 50 percent or so before I'll ever need to invest in direct processing hardware again. And when I do decide to invest more in hardware, I'm perfectly confident that they would just ship us a ready-to-go unit that can be plugged in with three cables and it's off and running.

I have burned a lot of time in the past configuring stuff like this myself, so the ability to pay a little bit of extra money to have something like this delivered, where all of the failovers are already configured, and all of the converged storage is already configured, and it's really just a blank slate to start building Hyper-V workloads on, is valuable. The fact that it's preconfigured and that there is a high level of support, so that I don't need to hire someone in order to do all this, has been my favorite feature.

Also, the hardware footprint is great. We've got two 2U servers which replaced four 2U servers. Granted, they were about three years old at that point, but we actually increased our processing capacity by about 50 percent while keeping our storage capacity about the same. We've actually been able to downgrade to a half rack from a full rack because we've gotten rid of some of our network equipment and some of our additional storage arrays. And the fact that that's all contained within 4Us of space is a complete 180 from the strategy we had before, which was four processing units and a few storage arrays. It's cut down on the amount of cabling we have to deal with by about 80 percent, so it's been a pretty big deal for the data center on the physical side of things.

The improved performance has scaled pretty well with the cost. I wouldn't say that the cost of performance is significantly lower. The main benefit is the cost of configuration and ongoing support. We're probably not saving a significant amount on hardware costs, but if I'm saving some 50 percent of my troubleshooting and hardware support time, we're probably saving, as a rough ballpark figure, $10,000 a year. If I were to hire even a part-time person to take care of just the hardware stuff that I'm now not having to take care of, it would be well over $10,000 a year to have a hardware architect available.

In addition, StarWind HCA has increased redundancy for us. Early on, just a couple of months into the tenancy, we had a pretty major hardware issue with one of the hosts, to the point where it was rebooting a few times a day. That was actually all Dell EMC's fault and had nothing to do with StarWind. Even with that host going up and down several times a day, there was only a little bit of inconvenience during the lag time when a live migration occurred from one server to the other, and we were up and running that entire time. We didn't incur any direct downtime over the course of a week-and-a-half where, literally, 50 percent of our processing units were going down three or four times a day. As frustrating as that experience was, it really helped strengthen my faith in StarWind solutions.

That situation, where Dell EMC servers were going down, has been my only real difficulty. I do understand that we were using refurbished Dell EMC hardware, so that may have played into the difficulties we were having. But at the end of the day, it ended up being something that the wider audience of Dell EMC was actually aware of as an issue. Neither the StarWind technicians nor the Dell EMC technicians were able to actually identify that problem sooner than a week or so. I found after, doing my own diagnosis and my own technician work, that there was actually a solution out there that many people Dell EMC's forums were aware of. The communication between Dell EMC support and StarWind support, in that particular scenario, left something to be desired, for me. 

I did express those concerns to StarWind and they were very responsive to that. They seem to really appreciate the feedback. I'm hoping that there has been a change that has already been enacted by them as a result.

We installed in March of this year, so we're relatively new. I believe we got refurbished, seventh-generation HCAs.

The stability has been great, with the exception of that one issue I mentioned which seemed to be Dell EMC hardware-specific. That even spoke to StarWind's stability in the sense that we had one host going down regularly without downtime.

We've had zero issues directly caused by StarWind. Everything is contained within the VM guests. Those are just configuration and Windows Server problems. This is definitely the most stable hardware we've had, and I've been involved in this business for eight years, on various stages of hardware. These past six months have been the lowest in terms of overhead so far.

The scalability seems really good. I haven't hit the need for scalability yet, but it seems to scale pretty linearly with the exception of storage. 

The idea is that all the storage is needed between all the hosts. So if we needed to increase our processing capacity, that would scale perfectly linearly. We would spend another X dollars to increase our capacity by 50 percent with an identical server.

I haven't explored storage capacity yet because we're a pretty low-storage-capacity company. But it seems like, with their additional products that aren't HCAs, their storage arrays, that you would be able to increase storage capacity on level with your costs as well. So you're not incurring a lot of overhead for interconnectivity or additional redundancy. At least that's my impression.

At the moment we're probably at 60 or 80 percent capacity across the board in all system resources, including networking. It's a really even 60 or 80 percent. If we can grow the business by another half next year, we'll be at 100 percent capacity. At that point, it would start making a lot of sense to look at adding another host because, if one fails and we have to fail over, we would effectively need to throttle everyone backed by 50 percent.

We don't use the proactive part of support a whole lot but that's really because we're a very simple setup at the moment. They've come to me a couple of times when they noticed some things going wrong, but that's usually when I'm in there reconfiguring things or rebooting servers. When our proactive support expires we'll probably renew because of the fact that they've been really on top of issues, whether or not I've already been aware of them. 

The part where support has really saved a lot of time is not really directly due to the proactive part of it. It has had to do with the fact that when I do need help, if storage is running slower, or if I see that there's some kind of memory-usage issue on the hosts, they're usually back to me in probably half an hour, at the very most, with a solution.

The main thing I've enjoyed from them is the really fast response when I do need help with reconfiguring or the like. I actually just reached out last week to try and make some networking changes. I got a response in about five minutes and I had an actual solution, with an advanced-tech ready to help me, within about 30 minutes. I don't know if that has anything to do with the proactive part of their support but I would imagine — putting myself in their shoes — that having a customer who is part of proactive support probably accelerates their response a little bit.

I've been really impressed with StarWind so far. They've been really helpful.

I haven't had to talk to StarWind at all for about a month. The last thing was a major networking upgrade request and I was really pleased with their response time. From a small-shop perspective, this is probably the best experience I've ever had in terms of the backing hardware for the services we provide. It's been very nice.

The solution this replaced was all home-brewed. It was all running on a Windows Server. We had a backplane connected to a few different storage area network arrays. It worked well but it incurred quite a bit of overhead just to manage it. If you've ever heard of people working with just Microsoft Failover Cluster Manager with backplanes, it was a bear, both to physically connect and to manage.

The concept of an HCA was actually kind of new to me, at the time. We had been under the practice of putting processing and volatile memory on one box and putting all of our storage into other boxes. That introduced some issues with single points of failure: If your switch fails then your storage is done and if your network switch fails then your communication is done.

I had started researching Microsoft Storage Spaces Direct, which I believe was a new feature in 2016. StarWind must have a lot of search engine optimization related to Storage Spaces Direct, because they ended up coming up, really early, as an alternative. They're very active on Spiceworks and they were constantly in threads about Storage Spaces and putting their product out there. I ended up researching them and the total cost of ownership, hardware-wise, was possibly a little bit higher than bringing up your own, but the fact that support and configuration were included in that price, made it a slam-dunk for us.

The implementation was fairly simple.

I had a really big, heavy pair of Dell EMC server boxes delivered to my workplace. I had to schedule some time to go physically into the data center, which is hosted two miles away from my office. The entire installation procedure was really a matter of unbox, throw the rails in, throw the servers on the rails. Each server then needed two power cords and two SFP connections between the servers themselves. And, bare minimum, they need one management connection to whatever your local Cat 5 switch is. That was it. That was really all that that needed to be configured, hardware-wise. 

Once those were up and running, we spent maybe 45 minutes just getting the initial Hyper-V configuration done, and I was off and running. I was able to create and migrate VMs at will. No downtime, no reconfiguration, and literally nothing else.

All together it took about two hours for completely setting up the hardware and getting Hyper-V ready to create guests.

We didn't have an implementation plan. Physically, we had room in our racks and spaces for the power supplies and the cables. The only planning was that I gave StarWind a half-day's heads-up that I was going to get everything installed. They were on the phone and on a remote support session at pretty much the minute that I was ready to do the software side of things.

I enlisted some help to get things physically installed. Once that was done, it was just me and one StarWind engineer. We had to be on the phone for about an hour in total over that entire process. It was just me and that one person. They seem to have their process petty down pat. He was flying through the configuration and I was just sitting in the back seat watching.

We haven't seen ROI yet because we're a pretty low-sales company. We're just sticking with who we have at the moment because we need some more people who are experienced with this Infor product in order to grow the business much. I would expect that we will break even with our hardware investment within the first quarter of the coming year.

That's not bad at all because that will end up being almost right at the one-year mark. Even if we had to throw those servers in the trash at that point we would be at zero loss.

In terms of the hardware pricing, we ended up going with refurbished machines because we're not in quite as critical a situation as other service providers may be. The pricing is pretty comparable between StarWind and other solutions, if you're just talking about hardware and a general support plan. The value starts to come back in a very real way with StarWind when you talk about the reliability of both the hardware and the support structure itself.

Our entire package was around $35,000 for everything, including three years of support.

We evaluated other options and, overall, the thing that made us go with StarWind was really the community involvement, mostly on Spiceworks. They're on Reddit too. Seeing how active they were in proactive troubleshooting and in answering sales questions for whoever was asking was a big deal. The fact they had extra manpower to handle that kind of stuff speaks really well to how efficient their support structure is.

Look long and hard at your current hardware. There is a significant utility in sticking with a single vendor for stuff like this. If you are at that point where you need to refresh pretty much your entire environment, or a significant portion of it, I would say you should seriously look at StarWind because they would potentially be able to take care of just about everything, hardware-wise, as long as you're a small enough shop and you're ready to really commit.

Up until implementation, in March of this year, we were very reliant on ourselves and sub-contractors to support the hardware configuration and make sure everything was up and running. We had to be super-proactive about being on top of Microsoft issues because anything that is 100 percent reliant on Microsoft can go completely haywire if the wrong Windows Update runs. So the biggest change, and the biggest thing that we learned, is that it's nice to be able to rely on an external company, as long as they know what they're doing. We've been able to call StarWind for anything to do with the framework we're built on or anything to do with the substrate that Hyper-V is running on, no matter what happens, and know they're going to take care of it.

I'm the only one dealing with administration or maintenance of the HCA and it will probably stay that way, just for security concerns. It's a lot easier to stay compliant if I'm the only person that can do any of that. We do subcontract to other people for support of our customer VMs, but that's a whole different game. That's all built on the StarWind framework.

StarWind is an easy 10 out of 10.