VMware Inc.'s latest release, vSphere 4.0, offers the vStorage APIs for Data Protection, which were added to vSphere 4.0 to improve the efficiency of data backups. Eric Siebert, an IT industry expert focusing on virtualization and author of the website VMware-land.com, discusses vStorage APIs in this Q&A. His answers are also available as an MP3 below.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Table of contents:
>> What are the main features of VMware vStorage APIs for Data Protection?
>> How is VMware vStorage APIs for Data Protection different from VMware Consolidated Backup and other virtual machine backups?
>> What are the benefits of using APIs in your data backup environment?
>> Are there any cons to using vStorage APIs?
>> Are there any things that you need to look out for or keep in mind when using vStorage APIs?
>> What does the future look like for vSphere?
The vStorage APIs for Data Protection are new in vSphere. They consist of a group of sub-APIs that are the vStorage APIs for array integration for multitasking, Site Recovery Managers and data protection. vStorage APIs for Data Protection are particularly valuable to data backup and replication applications. The VCB model has to access virtual machine (VM) data through a proxy server to get to the data, but vStorage APIs allow direct integration with vSphere so you can access the data directory without going through a third party.
There are also a lot of new features in vStorage APIs for Data Protection. Changed Block Tracking (CBT) is one significant feature in vStorage APIs because it allows the VMkernel to track the disk blocks that change. So a backup or replication application that wants to see what has changed since the last backup or replication simply queries the vStorage APIs for Data Protection to find out exactly what blocks have changed. The VMkernel keeps track of that, so it quickly provides the blocks that need to be backed up in incremental backups. That itself greatly improves the time of incremental backups and replication.
There are some other features in the vStorage APIs for Data Protection that allow for things like directly accessing disk and for hot adding disk, which can both increase the efficiency of backup applications.
The main benefits of using APIs in your data backup environment are that you get direct integration. You don't actually have to go through other layers or other methods to get to the data that's inside the virtualization layer. The APIs allow for the backup vendors that write the applications to directly interface with the virtualization layer and to make calls and queries to that layer to access the virtual disks. The vStorage APIs offer several benefits over other virtual machine backup methods. It takes out extra layers that exist from some of the unconventional methods some people use to get to a virtualization layer, and it allows the backup applications to directly interface with vSphere without going through another application or utility.
The vStorage APIs are particular to certain vendor integrations, so you need to watch out for that. For example, with the Site Recovery Manager (SRM) APIs, each vendor has to develop their own site recovery adapter that's specific, and has to be approved by VMware to be included in vStorage APIs. So, each vendor for some of the vStorage APIs has to develop their own type of integration and get it approved by VMware. In other words, you need to make sure that the vendor that you're dealing with has an approved integration from VMware to access what they're trying to get to at the vStorage APIs.
For the vStorage Data Protection APIs, there aren't any major things you need to keep in mind. As I mentioned earlier, the Change Block Tracking feature is probably one of the biggest things used in the Data Protection APIs, and that feature is more universal. Any backup vendor can make a call to that VMkernel and get the blocked changed data. But make sure you check with your vendor. Different vendors offer different support for vStorage APIs. For example, some vendors like Veeam are fully integrated and use all the available capabilities of vStorage APIs for Data Protection. Other vendors have been slower and integrated their products to take full advantage of only some of the features offered. So when looking up vendors you might want to check out their level of integration with APIs and see if they're taking advantage of all of its features.
It looks great. VMware has put a lot of effort into improving their product and staying ahead of the competition by adding all sorts of features, specifically for the vStorage APIs. The next release of vStorage APIs is based on array integration that allows for storage hardware to offload some of the paths that are normally handled inside of the VMkernel. The next release will allow for a lot of vStorage APIs for integration to emerge and be available for use. A lot of operations that are time consuming on the VMkernel will be offloaded to storage and be a little more efficient.
Overall, VMware is doing a good job of improving all areas of its product, especially when it comes to automation, management and trying to make their whole package as much of a cloud-friendly offering as they can. So I think this next release of vSphere will have a lot of great new features. Beyond that, I except to see more great things come out of VMware for vSphere.