Try our new research platform with insights from 80,000+ expert users
it_user509289 - PeerSpot reviewer
Solutions Architect at a transportation company with 10,001+ employees
Real User
It's simplified our deployment methodology a fair amount, and it gave us better performance.

What is most valuable?

I think performance and cost are the most valuable features of VMware Virtual SAN. We're stringing up an entire virtualization environment for VDI and RDSH through Horizon View. When we compared the cost of a traditional SAN versus VSAN, that’s what actually made it all possible for us. We're actually able to deploy Virtual SAN for a fraction, like 1/5th, of the cost, of what we're paying for our SAN. It was crazy. The reduced cost made it very palatable and then the actual performance of it made it even that much more functional.

How has it helped my organization?

I'm from the cloud virtualization side of things, so consolidating the data allowed us to set up the VSAN instead of a traditional SAN, and allowed us to do faster deployments without having to interact with as many teams. It's simplified our deployment methodology a fair amount, and it gave us the better performance we're looking for from a SAN perspective.

Beyond that, it didn't change a lot how we function, necessarily, but it gave us a better tool, or a tool specific for our use case, or something that opens up the door for more. I think that the product itself is going to be paramount in other expansions and other aspects of the corporation. We'll likely keep expanding it into general computing and servers across the globe. It might help with some of the other deployments, cache centers and data centers, so that we don't necessarily have to buy SAN. It gives us the performance for the cost that really makes it attractive overall. Beyond that, I don't know.

What needs improvement?

I know it's coming, but I'm really excited for the encryption. I know it's on the all-flash, which is fine, because we're migrating to that anyways. Nonetheless, the encryption would be great for at-rest data, because I don't want to rely on a third party. I don't want to get some self-encrypting drives or anything like that; drives me nuts. That would be very good to get.

I'm looking forward to being able to do VSAN shares with other clusters; sharing the VSAN storage outside of its existing cluster so that we can actually move data a little bit easier between them, or allocate VMs across the entire frame and all the different VSAN storage. I want to try to make more use of the VSAN storage and do some better vMotions across hosts and clusters. That, I think, would be the best.

What do I think about the stability of the solution?

I like its stability. I think we probably need to get an additional node in there. Right now, we're running some 4-node VSANs. We probably should be at a 5 with a 2-RAID parity on that. Four is okay; it's stable, it's efficient. I haven't really run into any issues with it.

Some of the earlier versions were a little rough; we saw some weird, crooked behavior. Beyond that, it's been solid, and it just works. No issues yet.

Our early deployments of VSAN ran into a few issues with performance. Some of the nodes we installed initially had very high IO utilization when nothing was occurring on the disks; likely related to some replication tasks. Additionally, our fault tolerance was low using just a four-node VSAN (giving an N+1 configuration). We really should be a N+2 (which apparently takes six nodes, not five…).

Performance since then has been outstanding.


Buyer's Guide
VMware vSAN
June 2025
Learn what your peers think about VMware vSAN. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,168 professionals have used our research since 2012.

What do I think about the scalability of the solution?

We're actually scaling out right now from several 4-node VSAN clusters to - I think we're going to go to - some 8-, and then eventually 12-, node VSANs. That's one of the really nice parts about it; we'll just be able to scale out. The only downside I think I have with it from a scale perspective is, we've got some hybrid VSAN right now. That's what we all started out with. We really liked the all-flash VSAN arrays that you can get, so we're doing that. However, we can't merge the two, so we have to create whole new clusters for the all-flash VSAN. That makes scaling a little bit rough there, but I don't think that will be much of an issue going forward, because flash is pretty inexpensive now and that's probably going to be the standard from here on out.

How are customer service and support?

I think we used technical support earlier on. I didn't personally, but I know our engineers had to work with technical support on some issues with a couple of our VSAN nodes kind of going crazy when they were doing some initial configuration setup. They were just sitting there idle, and one of them would spike up; I don't know if it was trying to replicate data or do something odd. They worked with the support team, got it resolved and addressed it, upgraded to a new version and haven't seen any problems since.

I think there could always be improvement. Whenever we interact with the VMware technical support, it's usually because we have issues that aren't easily solved. We've got our own set of engineers that are really intelligent guys, very capable individuals. Whenever we call in, we always get the initial first line of defense, "Hey, give us your logs." Okay, here's our logs. And then they ask us silly questions and basic troubleshooting and, "Did you do this?" Of course we did. I guess the initial support services guys are just that basic line of defense. They don't always really understand the people that they're dealing with nor have that knowledge of the customer base. That knowledge set they're working with makes it difficult to interact with them a lot of times and getting issues escalated. It's always been kind of a tricky thing for us.

Which solution did I use previously and why did I switch?

We've been using traditional SAN for a long time. Our engineers had to do test with an initial project to do some developer builds, and they wanted some persistent VMs, and they wanted humongous amounts of storage in them, because they're crazy people. The goal was to give them some virtual machines to replace all these physical machines that they had, because whenever they mess up a machine and they want to rebuild, it takes a long time. You have to rebuild the whole machine, give it back to them, and then they have to build it out all over again.

