USP-v and USP-VM supports VMWare vStorage API with VMWare vStorage API for Array Integration

On May 3rd 2011 Hitachi Data Systems announced the availability of support for VMWare's vStorage API with VAAI on the USP-V and USP-VM. The long awaited update that was already available on the VSP and AMS2000 series has now been included in USP-V and USP-VM microcode 60-08-01 and higher.

If you have VMWare (and who doesn't these days) this is a very welcome addition to the large set of functionality the USP-V(M) already has. One of the best things with this part is that, as with the VSP, instantaneous support for external storage array who natively do not support VAAI is also included. So if you have a storage array which is on the supported external storage list for the USP-V(M) you can use VAAI for that side as well. This list currently extends to over a 100 array type from numerous vendors.

The only thing you need is an upgrade to MC 60-08-01 or higher + VMWare vSphere 4.1 and you're good to go.

So what does it support:
Full Copy: this enables the storage system to offload all data intensive IO from the host. This means that for cloning of VM's the ESX host does not need to read and write data back and forth to the array.

Block zeroing:
Improves provision speed and flexibility as well as a more effective use of thin provisioning. When a VM is configured with eagerzerothick policy and it is copied or cloned to a TP pool it immidiatly becomes thin. This allows for far better use of available space on the array.

Hardware Assisted Locking:
In previous version when a lot of VM's were deployed on a VMFS datastore all storage related operations like cloning, vMotion, addition and removal of VM's etc required the ESX host to set a SCSI reserve on the entire LUN. This prevented other VM's from doing similar tasks and sometimes resulted in conflicts. The VM kernel has been modified so that in conjunction with the new MC on the USP-V(M) only the meta data of those VM's who require this exclusive lock are affected.

What currently is not included yet is Thin-provisioning STUN and UNMAP support but it seems this will be around later this year.

So what do yo need? An active maintenance agreement with HDS and vSphere 4.1 and you're good to go.

If you have storage arrays who do not support VMWare vStorage API with VAAI but want to enable that have a look at http://www.hds.com/products/storage-systems/specifications/supported-ext... to see if they are supported to be attached to the USP-V(M)

The HDS solution pages for VMWare are located here http://www.hds.com/go/vmware

For more information around VAAI check out VMWare's website over here http://www.vmware.com/products/vstorage-apis-for-array-integration/ or http://kb.vmware.com/self service/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021976