- vSphere APIs for Storage Awareness (VASA)
- Virtual Volumes (vVOL)
When in use vVOL VMDK's are bound to a host. Under certain circumstances it is possible that the host never releases the active binds, for example, if the host fails due to a hardware error. In this case a deletion of the vVOL VMDK will fail with error:
FINAL FAILURE deleteVirtualVolume, error (RESOURCE_BUSY / Caused by: volume of naa.xyz was still bound to X handles and cannot be deleted.