Using the VDI solution, Horizon View, and VSAN made it actually cost-effective, because if we were try to do the amount of storage that they were looking for on the VMs with traditional SAN, it would have cost us a lot more than anybody's willing to spend or to endure. The VSAN made it very possible and gave us the performance needed to actually facilitate and even perform better on the VMs than they do on the physical boxes that they were using, which is good. It all helped.

Which other solutions did I evaluate?

At the time, we did not look into other solutions. It was either SAN or VSAN. From a SAN perspective, we have a partnership with HP for some 3PAR storage, and we have some EMC storage as well. When it comes to VSAN, it was included in our ELA that we agreed with from VMware's perspective. We figured, if we're paying for it, we might as well try using it. It worked out really well.

What other advice do I have?

When selecting a vendor like VMware, a lot of the decision comes down to functionality. Functionality, performance, and cost, those are the usually big factors. A lot of times, my company's really focused on cost, which is a pain in the butt. We're a very big VMware shop to start with, so whenever we can use a product that can simplify deployments, simplify management, and integrate with everything that we already have, that makes it really desirable. That's I think what VSAN did; it really simplified the way for us to get our storage for virtual machines and give us that performance and at a lower cost. That satisfied all the different aspects we look for in products.

I gave VSAN a perfect rating because it's been great. We really haven't had any problems with it; it's been solid. I haven't had to deal with the SAN guys, so that makes my life much better. We get much better performance out of it than I would have ever thought. We get all the IOPS we need from it; we get dedupe on the all-flash array. It's my own little SAN and nobody else gets to mess with. I think it's fantastic. I just love it, I really do.

If you have the budget or it's available to you, definitely go for it, because it's going to save money over the traditional SAN.

The only caveat I ever give to anybody about it is that the initial investments are a little rough. You can't just build a 1-node VSAN; you can do a 2-node VSAN, but, boy, no one ever wants to do it. To really get to a point where you get the data redundancy and the high availability, you need a 4-node VSAN, which can cost a fair amount for that initial investment.

If you're trying to do something small, it doesn't make a lot of sense, but if you're in a larger organisation like we are and you have to do a lot, this is a fantastic tool.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
PeerSpot user
Data Center Engineer at Strategic Solutions of Virginia
Video Review
Real User
I'm able to manage it easily from the web client as it's fully integrated in the VMware stack. As an improvement, I'm looking forward to VSAN Observer being transitioned into the web client.

What is most valuable?

The most valuable features of VSAN are consistent and increased performance with a linear cost which helped us in our data center.

Using VSAN Observer, we were able to see exactly what the VSAN environment is doing on a day to day basis, so we've gotten to really enjoy that interface.

How has it helped my organization?

The benefits that we're seeing are directly related to our customers. They have better experiences using their EMR and practice management systems.

The manageability is better, it's definitely fully integrated into the VMware stack so it's very easy to use from the web client.

What needs improvement?

The features I am most looking forward to are the performance monitoring capabilities of VSAN Observer being transitioned into the web client. That's what I'm really looking forward to.

UPDATE: Capacity and performance monitoring is now available in the web client and works well in 6.2. I am looking forward to DARE(data at rest encryption) in the next version.

For how long have I used the solution?

We have used vSAN for approximately a two years.

What was my experience with deployment of the solution?

We had one issue with deployment, which was related to using the legacy vsphere client to place the hosts into maintenance mode. Which is easily resolved by using the web client for maintenance.

What do I think about the stability of the solution?

The stability exceeds what we're currently on from a standard SAN platform.

What do I think about the scalability of the solution?

The scalability is much greater than the current SAN that we're on because we're technically locked in to a certain number of discs and a certain number of performance and so the scalability is drastically improved. We currently have a four node cluster and we're going to be just incrementally moving off of our legacy SAN.

UPDATE: We expanded our cluster to five vsan nodes however we are now in process of retrofitting four legacy hosts for a total of nine vsan nodes.

How are customer service and technical support?

Technical support was very responsive, the technical support staff was. Specifically patching hosts, we inadvertently caused VSANdata evacuations during the middle of the day. Whereas, if you were to do a maintenance mode with non-evacuation, that wouldn't happen but they were able to get to the root cause and provide us an answer on why that happened.

Which solution did I use previously and why did I switch?

We made the jump to VSAN primarily due to cost renewals going up year over year on traditional platforms. The software and hardware costs that we see now is just linear, we know what it's going to be.

We actually have been with VMware for quite a while so we made the choice to use VSAN because of that partnership that we have had over the years. We're fully focused in VMware and we love the product. That's why we chose VSAN.

How was the initial setup?

I wasn't familiar at all with VSAN at the time, so there was a little learning curve there but outside of that it would be comparable to setting up a legacy SAN environment.

What's my experience with pricing, setup cost, and licensing?

We actually, just by incrementally increasing the cost of our servers, plus the licensing, we were able to linearly scale our environment as opposed to doing forklift upgrades.

Which other solutions did I evaluate?

We evaluated other all-flash arrays and hyper converged infrastructure.

What other advice do I have?

Everybody wants to say 10 and I would say it's going to be a 10. I love VSAN and I would say it's probably an 8 and there's room for improvement. It's constantly being worked on and I think it's going to be the storage platform going forward.

