VMware vSAN Reviews

We usually use it for any workload virtualization, data center virtualization, and storage. We use it for our software-defined storage and when a customer needs scalable storage. Data center modernization is also a use case for it.

I am using its latest version.

The scalability of the solution is most valuable.

They can improve the manageability of the solution to make it more simple. It is not that complicated, but it will be good if they can make it more simple.

I have been using this solution for almost three years.

It is stable, and its performance is very good.

It is really scalable. We have five to six administrators and implementers who work with this solution.

They are supportive. They are good in their support.

In my previous company, I worked with Nutanix. In my current company, I'm working with vSAN. Nutanix is much simpler from an interface point of view. vSAN, as a part of VMware, has more maturity in terms of features and software-defined data center journey. VMware is more mature than Nutanix in this area.

It is straightforward. It took two to three days.

In terms of maintenance, it requires the usual day-to-day maintenance. It sometimes requires some kind of support.

We installed it ourselves.

It is not that expensive, and it is not even cheap. If it is designed in a proper way, it has good pricing, but if you do oversizing, the price will be high. There are different licensing models.

I would advise others to do proper sizing and look at the features that they want to include or not include. They need to first understand their business needs and then do the sizing. This way they will get a good solution.

I would rate VMware vSAN a nine out of 10.

In our model, the price of vSAN storage space is a bit lower than SATA-based storage space from other storages, and vSAN usually has better characteristics (IOPS + latency).

We can easily scale up our vSAN cluster horizontally. All we need is to buy the same hardware nodes and put them in racks.

vSAN has better integration with virtualization than any other datastore.

Stretched All Flash vSAN is the leading product to build a disaster recovery solution. We have a plan to build it in near future.

It’s simple: We are service provider and if a solution can give us new opportunities, it is a good solution. We can build economically effective IaaS clusters on top of vSAN.

vSAN is very complex inside. For example, you need to have a plan for any emergency situation, beginning from the PoC stage; how you monitor SSD and HDD; how you change them. It looks simple, but you cannot just remove a broken component and an install new one. Under the vSAN layer, you need many accurate steps to make these simple actions.

And when you operate a big environment, you need to have more tools to control the health of the solution, to troubleshoot issues and so on. VMware has improved this side from 5.5 to 6.5, and there’s still room for it.

vSAN is not a hardware-agnostic product. We would like to have more compatible SAS controllers and other components in the market. There is room for improvement for both hardware vendors and for VMware.

On the other hand, vSAN is a production-ready solution and all these possible improvements are cosmetic issues.

We have used it from the vSAN 5.5 release date, more than two years.

We use VMware vSAN 5.5 with the latest updates in our products.
The first product is a B2B sector solution, CloudLine, and we sell space on vSAN as one of the storage tiers.
The second one is our B2C solution, CloudLite.ru. It looks like Digital Ocean – we sell IaaS to retail customers in the mass market.
We have plans to build new clusters using vSAN 6.5.

We have encountered stability issues. We had run many tests with vSAN before production. To avoid any issues with vSAN stability, one needs HCL hardware and compatible BIOS drivers for each of the components. The crucial part is that you need HBA without RAID and with disk pass-through, which is important. Finally, you need strong network expertise and a solid network.

We have not encountered any scalability issues; you can scale vSAN horizontally without any issues. But you need to start from 5 (!) nodes; not 3 or 4. It’s a long story – why? :)

Rating technical support is not a simple question. VMware has great technical experts at level 2 and 3, and they are always available if you have severity 1 issue. Technical support is not so good for minor issues.

Previously we use traditional datastores - NetApp, EMC, IBM. And we continue to use it.

Initially, you need to have enough expertise. You need to read some popular bloggers and select hardware from “recommended nodes”. And then you can start a PoC.

We are part of the VMware vCAN program, so our licensing is different from the retail model and it’s comfortable for us.

We keep an eye on all solutions that come to the market. We have tested SimpliVity and Nutanix. We use MS Storage Spaces in our production. All these products have their pros and cons.

You need to use it for the reason of economical efficiency. It’s one of VMware’s great products.

vSAN is a great product, and we see improvement from 5.5 to 6 and 6.5.

