---
title: "State vs. Status"
description: "In Veeam technical documentation, we use state when talking about an overall condition of an entity or a result of some operation with the entity (such as Idle, Running, Disabled, Verified and so on), while status stands for the current condition..."
canonical: "https://helpcenter.veeam.com/docs/styleguide/tw/state.html"
breadcrumb: "Style Guide > Tips and Tricks > State vs. Status"
dateModified: "2026-09-03"
---

# State vs. Status

In Veeam technical documentation, we use **state** when talking about an overall condition of an entity or a result of some operation with the entity (such as *Idle*, *Running*, *Disabled*, *Verified* and so on), while **status** stands for the current condition of an entity with respect to particular circumstances (such as *Success*, *Failed*, *Warning* and so on).

### Examples

1. When the verification process is over, Veeam Backup & Replication removes the delta file of the VM replica snapshot, powers off the VM replica and creates a report on its [state]{.mdhl-correct}.
2. If the failover plan becomes inconsistent with the virtual environment, you can reset the current plan [state]{.mdhl-correct}. This operation returns the plan to the [*Disabled*]{.mdhl-correct} [state]{.mdhl-correct}.
3. If Veeam Backup & Replication fails to copy data for the full backup file during the first backup copy interval, it marks the job session as finished with the [*Warning*]{.mdhl-correct} [status]{.mdhl-correct}.
4. For every VM in the list, Veeam Backup & Replication checks the configuration database to obtain the date of the latest backup job session completed with the [*Success*]{.mdhl-correct} [status]{.mdhl-correct}.