# Data Object - EntityResourceCheckDetails(vim.vsan.EntityResourceCheckDetails)

Extended by
  VsanDiskGroupResourceCheckResult, VsanDiskResourceCheckResult, VsanFaultDomainResourceCheckResult, VsanHostResourceCheckResult, VsanResourceCheckResult
Extends
  DynamicData
Since
  vSAN API 6.8.7

## Data Object Description

Details about the resource check result for a given entity. The result contains information of current and predicted usage the various resources, like capacity, for the entity. For example, for a host result contains current and predicted capacity usage and component counts.

Properties

Name | Type | Description
--- | --- | ---
additionalRequiredCapacity* | xsd:long | vSAN's recommendation for additional capacity for this entity to be added in order to make the operation succeed. This will be sum of all child entitie's additionalRequiredCapacity required. For example, host's additional capacity will be sum of all disk-group's additional capacity on the host.
capacity* | xsd:long | The total physical capacity of the entity in bytes. For example, host capacity will be sum of all disk-group's capacity on the host. If isNew is true, the currentUsage is set to 0 since this a recommendation for adding new resource.
components* | xsd:long | Predicted number of vSAN components on this entity post operation.
isNew* | xsd:boolean | The flag indicates whether this is a new resource entity that is recommended to be added for more resources in order to make the operation succeed. For example, for a disk group entity the flag indicates whether this is a new disk group that is recommended to be added for more resources in order to make the operation succeed.
maxComponents* | xsd:long | Number of maximum vSAN components this entity can hold.
name* | xsd:string | The friendly name for this entity. This is the name specified by user when the entity is created or updated.
postOperationCapacity* | xsd:long | The predicted total physical capacity of the resource entity in bytes after the operation is done. For example, if the resource check is for host enter maintenance mode operation the capacity which host was contributing will be removed from the fault domain's total physical capacity.
postOperationUsedCapacity* | xsd:long | The predicted physical usage of the resource entity in bytes after the operation is done. For example, if the resource check is for host enter maintenance mode operation, vSAN will simulate the disk usage after the given host enters maintenance mode. If vSAN deduplication and compression is enabled during the operation, vSAN simulation will not take this into consideration and thus will make a conservative estimation of the post-operation disk usage with data non-deduplicated and uncompressed. If vSAN deduplication and compression is disabled during the operation, vSAN simulation will use the average of current deduplication/compression rate of all disk-groups in the cluster to estimate the inflation of data for a rough calculation of the post-operation disk usage.
usedCapacity* | xsd:long | The current physical usage of the entity in bytes. If isNew is true, the currentUsage is set to 0.
uuid* | xsd:string | The vSAN UUID of the entity.
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="EntityResourceCheckDetails"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="name" type="xsd:string" minOccurs="0"/> <element name="uuid" type="xsd:string" minOccurs="0"/> <element name="isNew" type="xsd:boolean" minOccurs="0"/> <element name="capacity" type="xsd:long" minOccurs="0"/> <element name="postOperationCapacity" type="xsd:long" minOccurs="0"/> <element name="usedCapacity" type="xsd:long" minOccurs="0"/> <element name="postOperationUsedCapacity" type="xsd:long" minOccurs="0"/> <element name="additionalRequiredCapacity" type="xsd:long" minOccurs="0"/> <element name="maxComponents" type="xsd:long" minOccurs="0"/> <element name="components" type="xsd:long" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>