# Data Object - DatastoreCapability(vim.Datastore.Capability)

Property of
  Datastore, VirtualMachineDatastoreInfo
Extends
  DynamicData
Since
  2.0

## Data Object Description

Information about the capabilities of this datastore.

Properties

Name | Type | Description
--- | --- | ---
clusteredVmdkSupported* | xsd:boolean | Indicates whether the datastore supports clustered VMDK feature. Since vSphere API 7.0
directoryHierarchySupported | xsd:boolean | Indicates whether or not directories can be created on this datastore.
nativeSnapshotSupported | xsd:boolean | Indicates whether the datastore supports native snapshot feature which is based on Copy-On-Write. Since vSphere API 5.1
perFileThinProvisioningSupported | xsd:boolean | Indicates whether or not the datastore supports thin provisioning on a per file basis. When thin provisioning is used, backing storage is lazily allocated. This is supported by VMFS3. VMFS2 always allocates storage eagerly. Thus, this value is false for VMFS2. Most NAS systems always use thin provisioning. They do not support configuring this on a per file basis, so for NAS systems this value is also false.
rawDiskMappingsSupported | xsd:boolean | Indicates whether or not raw disk mappings can be created on this datastore.
seSparseSupported* | xsd:boolean | Indicates whether the datastore supports the Flex-SE(SeSparse) feature. Since vSphere API 5.5
storageIORMSupported | xsd:boolean | Indicates whether the datastore supports Storage I/O Resource Management. Since vSphere API 4.1
topLevelDirectoryCreateSupported* | xsd:boolean | Indicates whether the datastore supports traditional top-level directory creation. See DatastoreNamespaceManager Since vSphere API 5.5
upitSupported* | xsd:boolean | Deprecated. As of vSphere API 8.0, and there is no replacement for it. Indicates whether the datastore supports the upit feature. Since vSphere API 6.5
vmdkExpandSupported* | xsd:boolean | On certain datastores (e.g. 2016 PMEM datastore) VMDK expand is not supported. This field tells user if VMDK on this datastore can be expanded or not. If value is undefined, then it should be read as supported. Since vSphere API 6.7
vmfsSparseSupported* | xsd:boolean | Indicates whether the datastore supports the vmfsSparse feature. True for VMFS3/VMFS5/NFS/NFS41, False for VMFS6. If value is undefined, then it should be read as supported. Since vSphere API 6.5
vsanSparseSupported* | xsd:boolean | Indicates whether the datastore supports the vsanSparse feature. Since vSphere API 6.5
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="DatastoreCapability"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="directoryHierarchySupported" type="xsd:boolean"/> <element name="rawDiskMappingsSupported" type="xsd:boolean"/> <element name="perFileThinProvisioningSupported" type="xsd:boolean"/> <element name="storageIORMSupported" type="xsd:boolean"/> <element name="nativeSnapshotSupported" type="xsd:boolean"/> <element name="topLevelDirectoryCreateSupported" type="xsd:boolean" minOccurs="0"/> <element name="seSparseSupported" type="xsd:boolean" minOccurs="0"/> <element name="vmfsSparseSupported" type="xsd:boolean" minOccurs="0"/> <element name="vsanSparseSupported" type="xsd:boolean" minOccurs="0"/> <element name="upitSupported" type="xsd:boolean" minOccurs="0"/> <element name="vmdkExpandSupported" type="xsd:boolean" minOccurs="0"/> <element name="clusteredVmdkSupported" type="xsd:boolean" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>