vStorage API Spreads Its WingsThe goal for VMware is to virtualize as much of the data center as possible. This goal can only be reached by increasing virtual machine (VM) density per physical server. The roadblock to high VM density per host is storage performance and data protection. Much of the focus of VMworld was addressing those issues through more vendors adopting the use of the vStorage API set.
The goal for VMware is to virtualize as much of the data center as possible. This goal can only be reached by increasing virtual machine (VM) density per physical server. The roadblock to high VM density per host is storage performance and data protection. Much of the focus of VMworld was addressing those issues through more vendors adopting the use of the vStorage API set.VMware's vStorage API set now has three basic integration points; backup integration, array integration and replication integration. We will cover the first two in this entry and deal with replication and disaster recovery later. From a backup perspective the API allows a backup application to get block level access to VMDK files, meaning that incremental, image level backups of VMs can happen in minutes. This can be done with a single application now, not an application talking to another application as was the case with VMware's VCB. The result is a greatly simplified backup scenario.
The vStorage API provides the ability to revolutionize backups in the data center. The entire model of backups can now change from one of dealing with millions upon millions of files to dealing with a few hundred server images, all being backed up at a changed block level. The various software applications will vary and compete in how they store and manage those blocks of data, but the days of dealing with millions of individual files per server may be over. Several vendors have gone so far as to add components to their software that allows converts of physical machines to VMs just for the purpose of backing them up.
There is also the updated vStorage API support that is focused on array integration. As we discussed in our recent article "A Case For Block Storage in Virtual Environments" block based storage is still the dominant storage type in VMware environments. And the vStorage API allows those arrays to enhance the environment even further. Arrays that support the vStorage API that was updated with the 4.1 version of vSphere can take the load off of the hypervisor and allow the array to do more through the array hardware. The key components of array integration are Block Zero, Full Copy and Hardware Assisted Locking.
Block Zero is the ability to pre-zero out block level write operations to the storage hardware. This is typically what happens when thick VM images are created. This will improve the speed at which VMs are created. Full Copy provides the ability for the storage hardware to handle large data moves or copies of VM images. Instead of reading the entire VMDK up to the host and then writing through the host to another volume, the array can now handle that and offload all that work from the hypervisor.
Finally Hardware Assisted Locking reduces the chances of a VM gone wild and locking out the VMFS LUN from all the other VM's dependent on that LUN by better controlling SCSI reservation contention. Larger environments have run into situations where an operation that locked a VMFS LUN did not complete and all the I/O for all the VMs using that LUN froze. Not good. What the array integration component of the vStorage API does is provide the ability to lock or reserve data areas but to do so on a much finer grain instead of the entire LUN. As a result if there is a frozen operation, a smaller portion of the environment is impacted.
As is the case with any API set, to see the data protection or array integration benefits vendors have to decide to support these capabilities within their products. This support can be at different levels so it will require more than just saying they support it. You will also need to understand how the support is being enabled and what the impact of that support is. For example shifting workloads off of the storage array is great as long as the array has the horsepower to handle that workload.
Track us on Twitter: http://twitter.com/storageswiss
Subscribe to our RSS feed.
George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.