Colleagues looking into VSAN, I would recommend looking into the VSAN Ready Nodes, they're pre-configured and you can customize your build to whatever you want really, without having to build your own necessarily.

We aren't currently using the Ready Nodes, but I could see where a Ready Node would be beneficial for deployment. The time to deploy would be improved using a Ready Node.

Peer reviews and peer contents are amazing things to be doing. That's part of the reason why we come here. We want to maintain our relevance, industry wide, and so we always constantly bounce ideas off of other peers in the industry.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
VMware vSAN
June 2025
Learn what your peers think about VMware vSAN. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
860,168 professionals have used our research since 2012.
PeerSpot user
Lead Engineer at SynchroNet
Video Review
Consultant
We don't have to drop half a million on a SAN for all the storage that we may or may not use, and it just eases the pain of a lot of storage. There were bugs, but things have stabilized significantly.

What is most valuable?

We have a private cloud that we host in our data center. All of our servers are on VSAN and we have customer servers that we host in our data center on our hardware that is on top of VSAN.

Data store: you don't have to carve out ones and ones and ones and then map from the data stores and data stores and data stores. Good performance.

It makes it really modular too so we can grow as needed, that's actually the case that I submitted to do this talk was about another customer that we host in our rack at our data center wanted to do small entry, have a small entry footprint but then grow as their business acquired other business.

How has it helped my organization?

Benefits are being able to grow as needed. We don't have to drop half a million on a SAN for all the storage that we may or may not use and it just eases the pain of a lot of storage. You still have to deal with the, the networking of it, making sure that everything is networked together, but that radically simplifies the storage administration piece.

Some of the problems that I have with, traditional SANS whenever I'm administering them is, whenever I do edit operations I have to be extremely careful. It requires a lot of planning up front to deploy the LUNs. To make sure everything matches all the way through from end to end. So that when I know have a data store, you know, one, whenever I turn it off on the SAN after I’m done using it, I'm not turning off the wrong one and taking down the entire environment. Things like that. You know, I don't have to deal with that 'cause it's just one data store and it does what I need it to do.

So, another big use case that we do is Horizon View for VDI customers. We use it internally and the contrast between our internal use, which is off of an NFS store, contrasting that with a VSAN, deployment is like night and day. Our internal one is kind of slow and kludgy. It's not a big central part of our day to day work so it doesn't impact us as much but I can see how big the difference is between the performance of a Horizon View deployment on an NFS target is compared to how tightly it works with VSAN and how much performance and throughput VSAN does with the, the read and write caching with the flash drives. We haven't got to mess a lot with the flash, all-flash VSAN, yet, but I'm sure we will soon here.

What needs improvement?

The dedupe is awesome. The stretch clustering is crazy, in my opinion. It's really cool. We've been talking about it internally and have lot of school districts and it actually makes a lot of sense for a school district because they have the fiber runs between the buildings so they can hit the five millisecond, ten, twenty, forty, a gig, requirements of the network and it would be a good use case for them I feel like. We have to look at the reality of it, of course, cause it got announced like yesterday, but it's really exciting to see some of this stuff and especially dedupe. Dedupe for root would be really cool. It's really kind of taking that mindset that I see a lot of people have that VSAN isn't, you know enterprise ready and putting it to rest.

For how long have I used the solution?

We are a partner with VMware and we do deployments services. Do a lot of professional services that's a lot of what we do and then we're growing our managed services to be able to incorporate VMware monitoring and alerting both, proactive and reactive, to be able to stabilize customer environments and give them the best performance that they can out of their products.

What do I think about the stability of the solution?

Starting out there was some stability issues but I don't see them the same way that I did. There were bugs, there’s firmware, the HCL cam, seemed a little fluid but things have stabilized significantly. There haven't been any major outages that were something that I would say wasn't our fault or wasn't due to like a configuration error somewhere in the stack so, and the best part about it actually was, whenever we did have these stability issues and outages VSN never dropped data.

It wasn't until we had gone through like five or six, dirty reboots that we started to have it drop the objects from the metadata tables so we couldn't address the objects and see them but they were technically still there, there was just no owner of them. So if we had gone in, you know, with a higher level engineer that knew how to take ownership of those back we would have been able to get them back but it was a VDI deployment so we didn't really care we just scorched earth and began again, but you know, data resiliency has been something that VSAN evangelists really talk about and it's something that they really do. You're not dropping data as long as you stick to the HCL, of course.

What do I think about the scalability of the solution?

Scalability is good. We haven't had to scale a lot. We scale from a three node to a four node and we're trying to decide that to a five node or not, it's pretty easy. Once you have a networking piece set up, like, that's one and done. Upfront costs and then you just bolt everything on the side because you just blast out the same config, same quotes, same everything. Get the exact same hardware. Stick it on. Scales out.

How are customer service and technical support?

Once you get to the VSAN team they know what they're doing. Like bar-none. They are incredibly receptive. They’re very good at giving you root cause and analyses and helping you work through issues.

Which solution did I use previously and why did I switch?

