- Allows for very easy administration
- You don't have LUNs to set up and assign
- The ability to set up storage policies and assign them at the disk level
- Allows for different setups for different workload requirements
We have been using vSAN in one environment for about eight months and in 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 in order to add them to disk groups.
There have been no issues with stability.
We have had no issues with scalability.
Fortunately, I have not had to contact support for any issues with my implementations.
We chose VMware vSAN for these reasons:
We have a Nutanix environment running in production as well.
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 purchased. Our cost savings were due to buying commodity server hardware with local hard drives instead of investing in large SAN hardware.