The main thing is the comprehensive data center management type of features. The overall management dashboard, capability to have multiple clusters, link clones, distributed computing, where you have vCenters in different geographies. Site Recovery Manager for failover, VSAN for storage, and again the EVO:RAIL mechanism combining with the type of VSAN architecture that is out there, and previously, the automation capabilities of vCloud Automation Center. Previously, I had experience with vCloud Director, but obviously everything's being transported onto vCloud Automation Center now.

The biggest benefit is cost, so for someone looking to deploy low cost storage, but something that integrates with their virtualization architecture. It's a very good fit for smaller companies who have multiple nodes, and can leverage commodity hardware to go with that. VSAN, by its architecture itself, has inbuilt features for reliability, for load balancing. You could enable VCRE cache, along with VSAN, so it works and integrates with a lot of other VMware technologies.

I would love to see VSAN transform into an EVO:RAIL-type of technology, but EVO:RAIL has a separate use-case. I think it's not meant for all companies either. VSAN does serve that purpose, and kind of addresses the primary need there. At the same time, EVO:RAIL is limited to certain hardware manufacturers and some providers who are kind of combining everything into one package and selling it off. Whereas, customers like to use commodity hardware, like to use regular software, and do things their own way. So, if VSAN continues to offer that flexibility, which it does today, I think there's great significance for it. If it integrates with replication and SRM, that takes it in a really good fashion, right to the area where it can be heavily adopted.

I have experience, personally, as a VMUG leader and as a vExpert in the areas of vSphere 6, SRM, I've tested VSAN in my home lab. I have worked with replication technologies. Done a little bit of vCloud Automation Center as well, and vCloud director.

I personally consider VSAN to be a very stable product. Obviously you have to have a minimum of four nodes, to say that, the minimum spec is for three nodes, but if you have 4 nodes or higher for VSAN, it is a very stable product.

It's all about adding nodes, and the number of drives to it. VSAN is very scalable. I was able to, just for a lab purpose, scale it up to 10 terabytes, and I started off at four, so it tells you that it was easier to scale from 4 to 10 terabytes, and the same mechanisms I've read online reviews and some white papers around it, it goes up to quite a few hundred terabytes.

Very straightforward, you need to obviously follow the configuration guide, read advance, just so that you understand the components around VSAN. Then it was just a matter of enabling VSAN, provisioning all the data storage that it needs. You obviously need to have a Solid State Drive to go with it, so many people don't realize that, but you should have one. That is to allow the performance that is required from commodity hardware to be scaled up.

For our VMUG group, I was trying to set up a lab, and I tried to go with the VSAN for storage purposes. It's a very rock solid product, very robust. Compared to the previous iterations it is very flexible and very strong now. It was a breeze to set up, it didn't take time. The reliability of VSAN is really good, I was able to set it up at four nodes and I purposely took out one node just to see what happens, and it just kept working fine.

Looking at VSAN or a different solution, it depends on the use-case really. Someone looking for Oracle database set up on ASN, is not going to first think of VSAN, but, if you design VSAN the right way, it can host Oracle databases. It's just a matter of how much compute you throw at it, how much storage power you throw at it, and how you design the pool. If you have done things the right way and you have sufficient cache, and you have sufficient Solid State, I think it can be a really good use-case for many different organizations.

It offers a lot of scalability to customers. People looking to scale up in terms of nodes when they need it, it's a perfect fit for it.

The purpose of vSAN is to cluster nodes and distribute storage usage. Like, if a server has ten hard disks, for example, and the main server also has ten hard disks, and the two other nodes or servers each have ten hard disks as well, then it will combine them all. Once combined, it becomes clustered. That's the reason why most clients want to use vSAN - to save on external storage and use the internal storage for the VMware environment.

vSAN that has been most effective in streamlining storage operations.

For data recovery alerts, it uses tools like snapshots and vMotion.

Overall, the features I find most valuable are related to the reliability and availability of the servers.

vSAN is the fastest in regards to creating VMs and connecting them to virtual networks. It compresses data, and if you have a physical server form factor, it fits only on one cluster node. That's why we use vSAN.

Better options would be clustered nodes, or even cloud configuration.

There is room for improvement in cloud configuration, we typically do web browsing for management. So, when we configure or manage VMs or vSAN, we usually open a browser and use VMware credentials. That's what we call cloud configuration.