We've been a strong VMware partner for a long time and we saw, my direct boss is John Nickelson, he's a vExpert, a huge, huge, huge storage person. He really identified the value that it was going to bring and how, impressive the technology was to have this, you know, kind of decoupling from the, you know, the big SAN box that sits in the corner and it really makes a lot of sense for certain use cases.

Some use cases where a traditional SAN is the right move, you know, if you want the capacity and stuff like that but the VSAN really helps especially with the VDI. That was where our biggest play was initially, was Horizon View mixed with VSAN.

We usually will do a four node deployment. That's in our opinion, the best configuration. Three nodes the minimum, but we like to do four so we can do rolling upgrades without losing our n+1 fault tolerance, and so, when we initially started using this, and technically it was before I started working there. When we initially started using this, we'd roll it out and just take advantage of the performance improvement that it would make. Getting the right cache with the flash drives, you know, allowed us to spin up, spin down, fast log-in times, fast application delivery. Really makes a difference.

What's my experience with pricing, setup cost, and licensing?

If you're looking at a traditional SAN you're already looking at a lot of money anyway. So, VSAN is a contender in a lot of cases.

Which other solutions did I evaluate?

To my knowledge we didn't ever do like Citrix or, you know, anything like that. We didn't actually deploy the VDIs that are on traditional SANS so I think that we have just done pretty much all VSAN coupled with VDI 'cause it just makes so much sense.

What other advice do I have?

Obviously, it saves rack space and that's something you have to consider. It's an important thing 'cause you got to pay for power, cooling, if you got give him more cabinets cause you got another SAN coming in that's more money for you that you may not be fully utilizing and it really helps with that efficiency. You know, your rack space is doing as much for you as they can because if you have to compute the storage memory, in some cases will view the GPU off load just for us all in a little for you, for your rack, and we have three of the exact same deployments just like on top of each other. Two of them are customer's and one of them is ours and they, you know, at 12 views of stuff, just one on top of the other where it would be, probably have a full rack rather than just, you know, a quarter of the rack and that's very beneficial.

I'd probably rate it a seven right now. Probably in six months it'll be an eight or a nine. Just, you know, growing pains obviously. It's a fairly new product. Having to deal with some of the baby steps, you know, and the HCL, getting the HCL right, the ready nodes things that they've been doing they've pretty much replaced the HCL with ready nodes. That was actually our initial offering for VSM was that. So, that actually simplifies the process a lot. It helps to bolster and make sure that you're not deploying something that isn't going to work.

You got to size the compute, the memory and the storage right? You got to make sure that all those are going to make sense so that you're going to be able to hit that within the con-con-confines of VSAN. Yeah, you only get the one flash disk and you want to make sure that you're hitting at least ten percent flash, magnetic disk and so you have to just you have to evaluate it. You know, make sure that it makes sense and don’t discount just because you think it's not enterprise ready or that it's too expensive.

Disclosure: My company has a business relationship with this vendor other than being a customer. We're partners.
PeerSpot user
PeerSpot user
Principal at a tech services company with 51-200 employees
Consultant
In terms of resiliency and recoverability, with policy-based storage you can decide what level of recoverability and redundancy you want.

What is most valuable?

Some of the most valuable features of VSAN include the ability to be able to provision and grow your storage as you need to without a very large upfront cost. Also the ability to be able to carry along the licenses as part of a refresh as opposed to traditional storage systems, you end up losing that investment after every single refresh which usually occurs every three to five years.

How has it helped my organization?

The great thing about VSAN in terms of resiliency and recoverability is the fact that with policy-based storage, you can actual decide what level of recoverability you want, what level of redundancy you want. This no longer the case of trying to figure out complex RAID-systems or anything like that. You set the policy, and you will get the level of redundancy and resiliency that you want. Something that has been in the enterprise space for quite sometime, with some of the more expensive arrays, now you can bring it down into the commercial even the mid-market space. That's pretty amazing.

What do I think about the scalability of the solution?

For scalability of VSAN, I mean, you've seen the blog post out there. They've taken up to four million IOPS. In terms of scalability, we haven't seen any roof, any limit, any ceiling to the scalability there. We are extremely surprised that VSAN has been able to keep up with solutions that are four or five times more expensive.

How are customer service and technical support?

The technical support for VSAN has been really surprising in a good way. In our experience, there are very few vendors that take full ownership of a problem when it occurs. What VMware has done is that whenever there is a VSAN issue or a question, as long as the hardware is on the hardware compatibility list, they took full ownership. They escalate with the hardware vendor. It's really one throat to choke. Where else can you say that?

Which solution did I use previously and why did I switch?

We've been a VMware partner for quite sometime. When VSAN was announced, we were actually working with the beta. We decided that this is really the track that we want to follow because we believe in the software-defined data center. Everything is becoming software-defined. For us to not do the same thing with storage when we're doing it with networking and with compute, it just really doesn't make sense. The same kind of savings had been brought by server virtualization, the same kind of flexibility, agility, that can also be applied to storage. So, it just seems like the next natural place to go. For us as a VMware-focused partner, it made sense to get on board with VSAN right from the get-go.

