# Data Object - VsanHostComponentSyncState(vim.vsan.host.VsanComponentSyncState)

Property of
  VsanHostVsanObjectSyncState
Extends
  DynamicData
Since
  vSAN API 6.7

## Data Object Description

This data object type describes sync state for a vSAN component.

Properties

Name | Type | Description
--- | --- | ---
bytesToSync | xsd:long | Indicates how many bytes need to be synced for this component.
diskUuid | xsd:string | Represents the uuid of disk on which component resides.
hostUuid | xsd:string | Represents the uuid of host on which component resides.
reasons* | xsd:string[] | The list of reasons indicate why the component went into syncing state. The API returns full list of reasons for background. However, sometimes it's userful to generate an aggregate reason, in which case the following priorities could be used: P0: "evacuate" P1: "dying_evacuate" P2: "rebalance" P3: "repair", "reconfigure" P4: "stale" See VsanSyncReason
recoveryETA* | xsd:long | The estimated time in seconds to complete recovery. This attribute will be not returned if no data has been synced.
uuid | xsd:string | Represents the uuid of component.
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="VsanHostComponentSyncState"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="uuid" type="xsd:string"/> <element name="diskUuid" type="xsd:string"/> <element name="hostUuid" type="xsd:string"/> <element name="bytesToSync" type="xsd:long"/> <element name="recoveryETA" type="xsd:long" minOccurs="0"/> <element name="reasons" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> </sequence> </extension> </complexContent> </complexType>