We have been dealing with it since 2016. And since that year, we've been a distributor.

Stability depends on the network. Some clients use networks with slow switches. Here, we're using ten gig to twenty-five gig. So, more often, it's the fastest network connectivity. But if the client is using one gig or ten Mbps. Some smaller companies face issues with a slow network.

When it comes to scale up or scale out, it means that the servers or the clustered nodes can be added, or another cluster can be installed to increase the resources of the clustered nodes.

The customer service and support are quite good. 

Positive

The deployment process is complex because it's a GUI infrastructure. There are two-ways configurations for the nodes or vSAN setup. You can do it on a GUI management interface or by console or CRM recommendation.

So, it could take half a day or a whole day.

It is sort of difficult to maintain without any training. If you don't have any ideas on maintaining, then it could be difficult. But if you're a master of VMware, you know how to handle it. You're already a professional and can easily handle it.

Overall, I would rate the solution a ten out of ten. 

We mainly use vSAN for two purposes. One is to improve application performance with the HCI. The second is to migrate customers from legacy storage to high-speed SSD-based infrastructure. They are moving the computer network and storage capacity together. 

The vSAN features we've found most helpful are live application migrations and storage policies. It has storage, policies, application, and DRS policies. Automation is there. 

Also, if a customer wants to go for a VMware stack, vSAN has flexible, completely integrated solutions for two clouds. Stretched Cluster, vMotion, VXLAN—there are so many features. 

We are an IT solution provider, and we've been using VMware for 15 years. 

I would say vSAN is stable. 

Once you develop all three of your stacks, you can plug in the rack servers and all. If you are increasing in parallel, vSAN automatically increases the overall computing capacity of the IT infrastructure in terms of network storage and what you can compute.

Technical support is also good. I would rate VMware support eight out of 10 because nobody is perfect.

Setting up vSAN isn't too tricky. All HCI providers—Microsoft, Cisco, and VMware—have very smooth implementation except for Microsoft storage, which is complex. 

Maintenance is required. Sometimes hard disks crash, but thanks to the mobility and abstraction of the software from the hardware, we can migrate the entire infrastructure layer to some spare PC's main server and perform maintenance. This is the standard patching practice in the industry.

The pricing model is sometimes a challenge for us because their licenses are very costly.

I rate VMware vSAN nine out of 10. I am a VMware fanatic. As a solution architect, I've designed solutions for many customers. Clients have personal preferences, and they're generally swayed by what the vendors tell them, but my perspective is purely technical. If you are going for features, scalability, and performance, VMware is the best solution. 

It's not dependent on any vendor. The VMware layer is there, and VMware is required, but it saves a lot of costs and provides flexibility. Let's say I bought around 10 or 15 servers, and I'm not satisfied with the performance. I can change my server and migrate all my workloads to the new servers in the future.

VMware has an edge in terms of computing and networking because if we are going for a VMware infrastructure solution, there's a storage layer, so it can work with any kind of server or vendor. Suppose I buy some of my servers from Dell, some from HP, and a few from various companies. VMware gives you the flexibility to work with any vendor, networking, switches, and storage. They can come together in a complete software layer. I can have five servers from five different vendors. If I don't like one, I can plug in a server from any vendor in the stack, and it'll work. 

We use this as storage solution for specific VMware services and for backup solution.

The most valuable feature is stability.

Disaster recovery needs to be improved, when there is a crisis, there is a problem with what is the quickest way to get out of it. This should be done automatically, not manually.

If we have a power failure then you have to find your way manually. There 's no way to automatically fix it. So there should be an automatic way to repair such crises from disaster recovery.

In the next release, I would like to see more clarity on where the files are. the details of the files, for example, where the owners of the files are, and more audits.

We have beeing using VSAN for the last three years. 

It is more stable now than it was before. It's not like it was in the first year.

Now it is stable, and we trust it more.

We don't want to enlarge the environment. If we have a new need, we will separate and start a new system.

We don't want to have a general-purpose infrastructure. It's not a good idea for our purposes.

We value less scalability more accurate assessment as it is not the way in our environment. We don't want to add more nodes to the same cluster, it's not a good idea. We separate it.

We get immediate response from the vendor on phone. For tasks onsite its not sufficient.