Previously before VSAN, we're using a whole host of different technologies because there were a lot of corner cases where we would have to use an enterprise array. Other times we would end up using something that's a little bit smaller. What VSAN has done is, not only bridge some of the gaps that we had in storage before, but it's allowed us to replace a lot of solutions that didn't really meet the needs perfectly. Here we've got a more custom-fit that we can provide our customers and be able to address about 80% of customer's needs.

What's my experience with pricing, setup cost, and licensing?

From a cost-benefit perspective, especially in regards to TCO, total cost of ownership, CFOs, CEOs that are looking to really cut down the cost of their storage systems because that's becoming a larger part of their overall IT budget. This uncontrolled cost is running along the same lines with the uncontrolled growth and data. So, you know, when more and more of that IT budget is going to storage, you have CFOs, CEOs looking to try to control those costs. What VSAN allows us to do is give them an enterprise-class array, enterprise-class solution at usually half the cost of the traditional arrays.

What other advice do I have?

I would easily give it a 9, because 10 would be perfect and nothing is perfect. After the next few releases, who knows? Maybe that 10 will happen.

For people who are evaluating bringing VSAN into their environment, one of the most important things to do is really get an idea of what the performance the requirements are and what workloads are going to go into that environment. That's best done with an assessment. Right now, VMware partners are providing a assessment service for VSAN. That's a great jumping off point to make sure that the VSAN implementation is going to go as expected and have an immediate win.

Disclosure: My company has a business relationship with this vendor other than being a customer. We're partners.
PeerSpot user
it_user335802 - PeerSpot reviewer
Global Cloud Architect at Tribune Media
Video Review
Vendor
Its part of the vSphere world, so it looks and feels like any other object that people are used to seeing metrics on. I would like to have snapshots for recovery be part of the core product.

What is most valuable?

It's not a storage array which is a very valuable feature of it and it's maintenance structure isn't paid like a traditional storage array. For me, that's the biggest leap with it is there's a compelling cost with reason to step in to it. You don't have to make a snap decision and get away from where I am. I can keep what I have and dip my toe in VSAN without risking an all-or-nothing decision.

How has it helped my organization?

VSAN is really simple to manage. Its GUI is part of the eco-system so it looks and feels like the rest of VMware. So a VMware engineer or a VMware operations guy's is going to be able to manage the provision storage without having to touch an array, which is generally higher profile so there's a cost reduction through headcount.

VSAN manageability is much easier because it's in and part of the vSphere world, so it looks and feels like any other object that people are used to seeing metrics on and there have been great improvement in management. In 655, there's a little bit of lack information. In the newer system, there's a lot more data about what's going on in that system, in the GUI, easily consumable.

What needs improvement?

The features I'd like to see in future releases of VSAN are around back-up and recovery. There is a great way to replicate data now, but I'd like to see them focus on making recovery from snap shots, off-site, part of the core product.

What do I think about the stability of the solution?

It's very stable. Once you get it built and you take the time to build the system correctly, do your research, once it's in place it's been very stable and it performs as it says.

What do I think about the scalability of the solution?

I'm looking at two different ways of scaling that system. One is for speed and one is for mass. It scales into mass based on what size of disc you choose and it scales in to speed based on solid-state drive size. Both of those are two different avenues that work well for us.

How are customer service and technical support?

I haven't had a technical support case open but we do look at the forums and try to avoid issues and problems based on what's in a publicly available space which has always been something that VMware has done really well, which is making issues public so we can avoid them.

Which solution did I use previously and why did I switch?

We chose it from a cost perspective. In media we are always looking to save money. It's a publicly traded company so the money I give back is smiled on. We saw a way not to pay maintenance for expensive systems and to run it in a system that performs on parallel with what we already own.

What's my experience with pricing, setup cost, and licensing?

So with a traditional storage array you pay maintenance based on the purchase price for the array plus any software you bought with it so that residual number is high, so if you paid a million dollars for the machine, you may have to pay $200,000 for maintenance at some point in time. With VSAN I'm paying server-based maintenance and that's a much lower number.

Which other solutions did I evaluate?

The top criteria we looked at when considering VSAN was performance and cost. We were going to make sure that we could deliver the performance that people are used to and used the system that costs less than a traditional array model. We did not look at other vendors because there really isn't another vendor that's doing this. There are people that are close but with a traditional hyper-converged box, there's a bunch of things I don't need. With VSAN I have the technical backing from VMware to back-stop the product and is doing what I need and no more so there is a cost-savings for not buying features-compute that I don't need.

What other advice do I have?

I would certainly give it an 8 and I would split in to two parts. The initial configuration of VSAN, once the systems in place, it manages and runs without much attention and that's where it's really shining at the moment, is once it's in production, it doesn't require a lot of care and feeding.

My recommendation is make sure you've got a hardware vendor who's promising you that this equipment that you get is on the HCL, so the compatibility list of what VMware supports and VSAN is important to having a successful deployment. Taking the time to do that and install and build the system correctly first will give you years of good results. Not doing that is a headache.

When looking at any new technology, having peer review and having information available about what it's doing, how many people have adopted it and whether or not it's a good technology is critically important. It's good to be on the edge but you don't want to be the first guy to take the blind leap so having that out and having the forms available has been very important.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
PeerSpot user
Senior Manager, Infrastructure and Operations at a agriculture with 1,001-5,000 employees
Video Review
Vendor
It works and integrates with other VMware technologies. They should integrate it with replication and SRM, so that it can be heavily adopted.

