For the second year I’ve been selected “EMC Elect 2015”. Like my previous post on being selected VMware vExpert, being named EMC Elect 2015 validates that the little bit I contribute to the EMC and VMware community matters and that I’ll continue making the effort. Click on the blue box for the full EMC Elect 2015 list:
Recently, with the announcement of the availability of VVols in vSphere.NEXT I was asked to give a deep dive presentation to a customer with a focus on what VVols meant for protection VM’s. While at EMC as a vSpecialist I lead a group focused on protecting VM’s so this is something I’ve been interested in for awhile. I’m a big fan of RecoverPoint and am excited about virtual RecoverPoint’s ability to offer continuous data protection for VSAN as I indicated here. I’m also a huge fan of VPLEX and spent a lot of time during my days at EMC discussing what it could do. The more I dug into what VVols could do to help with various VM movement and data protection schemes the more I realized there was much to be excited about but also much need for clarification. So, after some research, phone calls, and email exchanges with people in the know I gathered the information and felt it would be good information to share.
What follows is kind of a “everything but the kitchen sink” post on various ways to move and protect VM’s. There were several pieces of the puzzle to put together so here are the past, present, and future options.
XvMotion (Enhanced vMotion) – vMotion without shared storage – Released in vSphere 5.1
In vSphere 5.1 VMware eliminated the shared storage requirement of vMotion.
- vMotion – vMotion can be used to non-disruptively move a VM from one host to another host provided both hosts have access to the same shared storage (i.e. A datastore backed by a LUN or volume on a storage array or shared storage device). Prior to vSphere 5.1 this was the only option to non-disruptively move a VM between hosts.
- Storage vMotion – this allows VM vmdk’s to be non-disruptively moved from one datastore to another datastore provided the host has access to both.
- XvMotion – As of vSphere 5.1. XvMotion allows a VM on one host, regardless of the storage it is using, to be non-disruptively moved to another host, regardless of the storage it is using. Shared storage is no longer a requirement. The data is moved through the vMotion network. This was a major step towards VM mobility freedom, especially when you think of moving workloads in and out of the cloud.
- For more information see: Requirements and Limitations for vMotion Without Shared Storage
Cross-vCenter vMotion – Announced at VMworld 2014, available in vSphere.NEXT (future release)
This new feature was announced during the VMworld 2014 US – General Session – Tuesday.
One of the big topics at VMworld 2014 was VVols. VMware announced it will be part of the next release of vSphere and almost every storage vendor on the planet is excited about the benefits that VVols bring. I was working the VVol booth at VMworld and had the pleasure of being interviewed by VMworld TV to discuss the comparison between VSAN and VVols. This was fun but unscripted and off the cuff so here it is:
VMworld TV Interview: Peter Keilty of VMware Discussed Virtual Volumes
What I’m trying to say is:
- VSAN is the first supported storage solution takes advantage of VVols.
- VVols, in vSphere.NEXT, will work in conjunction with VASA to allow all block and file based storage arrays to fully realize the benefits of Storage Policy Based Management (SPBM).
- Each storage vendor can write a VASA/VVol provider that registers with vCenter to integrate with the vSphere API’s and promote their storage capabilities to vCenter. I expect just about every storage array vendor to do this. I have seen VVol demonstrations by EMC, NetApp, Dell, HP, and IBM.
- VVols eliminates the requirements of creating LUNs or Volumes on the arrays, instead, arrays present a pool or multiple pools of capacity in the form of storage containers that the hosts in the cluster see as datastores
- Through SPBM, administrators can create different service levels in the form of policy that can be satisfied by the underlying storage provider container.
- When VM’s get provisioned, they get assigned to a policy, and their objects (namespace, swap, vmdk’s, snap/clones) get placed as native objects into the container in the form of VVols.
- You can even assign objects from the same VM to different policy to give them different service levels, all potentially satisfied by the same storage provider or perhaps different provider containers. In other words, a vmdk for an OS image might want dedupe enabled but a vmdk for a database might not want dedupe but might want cache acceleration. Different policy can be set and each object can be assigned to the policy that will deliver the desired service level. The objects could be placed into the same storage array pool but taking advantage of different storage array features. And these can be changed on the fly as needed.
Like all the storage vendors out there, I’m very excited about the benefits of VVols. For a full description and deep dive check out this awesome VMworld session by Rawlinson Rivera (http://www.punchingclouds.com/) and Suzy Visvanathan:
Virtual Volumes Technical Deep Dive
I’m really looking forward to attending VMworld 2014 in a few weeks. Its a great time to catch up with friends and meet new ones. For me the week kicks off on Thursday at the VMware SE Tech Summit. Then vOdgeball on Sunday afternoon with a team of former EMC vSpecialists. This is a great event to help out a great cause, the Wounded Warrior Project. We’ll also be honoring our two vSpecialist friends, Jim Ruddy and Stephen Hunt, that were recently involved in a tragic accident. Then the main event starts Sunday night. It should be fun and exhausting.
Virtual SAN (VSAN) is sure to be one of the highlights of the show.
I’m often asked how to protect Virtual SAN (VSAN). Its simple, any product focused on protecting a virtual machine (VM) will work for protecting VM’s sitting on a VSAN enabled vSphere cluster. VMware offers VDP/VDPA for backup & recovery and there are many other VMware partners with backup & recovery solutions focused on protecting VM’s. Backup & Recovery is a great way to protect data but some customers like the benefit of more granular recovery points that comes from data replication either locally or to a disaster recovery site.
To protect VSAN data in a primary site to a remote disaster recovery site VMware offers vSphere Replication (VR) to replicate the VM data sitting on a VSAN Datastore over the DR site. Of course Site Recovery Manager (SRM) is supported to automate failover, failback and testing. The VR/SRM combined solution can also be used for planned data center migrations. Here are a few great write-ups on the topics:
One of the main benefits of VR is that it will work to replicate VM data on any storage to another site with hosts connected to any other storage. So, VSAN can be the source, the target, or both.
vSphere Replication can be set to asynchronously replicate every day, hour, or up to every 15 minutes. Thus providing a Recovery Point Objective (RPO) of up to 15 minutes. For many customers, this is “good enough”. For some customer workloads, asynchronous replication is not “good enough”. They need synchronous replication protection and there are several solutions in the market. One that I’ve been a big fan of for a long time is EMC’s RecoverPoint which has a great reputation for protecting enterprise mission critical data and applications. Essentially it splits every write transaction, journals it, and synchronously makes a copy of it either locally or to a remote DR site without impacting application performance. Of course there are more details but this is essentially what it does which results in being able to recover back to any point in time. Often it’s labeled as “Tivo or DVR for the data center”. One other benefit of RecoverPoint is it can replicate data from any storage to any storage, as long as there is a splitter for the storage. EMC VNX and VMAX storage arrays have splitters built in.
The big news that just came out last week that peeked my interest is that EMC is now offering a Beta of a completely software based RecoverPoint solution that embeds the splitter into vSphere. This brings the RecoverPoint benefits to any VMware customer running VM’s on any storage: block, file, or of course even VSAN. The EMC initiative is call Project Mercury and for more information check out:
I’m excited that VSAN customers will have a choice for data protection, asynchronously with 15 minute RPO using vSphere Replication or continuous, synchronous, and asynchronous with EMC’s Virtual RecoverPoint.
Over the past few months I’ve had the pleasure of speaking to the various EMC SE teams in the North East and Mid-Atlantic regions. Since VSAN is now GA, its important to understand where VSAN fits in the market compared to EMC solutions. I should point out that I’d be happy to have the same conversation with other storage vendors. That’s the beauty of the “Federation” between EMC II, Pivotal, VMware, and RSA. Each individual company is free to work with the competitors of the other members of the federation. But, they also want to make sure they work with each other as closely as anyone. Kind of like when VMware opened up the API’s to vSphere and EMC made sure they were the most integrated with them… so EMC is now making sure their SE’s are the most up to date on VMware’s latest storage offerings. VSAN is a great solution, I’m am swamped with customer requests to hear more about it, but it is not necessarily going to replace all storage solutions in a data center for all workloads. Customers are identifying use cases that fit best for them where VSAN offeres better cost/performance/operational benefits. The VSAN message has been well received by the EMC teams and I look forward to working closely together.
On that note, I’m attending EMC World 2014 this week. The VMware VSAN team is setting up a Hands On Lab where you can get your hands on the technology. Chuck Hollis has the details here:
I wanted to make sure you know where to go so here’s the map to the location.
Also, here’s a link to the Chromebooks that we’ll be using and then giving away at Wednesday night.
Looking forward to seeing you all there.
This session will be all day on Saturday 2/8/2014 starting at 8:30AM. I will be presenting the SDDC and VSAN overview as well as the vSphere Flash Read Cache Technical Presentation. The technical deep dive on VSAN will be presented by Wade Holmes and a few other guest speakers. Wade has authored a couple of the Hardware Configuration guidance blogs on SSD and IO Controllers and has been feverishly testing VSAN in all sorts of configurations in preparation for product launch. I’m excited about the technical depth that Wade will go into and know our partners will get a ton of good information out of this session. In addition, one of our engineers, Joe Cook, has been working with a bunch of customers to implement VSAN. He will share the processes he’s been using for Proof of Concepts as well as present how to monitor and troubleshoot VSAN. As a bonus, he’ll share a new tool that we’ve developed to help our partners analyze customer environments in preparation for VSAN and other VMware technologies.
This session will be all day Monday 2/10/2014 starting at 8:30AM. Prior to my current position as a Software Defined Storage SE for VMware I was an EMC vSpecialist for almost 4 years. So this session is near and dear to my heart. I just sat through the EMC Elect PEX planning concall and saw the full agenda for this one. Lots of great presenter’s including of course Chad Sakic, Jason Nash, Aaron Chaisson, Rob Peglar, Brian Whitman, and others. Chad will kick things off but you’ll need to download the NDA form from the PEX schedule builder and bring the signed copy in order to get into the session.