VPLEX and vSphere 6, Can They Live Peacefully Together?

I believe in stupid questions.  They are born from a lack of knowledge and can’t we all relate to that?  For instance, a coworker recently asked me: “With VMware’s vSphere 6 coming out, how does that change things for VPLEX?” To which I replied, “Not much.” Because when you ask a stupid question, the person who answers is allowed to be deliberately obtuse.  That’s a rule I just made up.unlikely friend

The real answer is that, really, not much changes.  There were three big items that launched with vSphere 6.  Here is a brief overview:

  • New Fault Tolerance – New changes include support for more CPUs and RAM, the move to two separate VMDKs vs a single shared VMDK, and lack of vMSC support
  • VVOL – A brand new approach to VM storage that allows storage arrays and data services to be managed from vSphere on a per VM basis
  • Long Distance vMotion – New vMotion modes and technologies now allow the movement of VMs over long distances between separate vSphere clusters

Like I said before, not much really changes with vSphere 6 and VPLEX.  VVOL support is baking, FT is local only, and LD vMotion support is so limited that your only option is the VMware solution.  For VPLEX the focus continues to be on the benefits gained by using VPLEX Local or VPLEX Metro with your vSphere environment.  Those of you who have VPLEX today know the enormous value of having native VMware HA and VPLEX Continuous Availability protection.  For those of you who don’t…  Isn’t there someone you can talk to about that? I know, stupid question.

To get the in depth scoop on VPLEX and vSphere 6 visit the VSPEX community and read the full blog.

About the Author: Cody Garvin