The reduction in cost of storage: In my most recent deployment, we reduced cost from around $20,000 per TB (CapEx) to less than $1,000 per TB (CapEx). This is not taking into account deduplication/compression or the ability to add disks and scale vertically, not incurring licensing costs, which would drive the cost down further.
Traditional SANs require large up-front costs, and with "forklift" upgrades, you end up spending a very large amount of money initially and then expect to recoup the costs over the lifetime of the array. This is not how vSAN – or any other HCI (hyperconverged infrastructure) product – works. The idea is to have a small initial investment and, with horizontal/vertical scaling, you can grow into the needs of your environment. This can be accomplished several ways, by either adding more disks to each host (vertical scaling) or by adding more nodes to the cluster (horizontal scaling). This allows for much greater flexibility with your storage. Before HCI, you were required to guess how much storage you were going to need, and were stuck with what you guessed at.
Upgrades are also much simpler. Because the system is software-defined, you simply upgrade the software rather than the entire hardware stack. If you want to upgrade the hardware, you would then simply add nodes in, and remove older nodes. It is also possible to create a new cluster and do a swing migration; however, this is similar to older-style upgrades. The point is that there are a lot of options available with HCI systems.
Management of the environments is overall simpler, allowing for during-hours patching with no downtime and little risk; also allowing us to stay more current with patching, reducing the overall risk of the environments.
The worst part of vSAN, as with most VMware products, is that you need to use the vSphere Web Client to interact with it. The vSphere Web Client is slow and clunky, making interacting with the system difficult and often times painful. I have been told that the new version of the web client will be significantly better, but do not have personal experience with it. Other than being difficult to work with, it can cause outage scenarios to take significantly longer to troubleshoot because you waste a lot of time waiting for the client to load information, or just load in general. It is a huge drawback for an otherwise very good product.
I have used it in various deployment scenarios since 2015, or about 1.5 years.
I have observed no stability issues when the product is deployed as instructed. It can and will have stability issues if you do not follow the hardware compatibility list (HCL) or the vSAN Deployment and Sizing Guide.
The product scales easily, up easier than down, due to the need to remove the disks and migrate the data from the nodes you wish to remove from the cluster.
Actual support engineers are excellent; however, opening cases is often difficult/frustrating.
In my current project, the customer previously used EMC VMAX arrays. As detailed elsewhere, the CapEx savings were incredible.
During my current project, initial setup was very complex, though this was by our own choosing and was needlessly complex. In the past, setups were often very straightforward, though you need to verify your design properly, as mentioned.
VMware licensing is per socket for VSAN, like everything else. The platform is very flexible, so be sure to look at all your options.
I was not part of the evaluation process but cost was a major factor, as well as high availability.
Discuss the deployment with VMware sales; I've met several of them and they are generally smart people looking to help get you the best deployment possible.