How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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!!!
We use it for virtualization related to development. We have two entities in our company. One is corporate, a subcontractor for NASA. And the other one is an electronic timesheet system. For the corporate side, it's mainly a file server. And we use StarWind HCA for development of the electronic timesheet system. It provides us VMs and tools.
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.
What we use it for is resilience in our Hyper-V cluster, for both the guests and the data. We have two appliances split between two physical comms rooms onsite. If we lost the power or network to one comms room, all of the guests and all of the data residing in the second comms room would be dynamically available.
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.
I'm a self-employed consultant and I'm currently an interim CTO at one of the largest flour companies in the Netherlands. Here, I have introduced the latest solution of StarWind, the hyperconverged hardware cluster. In the past, it was all software-based. But now I use their latest solution, including hardware. The primary use case is all on-premise. An ERP system is running on it as are a VDI solution and a terminal server, and it is all based on a Hyper-V virtual environment. The complete IT infrastructure is running on the StarWind cluster. The company has about 200 employees.
We use it to replace some Hyper-V infrastructure. We are looking for some decomplication, hopefully. Our old Hyper-V cluster was three Dell R410 servers with two Cisco switches that were connected by iSCSI to VNX. The VNX was coming toward end-of-life. I've de-cabled it now and taken out the rack and I've got a box of Ethernet cables. There was a massive amount of stuff that did the same job as two servers and a couple of Mellanox cards. Although it was end-of-life, we got some quite severe warning emails from EMC saying, "This is it guys. Your support is terminating. If anything goes wrong with it, good luck." We could have purchased a third-party warranty on it if we'd wished, but then it would have been a matter of luck in terms of the parts. Although nothing ever actually went wrong on the VNX, hardware-wise, it was about not having that parachute.
We've got a two-node, Hyper-V cluster for high-availability. We have it running on Windows Server 2016. It's being used for file servers, database servers, application servers; all on-premise, private cloud-type services.
We run it mostly for business processes. We have a manufacturing plant. We use it for our ERP system, some of our databases, some IT applications. It really drives the organization and the main things we use on a day-to-day basis.
I wanted something for high-availability. We're a logistics company and we have guys working 24/7, to some degree. I needed a solution that was going to provide high-availability. It's all on-prem. It's the two-node, high-availability model.
We are using the system to run our various virtual machines in a Hyper-V cluster. They run services such as SQL Servers, our Skype for Business phone system, some financial applications, various domain services, and SharePoint servers, among other miscellaneous systems. We use StarWind’s HyperConverged Appliance in one of our server rooms and plan on upgrading more legacy equipment at another location next year. We have it set up as a Microsoft Hyper-V private cloud.
We are currently using StarWind HCA to build out a flexible, distributed storage system. We had a myriad of file, application, and database servers that ranged from physical to virtual. StarWind helped us consolidate and make the necessary physical to virtual server moves (P2V), and the entire process was very pleasant. This system also allows us to achieve high availability (HA) across the entire IT infrastructure that we are responsible for, which was a major driving decision. This was all completed at an affordable price point for an SMB, which was also a key element for an NPO.
We had to replace an aging and complex infrastructure. We did so with the hyper-converged appliances from StarWind.
We had non-virtualized and old infrastructure that needed to be upgraded. We use HCA for all of our servers.
We used to have four Dell EMC PowerEdge hosts running various versions of Microsoft Hyper-V with no redundancy. We are also running out of storage space and have been dealing with an increasing complexity of Windows Server licensing. We investigated and received proposals from three vendors (Dell EMC, Scale Computing and StarWind). Ultimately, the main decision point was cost. StarWind is the only vendor that only needs two nodes to set up the cluster. Not only have we saved on the extra node, but we also don't have to license another Windows Server Datacenter edition. Our StarWind HCA has been in production over 12 months, and we have had no issues or single downtime so far.
Before implementing the StarWind solution, we had standalone servers with Hyper-V on top. With this IT infrastructure, there was no fast and easy way to restore virtual machines (VMs) from backup if a Hyper-V host failed. The process and time it took to restore the VMs from backup were long and tedious. Moreover, there were no constant availability of applications and the necessary protection of the agency’s data. We required a solution with the help of which it would be possible to build a highly available (HA) and fault-tolerant (FT) IT environment at a price affordable for a ROBO’s budget.
We are a small school with 700 users. We replaced an eight-year-old HP system (two HP DL360 G7s and an HP StorageWorks X1600) with a two-node HCA cluster.
Our small business was looking for a reliable and cost effective solution to ensure maximum uptime. We went from a single server to a virtualized hyper-converged infrastructure to allow routine maintenance at our convenience and have peace of mind that a failover system was in place.