Datastore Get Capability
Capabilities of this datastore.
The unique identifier for the managed object to which the property attaches; the serialized managed object reference for a request has the form moType/moId
, in this case Datastore/{moId}
.
The vSphere release schema. The current specification covers vSphere 8.0.3.0 APIs.
OK
{
"_typeName": "string",
"directoryHierarchySupported": false,
"rawDiskMappingsSupported": false,
"perFileThinProvisioningSupported": false,
"storageIORMSupported": false,
"nativeSnapshotSupported": false,
"topLevelDirectoryCreateSupported": false,
"seSparseSupported": false,
"vmfsSparseSupported": false,
"vsanSparseSupported": false,
"upitSupported": false,
"vmdkExpandSupported": false,
"clusteredVmdkSupported": false
}
Indicates whether or not directories can be created on this datastore.
Indicates whether or not raw disk mappings can be created on this datastore.
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.
Deprecated as of vSphere8.0 U3, and there is no replacement for it.
Indicates whether the datastore supports Storage I/O Resource Management.
Indicates whether the datastore supports native snapshot feature which is based on Copy-On-Write.
Indicates whether the datastore supports traditional top-level directory creation.
See also DatastoreNamespaceManager.
Indicates whether the datastore supports the Flex-SE(SeSparse) feature.
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.
Indicates whether the datastore supports the vsanSparse feature.
Deprecated as of vSphere API 8.0, and there is no replacement for it.
Indicates whether the datastore supports the upit feature.
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.
Indicates whether the datastore supports clustered VMDK feature.