VMware vSAN Review

All objects in our datastore are replicated and can be failed over using the built-in HA feature.


What is most valuable?

Simplified datacenter failover in the VMware environment is the most valuable feature of this product.

Previously, when using SRM (VMware Site Recovery Manager) we’d have to configure VMware objects (VMs) for failover. With vSAN, all objects in the datastore are replicated and can be failed over using the built-in high availability feature.

How has it helped my organization?

vSAN significantly reduced the complexity of our data center failover along with the data center design requirements.

What needs improvement?

vSAN health reporting needs some work. There were a few instances where the vSAN would report health issues with disks, even though it was functioning correctly. I believe VMware stated this would be corrected in future versions.

We also had some issues with reinstalling hosts that had vSAN enabled. JBOD disks would retain the vSAN configuration information and would need to be manually cleared to allow for the new vSAN instance to be enabled.

For how long have I used the solution?

I tested it over a period of five months.

What do I think about the stability of the solution?

We didn’t have any stability problems. Once configured, vSAN operated without issue.

What do I think about the scalability of the solution?

We didn’t have any scalability problems. vSAN scaled quite well.

How are customer service and technical support?

Technical support is excellent. VMware provides top notch support.

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

This was our first time moving to a HCI storage solution.

How was the initial setup?

Setup was straightforward. With ESXi as the base, it was quite easy to then enable vSAN. We used the just a bunch of disks (JBOD) configuration and vSAN consumes those disks easily through the vCenter web GUI.

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

vSAN is not cheap. Weigh the benefits of a reduction in complexity against the cost.

Which other solutions did I evaluate?

We did not evaluate any other options.

What other advice do I have?

Use the GUI scripting vSAN implementation, at least for ESXi 6.0. We found that it was much quicker (and still fairly simple) to implement via the GUI. I’ve heard this may have gotten better in ESXi 6.5.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email