Valuable Features:

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.

Improvements to My Organization:

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.

Room for Improvement:

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.

Use of Solution:

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.

Stability Issues:

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.

Scalability Issues:

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.

Initial Setup:

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.

Other Advice:

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.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
it_user335178 - PeerSpot reviewer
CEO/CTO at Bay State Health (VertitechIT)
Video Review
Real User
We spend less on equivalent storage using VSAN to replace our traditional SAN architecture. They are working on extending VSAN's access outside of its virtual bubbles, which I'm looking forward to.

What is most valuable?

The value that VSAN brings to our organization, really there are two major areas. One is the ability to replace very expensive proprietary SANs. The other is the need to replicate and keep data available at all times across three separate data centers. Those two elements are really where VSAN plays.

How has it helped my organization?

Probably the biggest benefit we get is the replacement of the SANS and it's purely a cost one. To give you an idea, we spend roughly 50% less on equivalent storage by using VSAN to replace our more traditional SAN architecture. Further, the operating costs are 20, 30 percent less. The ability to scale our storage as we need it is far simpler with VSAN than buying the more traditional route. So I would argue that that's probably the single best feature we get.

What needs improvement?

There are features that I would love to see added to VSAN and I think they're being worked on. One of the major limitations is its inability to provide storage to things outside the hyper-converged world. Any traditional SAN we have left over in our institution will be for that function. Ultimately, if we can remove that by simply extending VSAN's access outside of its little virtual bubble, so to speak, that's the key. And as I said I think that's going to be added.

For how long have I used the solution?

VeriTech is a consulting and engineering firm specializing in health care. We provide, management and technical skills often acting as the CTO of, healthcare institutions. One of our engagements is I'm actually the interim acting CTO of Baystate Health, in western Massachusetts. VSAN is one of the primary ones but, software defined, architecture and complete hyper-convergence is really what we use VMware for. We use NSX and VSAN as part of our, absolute total infrastructure. And that's all part of vCloud, initiative. We also use Horizon for our VDI, implementation. And that pretty much-those products are 99% of what we use.

What do I think about the stability of the solution?

The stability of VSAN so far has been excellent. We're just beginning to enter production. We're beginning to migrate our data off a traditional SANS which are a collection of EMC, IBM, NetApp, whole range of them onto the VSAN platform and so far we haven't had any problems.

What do I think about the scalability of the solution?

It's actually the internal feature that I think gets us the great feature of savings out of it. With VSAN I simply add disk drives and hosts to my infrastructure at any of the facilities I have. The net result is an increase of both storage and processing.

In the older model, if I need to add, let's say a terabyte of space for some particular tier one application, I have to add a terabyte, from let's say EMC, into data center one, a terabyte into data center two, a terabyte into data center three, and if, in my adding of those, I cross one of those magic boundaries where I'm out of cabinet space or whatever, then I have all those expenses. None of that is true with VSAN. In VSAN, I simply add drives into a chassis anywhere in my system. If I need more space, I buy a simple chassis, throw it in there, and continue to add the drives. Much more scalable. There really is no limit to it.

How are customer service and technical support?

Technical support on VSAN has been excellent also. It's been a bit of a paradigm shift for our employees. They're used to that traditional sort of big iron, I'm going to call it stair-step limited approach and it's taken a little bit of skill to get them used to it, but VMware has been there right for us from the beginning. They've helped our people understand the difference and we're pretty much now self-sufficient.

Which solution did I use previously and why did I switch?

The choice of VSAN was almost made for us. And let me step back for a minute and say it's not particularly the product, although we love the product, it's where we suggested after quite a lot of testing of other-of other competing products, we knew that traditional SAN architecture and the cost of deploying it, maintaining it, was unsustainable. Our budgets in healthcare IT are flat. No one's giving us extra money. But, with all the images and the doctors and the sharing of data, the need to store data is not being held flat. It's going way up.

We simply don't have the money. So we needed some new, way to address storage. And that meant software defined storage. So that was a given. The next step was we needed something that would provide the levels of service we have, and stability we have with the traditional architecture but at far less price. That's where VSAN shone. That's where when we did all the necessary testing and reviews VSAN acted in a secure performance and cost, areas needed.

The selection of VSAN, it's really part of a larger hyper-convergence model and for technical reasons and for simplicity, we wanted products. If we were going to move our entire, siloed approach of storage here, processing here, networking there, onto one single platform, we wanted all of those abilities buried into the extraction or the hypervisor level itself. We didn't want to buy independent little products and snap them in so to speak. Really, that means the only solution suite was the VMware world of products -- NSX for networking, VSAN for storage, and vCloud for everything else. So it really was a no brainer. That was really the essential relationship between VSAN and the other products.

How was the initial setup?

