# Enum - VsanObjectHealthVsanObjectHealthState(vim.host.VsanObjectHealth.VsanObjectHealthState)

Since
  vSphere API 5.5

## Enum Description

The vSAN object health state enumeration.

Enum Constants

Name | Description
--- | ---
datamove | Objects in this state are fully compliant with their policy and are healthy, but vSAN is actively rebuilding them.
healthy | The object is in perfect condition, exactly aligned with its policy, and is not currently being moved or otherwise worked on.
inaccessible | An object has suffered more failures (permanent or temporary) than it was configured to tolerate, and is currently unavailable and inaccessible.
nonavailabilityrelatedincompliance | This is a catch all state when none of the other states apply. An object with this state is not compliant with its current policy, but is meeting the availablity (NumberOfFailuresToTolerate) policy. The object might be in this state because vSAN is not able to meet a non-availability related policy such as NumberOfDiskStripesPerObject because of lack of available resources. User need check the vSAN system resources like the number of fault domains and hosts, free capacity to make it compliant.
nonavailabilityrelatedincompliancewithpausedrebuild | Since vSAN API vSAN 6.7U3
nonavailabilityrelatedincompliancewithpolicypending | Since vSAN API vSAN 6.7U3
nonavailabilityrelatedincompliancewithpolicypendingfailed | Since vSAN API vSAN 6.7U3
nonavailabilityrelatedreconfig | The object is fully in compliance with the NumberOfFailuresToTolerate policy and the data movement is to satisfy another policy change.
reducedavailabilitywithactiverebuild | The object has suffered a failure, but it was configured to be able to tolerate the failure.
reducedavailabilitywithnorebuild | The object has suffered a failure or its policy was recently changed to have higher availability requirement but vSAN was able to tolerate it. The object is accessible and I/O is flowing.
reducedavailabilitywithnorebuilddelaytimer | The object has suffered a failure, but vSAN was able to tolerate it. However, vSAN is not yet working on re-protecting the object, as it is waiting for the 60-minute (default) delay timer to expire before issuing the re-protect.
reducedavailabilitywithpausedrebuild | Since vSAN API vSAN 6.7U3
reducedavailabilitywithpolicypending | Since vSAN API vSAN 6.7U3
reducedavailabilitywithpolicypendingfailed | Since vSAN API vSAN 6.7U3
remoteAccessible | Since vSAN API vSAN 7.0U1
VsanObjectHealthState_Unknown | Since vSAN API vSAN 6.7U3

Show WSDL type definition
<simpleType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanObjectHealthVsanObjectHealthState"> <restriction base="xsd:string"> <enumeration value="inaccessible"/> <enumeration value="reducedavailabilitywithnorebuild"/> <enumeration value="reducedavailabilitywithnorebuilddelaytimer"/> <enumeration value="reducedavailabilitywithactiverebuild"/> <enumeration value="datamove"/> <enumeration value="nonavailabilityrelatedreconfig"/> <enumeration value="nonavailabilityrelatedincompliance"/> <enumeration value="healthy"/> <enumeration value="reducedavailabilitywithpolicypending"/> <enumeration value="reducedavailabilitywithpolicypendingfailed"/> <enumeration value="reducedavailabilitywithpausedrebuild"/> <enumeration value="nonavailabilityrelatedincompliancewithpolicypending"/> <enumeration value="nonavailabilityrelatedincompliancewithpolicypendingfailed"/> <enumeration value="nonavailabilityrelatedincompliancewithpausedrebuild"/> <enumeration value="remoteAccessible"/> <enumeration value="VsanObjectHealthState_Unknown"/> </restriction> </simpleType>