How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
We are using VSAN in our private cloud environment to provide highly redundant CSVs to a Hyper-V Cluster. We are using a converged environment so we have two commodity grade servers setup as a highly available StarWind cluster, then we have numerous Hyper-V compute nodes which access CSVs from the StarWind cluster. We are able to use Veeam to backup and replicate the VM files from the CSV/cluster. We use off the shelf 10 GbE SPF+ modules and off the shelf 10 GbE switches. With MPIO, we were able to create a redundant network infrastructure to support our SAN network.
We needed to deploy the new infrastructure in our new data center as soon as possible. As a reliable, fault-tolerant storage, we chose StarWind solution. I took two old Supermicro servers and installed them in RAID controllers and SSD drives, then installed Windows Server 2012 R2 with the Hyper-V role. Then, I made StarWind the two-node iSCSI target. The servers were connected to the VMware cluster via the iSCSI 10 GbE interfaces. The storage showed very good speed results with SQL databases, file servers, and MS Exchange, which completely satisfied us.
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 have a fault-tolerant infrastructure, consisting of two storage nodes hosting the VM's storage and two Hyper-V nodes.
Our company, an IT integrator in Ukraine, conducted a pilot deployment of five two-node Hyper-V failover clusters with CSV build with VSAN for Microsoft Hyper-V. Each cluster consisted of only two hardware nodes with redundant 10Gb/s direct DAC links (no switch) and 1Gb/s uplinks. After four months of testing, we have no doubt in using this exact solution in our customer’s production environment. We are going to deploy three similar installations this year. Also, we are planning to test the new VSAN for VMware vSphere.
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.
We have set up a dual StarWind SAN with a fault-tolerant volume for our critical virtual servers in addition to some non-fault-tolerant volumes for less critical virtual servers in both our corporate HQ and one of our large divisions. The corporate site is using Hyper-V and the other division using VMware ESX. Between the two sites we have 15+ physical servers with over 150 VMs running. Our corporate site uses Dell servers w/SAS drives for the two StarWind nodes and the division site built two white box type servers using NAS-specific SATA drives. Both solutions have been outstanding.
This solution provides us with high availability and failover with fault tolerance across two nodes. Implementing a highly available environment made way more sense to our company using StarWind’s Virtual SAN than other SAN or virtual SAN solutions we looked into over the past few months.
We tried StarWind because the other solutions we tried were not doing enough, and the performance of this solution was very good. The price is cheaper than other solutions. The physical server was very useful to set up a designer virtual server.
We needed a SAN to support our environment comprised at the time of two Hyper-V 2012 Clusters. We're now migrating to Hyper-V 2019 and we had no issues with the migration from the storage. We use SATA NL and SSD to give our VMs different performance tiers. Update: We finished the migration and moved all storage iSCSI comms to Mellanox. We have had 0 issues with Starwind.
I started using this product when I had challenges with failover as one of the requirements for my client. I had to deploy the failover environment but the challenge was mirroring of the servers. Now that I have implemented StarWind, everything is running perfectly.
StarWind VSAN software was easily deployed on the commodity hardware and integrated into the existing IT infrastructure. We have used in HyperConvergence and Citrix XenServer installations without any problem. With our customized hardware, we have very good IOPS and throughput.
The solution provided me the ability to share storage between three physical VMware hosts in my environment. Hence, I have HA for my VMs to move across hosts once they are stored on the vSAN using VMotion. Moreover, I am able to utilize the storage I already have on servers and save the expense of purchasing a new storage appliance.
We use this solution for a High-Availability cluster for Hyper-V on two nodes. We are running on Windows Server 2016.
We were looking for a Microsoft Windows 2016 Hyper-V clustered solution that didn't require an external SAN network. Something that could utilize the local storage on each server, and also allowed us to configure the storage as we required it. We had looked at Storage Spaces Direct, but it was too restrictive in terms of configuration.
We use VMware ESXi and needed a SAN replacement. Our old SAN is an HPE StoreVirtual VSA, but we are running out of space and it's getting old, so our support will be ending soon. We will use the storage for our main cluster including OS and data drives.
We had to build a highly available Hyper-V cluster. As I work for a charitable organization, the most important part is keeping costs as low as possible. I have looked into a few solutions and none was as easy to deploy because it allows us to use hardware that we already have and not invest a lot of money.
I used their Virtual SAN software to add new SANs to my VMware environment. I began working for a company that had a Virtual Environment already in place and there was no documentation regarding the configuration of the system. The storage was not managed correctly and I had to find a way to make space with what hardware I had at the time.
We use 2-Node software-defined storage clusters with iSCSI access to 30 TB in HA-targets, and 140 TB in flat targets. Our environment includes eight vSphere hosts and more than one hundred Windows VMs (file servers, MS SQL servers, Oracle Database servers, MS Exchange servers, etc.) are connected to StarWind's iSCSI targets.
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 use this solution for SAN storage. We have a two-node Microsoft Windows 2016 full SSD (SATA) configuration with RAM cache (500GB each node), and iSCSI to connect HA virtual clusters. Using Mellanox network technology with two 100Gbit switches in HA mode. Also, we have more than sixty MSSQL databases hosted.
We are using a two-node StarWind VSAN cluster on a Dell 720xds. The StarWind VSAN helps us to better leverage the computing power of our ESXi hosts and helped solve the problem of expanding local storage.
Our primary use case is for a distributed virtual SAN over two data centers. Virtual SAN uses three servers in two data centers.
Our primary use case is to create vSAN for a small business environment and to manage it without using a physical SAN.
Our primary use case is data storage. It has helped us to make better strategical decisions, work safely and quickly.
Our primary use case is as a virtual storage area network for server clusters and file storage in a production environment for our company.
Our primary use case for this product is to obtain high availability for our file servers under the control of the Microsoft Windows 2008 operating system.
StarWind VSAN is used as shared storage for our Hyper-V cluster. We have two nodes, HDDs in RAID 10. HPE ProLiant servers, Windows Server 2016.
StarWind is cost effective. There's no need to purchase additional hardware as shared storage. They have great technical support.
Before, we used a cluster of two Windows servers with shared storage system on a single SAN. One of them was a working clustered SQL server with database mirroring. Every part of the system was redundant except for SAN. It was almost satisfying. Every cluster server system we know needs shared storage system. The cluster could be fully redundant, but this redundancy is worth nothing without a redundant storage system. We had a single SAN system. As a single system, SAN was not redundant. But we needed a redundant storage system. We always were afraid that once upon a time our SAN will stop to work. We, of course, had backups, but it was not enough. What we needed was the system with no data loss in case of issues and with no interruption (or only several seconds of interruption) in data processing. We were looking for a relatively simple and not very expensive solution. Why have we selected StarWind among other storage solutions? Actually, I don’t know why. Simply, I was looking for a solution using Google. StarWind was the first system I found that gave me hope. When I did some tests with StarWind, I stopped looking for anything more.
We are a gold mining partnership in Malartic, Québec where we are working 24 hours a day and seven days a week. About 1500 people are on our sites, 900 user computers and 100 different virtual servers run to maintain the production area. Single point of failure, no real-time synchronization with our disaster recovery site, and we are unable to make updates and upgrades without any cuts on the production infrastructure.
The use of the StarWind solution does not have to be just a strictly IT domain. In my case, we needed to find and implement a solution that guaranteed the supervision of security systems in the scenario of a full disaster of our main center of supervision. To achieve that, we needed to use technology that would give us fast and reliable data replication between two supervision centers and would not ruin our security department budget. On the other hand, the solution must be easy to administrate with the tools we had. StarWind Virtual SAN was a bulls-eye. Now, we can transfer the full spectrum of information to remote infrastructure that allows us to ensure continuity, which means better security for the company. The StarWind Virtual SAN management console is intuitive and easy to use.
In our organization, we use this software for the first year. It is used to work with backup data storage. Still, it never lets us down, and we never lost our data.
We're using it in our DR site for replicating virtual machines from a primary site. We needed a solution that took up less rack space, so we went with something that converged infrastructure. It's providing storage for our virtual platform.
We have two StarWind VSAN nodes installed in a small company. We're mirroring these nodes where all services are installed.
We use StarWind for multiple 2-node hyperconverged Hyper-V Windows clusters in our datacenter environment.
We needed to consolidate our physical servers, so we went with the StarWind cluster to virtualize our servers.
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.
The primary use case is backup storage for our VM servers.
We use it for data redundancy and failover.
The primary use case is to provide a virtual storage for our data and virtual machines. Not having a budget for a physical SAN, we use what we have to get the best of what we have, this is primary reason for using this VSAN.
StarWind is the highly redundant storage solution for our company-wide hardware agnostic Hyper-V environment.
We had decentralized storage, inefficient storage and computer utilization, non-utilization of VMware vSphere advanced features like HA, FT, vMotion which require shared storage like StarWind.
* I've used StarWind VSAN for replicating vSphere datastores and in Microsoft SQL and file systems clusters. * I used one in mission-critical systems like a call center, SQL, SharePoint, etc.
Started with a trial and then moved to the paid version. I have a 3 node cluster, (20) 1TB spinning drives, RAID 0, (3) 800 GB SSD drives, RAID 5 and 18GB RAM cache per node. Using 10G Infiniband for the iSCSI & SYNC network loops. This is to support local disks of VMware Horizon View full clone desktops.
StarWind VSAN eliminates the NAS/SAN as a single point of failure. It's an affordable synchronous HA storage solution which allows us to use extremely fast direct-attached SSD storage in an HA environment.
I use StarWind Virtual SAN software to change our old HPE Fibre Channel storage into an iSCSI solution for our development environment.
Replicated, high availability storage for VMware vSphere cluster of VMware ESX 2-nodes in an HA cluster for Virtual SAN storage, only this software can do a 2-node cluster.
To give us the ability to install a cluster environment, increasing reliability for our plant infrastructure.
StarWind is used as the primary storage for three VMware hosts. It is running as a two node cluster for HA.
Our primary use case of this solution is the deployment of a highly-available Microsoft Hyper-V environment. Using the StarWind Virtual SAN product allowed us to deploy a Hyper-V cluster that provides uninterrupted failover between nodes that would have otherwise not been possible. Additionally, we have implemented the same redundancy on our dedicated file storage systems.
We use StarWind vSAN software storage solutions to run two hypervisors in an HA clustered environment.
I've used StarWind Virtual SAN software in two different solutions for several years. Both were highly critical production environments requiring 100% uptime and fast performance. In both solutions, this platform satisfied those requirements.
We use StarWind for storage on our Hyper-V cluster. We started with their free offering in a test environment and found the performance and stability so attractive that we built a three node cluster using Dell 720s and ten gigabit copper ethernet. It has now been running continuously for four years with essentially zero downtime. As it approaches end-of-life we will be migrating to their managed appliances.