The implementation of VSAN along with the implementation of all hyper-convergence technology is tricky. Although we benefit greatly for it now, there were a lot of issues that, we simply had to work through. And these are not really an issue related to the product itself but more related to the nature of what the product does. Since VSAN is a software component that allows you to add storage to your hyper-converged system, which in turn is based on products like Cisco’s UCS, the revision of code in the Cisco UCS chassis, the types of drives, the levels of drivers across the entire platform are essential to keep in lock step. So, we had many cases where, as we added capacity, turned on new features, began to migrate, we ran into all sorts of, um, difficulty. But the truth is, with our people, with VMware’s, with Cisco’s, everybody supplied the skills we needed and now we're pretty much, we're there.

What was our ROI?

Well, VSAN is a solution of replacement. VSAN is going to replace all of our traditional SAN. So ultimately at the end of the day a couple years from now, almost all of our storage should be on VSAN. It really should be very little if anything left.

Which other solutions did I evaluate?

When we selected VSAN, as I said, remember, it's part of a total package, so the better question is, when we were selecting hyper-convergence, who would be the vendor for that. Well, there aren't that many options out there. There's really three. You have Microsoft. You have, open stack solutions and open source solutions, and then you have VMware. The Microsoft product, although engaging, isn't really ready for prime time according to our needs. The open source open/stack option is potentially interesting but requires a great deal of internal engineering and support that healthcare systems really don't have. Really left VMware as the only viable, affordable, complete solution. And hence we chose it.

What other advice do I have?

On one side is a strategic vendor and that's where VMware, Microsoft, in the medical case, Cerner, which is a large application provider. There are four or five vendors that I would consider strategic and these are vendors that we could simply not operate without the function that they provide. So when a vendor's classified as strategic and then we look at the function they provide, there has to be a level of commitment. They must be a market leader. They must have enormous R&D capabilities. They must be flexible. They must interact with our engineers at a peering level, not simply as a dictatorial here, use this, and that's what's good for you and no more. VMware clearly acts appropriately like that. So, because, VSAN is part of hyper-convergence, hyper-convergence is a strategic imperative you can connect the dots where a company like VMware is necessary.

I would say, that they are definitely there. They're a high nine [out of 10]. Anybody that's looking to do hyper-convergence I think needs to understand a few basic principals. And all of these apply to VSAN as it applies to any of the elements of hyper-convergence. This is a long project. It's not something that's going to happen all at once and the value is after completion, the sum total of the parts.

If you go through a project like this for example, at Baystate, it's a two to three year project with required funding across that period of time. If, for some reason, we withdrew funding halfway through this process we would end up with less than the sum of our parts, we would end up with a lot of disconnected stuff. So be sure to make sure that your management and the people involved understand that this is a major commitment. It's not, oh, I'm just going to buy this once and forget it.

The other thing I would suggest, be paid attention to, is the affect this has on your people, on your engineers, on your workers, your HR considerations. In a traditional environment like ours, we're siloed. We have our storage guys here, our networking guys here and so on and so on - very expensive, a lot of duplication. In a hyper-converged model, all of that becomes one. Really what you have is a series of better trained, more effective engineers, but less of them. That doesn't mean you fire people.

That means you now put those people to other projects that have been sort of languishing because we just could never get around to them. That's, I think, a big thing to understand, that you will affect the way your users work. If they're not willing to learn new skills, if they're not willing to cross boundaries which were once siloed, your project could be in jeopardy.

When researching anything like hyper-convergence, the more information the better. We spent a great deal of time talking to not just health care institutions, and to be fair, this is a relatively new trend in health care so there really aren't all that many to talk to, but there are a number of non-healthcare institutions that are further along in some of these projects than healthcare is. We spoke with them, we spoke with vendors, we spoke with even other consulting firms. I think it's very important to gather as much information as you can before, you know, embarking on this.

Finding the resources for the gathering of this information is both hard and easy. It depends on which one we're talking about. The ability to get information from other institutions if they're outside of healthcare, and remember I'm speaking from a healthcare point of view, may be difficult, because they may not be allowed to share certain information. Getting consulting information is difficult unless you, of course, engage them. And I would argue that it's not necessarily such a bad idea to engage for a small amount of money the relative experts in some of these consulting firms and just have a quick conversation with them. If all of a sudden they seem to be knowledgeable, you do your homework on them, I would argue a further engagement is not necessarily a bad idea. But you do have to put some efforts into finding the info. It's not just going to fall out of space.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
it_user603867 - PeerSpot reviewer
it_user603867Works at a tech company with 51-200 employees
Real User

Many Excellent Points.

See all 2 comments
it_user335157 - PeerSpot reviewer
Director at Cloud Carib
Video Review
Consultant
We simulated disk, host, and network failures. Virtual SAN had no issues dealing with them.

What is most valuable?

With Virtual SAN we did like the performance, the simplicity, the fact that it’s very easy to manage and upgrade and the integration with all of the VMware technologies that we are very familiar with. Also the fact that it's completely different from the old paradigm of provisioning storage and different storage systems and it's also saving rack space. We use less physical space for the deployment of storage systems.

When we first were shown Virtual SAN, we compared our traditional storage system what we had with the Virtual SAN performance in one of our labs and we showed that the performance was impressive with Virtual SAN. So, we started adding more applications to it and expanded this Virtual SAN Proof of Concept that we had. So, we realized that our performance is comparable to old flash, disk carriage at a much better core structure that we get as cloud providers. So, the fact that it is very fast, very simple and the fact that it's also easy to consume as a cloud provider, this made it a no brainer for us.

