What to expect when deciding about vSAN
Overall Satisfaction with VMware vSAN
We have used vSAN to store our SQL databases. We have migrated them from an [all-flash] storage vendor and at the same time, we have migrated the SQL servers in active/passive clusters to [Always-On clusters]. Currently[,] we have 6 nodes for all our SQL production databases. We created an isolated cluster in vSAN so we [would] solve two main issues: SQL licenses (associated with hosts' CPUs) and storage [licenses] (associated with a storage box). We have [configured] different kinds of raids [(5, 6, and 10)] [depending] on each VM service.
Pros
- Save us costs regarding storage[.]
- Save costs regarding managed services[.]
- It [allows] us to manage in only one interface all aspects of our load[.]
- It reduces rack space[.]
Cons
- More granularity in statistics[.]
- More detailed graphs about usage[.]
- Easier way to find unused/unassigned hard drives[.]
- Easy of management[.]
- Single point of contact for VMware and storage teams[.]
- Less rack space[.]
- Reduce in SQL licenses[.]
- Reduce in storage licenses[.]
- Reduce in data center costs[.]
Currently[,] we are testing both technologies in a time frame so we [still know] after some years which one is the best, according to our loads' needs. We had VMware before moving to vSAN, one [of] many [reasons] to move to vSAN is the opportunity to make the jump in a continuous way. The basic infrastructure did not change, our tech team knowledge was maintained since we did not move to another vendor's solution.
Do you think VMware vSAN delivers good value for the price?
Yes
Are you happy with VMware vSAN's feature set?
Yes
Did VMware vSAN live up to sales and marketing promises?
Yes
Did implementation of VMware vSAN go as expected?
No
Would you buy VMware vSAN again?
Yes
Comments
Please log in to join the conversation