of course its a matter of service level, no complaints.

No, software solutions from VMware based on VMware platforms no migrations.

The integrator "vendor team" had good experience at the last project. level of expertise was very good.

I would rate this solution an eight out of ten.

Our primary use case for vSAN has been our branch locations and multiple different office locations. We are running vSAN as an alternative to external storage arrays, and it's working really well to provide us with data storage at these branch sites.

The most valuable features of vSAN are its simplicity to deploy and that we can use commodity disks in our servers without complexity or need for external storage arrays or storage specialists on our teams. It's part of our vSphere admin's duties as opposed to storage experts.

The features of vSAN allow us to reduce our operational complexity to a large degree. It's a single pane of glass for the administrator, and we're able to somewhat reduce costs, other than the fact that vSAN is somewhat expensive to license.

I see room for improvement for vSAN just around general hardware compatibility and expanding that sort of matrix. It's pretty wide already, but everything else within vSAN seems to work really well. It is very well-integrated. 

I don't see a lot to complain about at this point.

Stability with vSAN has been really good. We've had very few issues. When we have had maintenance issues, the vSAN has come back and healed them automatically for us. I don't think that we've had to actually engage support a single time in the six months that we've been running vSAN in our corporate office.

I can't really speak to scalability. We have a fairly limited deployment at this point with three nodes, so it's a bare minimum sort of configuration.

We have not had to engage technical support for vSAN. At this point, we've been able to solve all the problems or basically work through the GUI intuitively to be able to resolve anything that has happened.

The decision to switch away from standard array to vSAN was a fairly simple one for us. We had been decreasing the amount of operations that we do inside of our branch sites. For the sites which remain, vSAN is a good fit versus the legacy Dell EMC VNX arrays that we had been deploying. 

We are finding that vSAN is a lot more scalable and adaptable, because we can go in with hybrid arrays for our lower-end storage needs or with all-flash versions of vSAN for places where we need more performance, and it's coming in at a lower cost point than an actual traditional array.

The initial setup for vSAN was extremely simple. There are some concepts that you need to understand before you go in, install, and click the buttons, but once you have your drives configured and inside of the individual nodes, the configuration takes just a few minutes. Everything gets done and orchestrated for you directly from the vSphere or vCenter consoles.

If I had to rate vSAN, I would give it a nine out of ten.

When we're choosing a vendor, we're looking at the ability for the vendor to be in business:

• The viability of the vendor
• Its reputation in the marketplace
• The technical solution.

These have a lot to do with our decision to work with a particular vendor. We typically seek out the best-of-breed solutions and try to adhere to those. At the same time, we try to work with the same vendors over and over, because we have existing relationships to leverage and existing expertise around the solutions that are adjacent to what we may be evaluating.

I find that vSAN allows for very easy administration. The fact that you don't have LUNs to set up and assign is great. The ability to set up storage policies and assign them at the disk level is also a great part of this product. You can allow for different setups for different workload requirements.

vSAN allowed for the expansion of our Public Library Patron computer environment into a three-node VMware cluster using commodity servers. This eliminated the need for expensive disk arrays and controllers while providing greater reliability and performance.

We have been using vSAN in one environment for about eight months and another environment for about four months.

The only issue I encountered during deployment was with the hardware and not with vSAN itself. The disks in the new servers were installed at the factory as RAID disks. I had to mark them as non-RAID disks, so that vSAN would be able to see them correctly for addition to disk groups.

We have had no issues with stability.

Fortunately, I have not had to contact support for any issues with my implementations.

We have a Nutanix environment running in production as well. We chose VMware vSAN for several reasons. First, the vSAN solution is part of the ESXi kernel. This allows for the product to be very fast with little overhead. Secondly, vSAN is included in the Enterprise Plus version of ESXi which, compared to competing products, provides a great cost savings.

The initial setup was straightforward, as was learning the vSAN environment. The complexity comes in setting up and managing the storage policies. These can be simple or complex depending on the environment. When using VMware Horizon View, there are several storage policies that are auto-created and -managed. Creating and managing your own policies and rule sets depend on your needs and workloads.

VMware vSAN is included in the Enterprise Plus level of software that we purchase. Our cost savings is in buying commodity server hardware with local hard drives instead of investing in large SAN hardware.