How has it helped my organization?

The simplicity to provisioned VMs and applied policy to specific VMs for our customers is one of the most important features for us without having to separate the area of storage like we had before with our traditional storage system. As a cloud provider the biggest challenge with storage is that you get completely mixed workloads. You don't know what the customers will be landing on. So, there is no way to predict the storage performance needs of a customer before they actually start using the systems.

What needs improvement?

There's some features in the future releases that we would really like to see: encryption as part of the offering. The application and compression would be nice to have those features available in the next Virtual SAN releases and also the capability to serve storage through other protocols. Like NSF or iSCSI for other vendors, for other applications that are not VMware. We have some solutions now that we use like Nexenta, in order to do that but it would be nice if Virtual SAN support of this natively. So we have one vendor to deal with.

For how long have I used the solution?

Cloud Carib is a cloud provider in the Bahamas, and it’s targeting enterprise customers in the Caribbean. The company started about three years ago and because we're using VMware products since the beginning, working with Virtual SAN on the new storage offering in addition to our vCloud stock which is the Cloud Director, vSphere, and VCNS.

What do I think about the stability of the solution?

There’s never been an issue with Virtual SAN over the last year that we've been testing it. Support is really efficient because it's same global support with VMware that we've been with and we are familiar with. As far as I know, some of the highest rated support from any vendors that we use. We did all sorts of tests initially before we deployed in the production environment. We simulated disk failures, host failures, network failures, and Virtual SAN didn't have any issues dealing with all of these failures, so we're confident in that deploy more applications, more VMs in this system.

What do I think about the scalability of the solution?

Since the original deployment, we have doubled the capacity of our recent cluster with zero down time. So the more nodes we have the more capacity we get the more performance and there's no downtime. So, it's very easy to scale up, scale-scale out with VSAN and all it takes is a few clicks. It's a very efficient way to upgrade your storage without adding more rack space than you actually need because by having converged storage network in the computer capacity, we don't have to waste rack space which is at a premium where we are in the Caribbean. So we did like the fact that we can scale our compute and our storage at the same time without wasting rack space.

How are customer service and technical support?

The technical support that we get from VMware is part of our cloud provider contract is very efficient, very quick responses. The support is always knowledgeable and they can resolve the issues. As far as I know it's one of the highest rated support from any vendors that we use and this is very important for our storage system because that's the most critical aspect of customers' data. They need to be able to have confidence that the data is on a solid stable system.

Which solution did I use previously and why did I switch?

So the way that we found out about Virtual SAN, we kept running into performance problems and capacity problems with our current storage that we had before. With all storage that we had and Virtual SAN is a radically different approach. So we were intrigued by that and, after testing it, we realized that all of our requirements were met by this approach. So some of the criteria that we look at when we evaluate vendors is the credibility of the vendor in the industry. The support history that we have with them, customer references.

So with VMware, we know that VMware is already used by everybody in the Fortune 500. Huge companies globally rely on VMware for day to day operations. So, we’re fully con=fident in basically running all of our infrastructure through the VMware technologies.

How was the initial setup?

We spent quite a bit of time studying the design guides from VMware about the proper implementation and the hardware compatibility list. Ran all of the self-checks that were listed on the website and we used hardware that was certified ATL. And with these requirements- having passed the requirements it was very simple to enable Virtual SAN. So, after the initial, deployment design we're able to implement it in a matter of hours. It was, very, very simple. Much easier than deploying a hardware based storage system.

Which other solutions did I evaluate?

The vendors that were directly competing with Virtual SAN for our project were hardware vendors that were providing all-flash systems. This would be the comparison for us. The cost of the all-flash systems was prohibitive for us. We are a relatively small cloud provider in the Caribbean and, with Virtual SAN, we like the fact that we can pay through the VCOM program where we pay for only what we use and this was another huge benefit with Virtual SAN in our use case.

What other advice do I have?

There's no issues that we have with it so far. We're very happy with it. I would highly recommend Virtual SAN for any demanding application that this running on VMware. We have no have reservations at all with Virtual SAN. We recommend Virtual SAN to anybody was has demanding applications.

So a lot of people think that Virtual SAN is a new unproven solution that people might use for testing or development but, what we actually see when we talk with our peers and with what we see with our customers is that people are using it in production and we are using it in production. If it can be used in production for a demanding app environment like cloud provider, then it means that it can definitely be used in production for any company that has storage requirements, demanding storage requirements.

Peer reviews and peer comments are very important factors when evaluating storage solutions or any other priced IT solutions is the raw data that you see from the people that are using it the way that we are going to be using something. It's not media or something that's not tested. So, this has the most weight for us. The most important factor when considering a solution whether PRC.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: We're partners.
PeerSpot user
Buyer's Guide
Download our free VMware vSAN Report and get advice and tips from experienced pros sharing their opinions.
Updated: June 2025
Product Categories
HCI
Buyer's Guide
Download our free VMware vSAN Report and get advice and tips from experienced pros sharing their opinions.