5. vCloud Resource Design : 5.10 Storage Independent of Virtual Machines : 5.10.2 Design Considerations
   
5.10.2 Design Considerations
Independent disk limitations and usage considerations:
*Only SCSI controller types are supported.
*The disk size counts against the organization virtual datacenter quota.
*If the class of storage is not specified, the organization virtual datacenter default is used.
*If you delete a virtual machine, the independent disk first gets detached from the virtual machine.
*When exporting a virtual machine with an independent disk, the disk is not tagged in any way to identify that its source was an independent disk.
*The following operations cannot be performed if the virtual machine currently has an attached independent disk:
*Clone vApp.
*Copy vApp VM.
*Capture vApp to Catalog.
*Move VM.
*Change owner.
*When using the elastic virtual datacenter feature and allowing a provider virtual datacenter to span multiple clusters, it may be necessary to move an independent disk to a different datastore if it is necessary to attach it to a virtual machine in a different cluster. This move can be avoided by using the locality argument to create a disk in the same cluster as the virtual machine to which it will be attached (not necessarily on the same datastore).
*Performance and ScalabilityThe scalability maximum for this feature is one independent disk per virtual machine up to vCloud Director 5.1 maximum number of virtual machines.