How a plan's state shows its readiness and its mode shows what it is doing.
From Ultra Transcenders VRO-13 by Tony Rough (coming January 2027)
Every recovery plan has a state, which shows what has happened to it, and a mode, which controls what can be done with it. Most operational decisions in Orchestrator start from these two values.
A plan shows one of three default states after creation, after a reset, and after a test or check completes. The State column is a rollup of readiness check, DataLab test and (for most plan types) malware scan results.
| Default state | Meaning |
|---|---|
| NEEDS VERIFIED | The plan has never been tested, never passed a readiness check, or has changed since the last DataLab test or readiness check |
| NOT VERIFIED | The plan failed a test, a readiness check or a malware scan |
| VERIFIED | The plan was tested successfully or passed a readiness check or malware scan |
For cloud plans, which cannot be tested in a DataLab, the default states refer only to readiness checks and malware scans. For storage plans, which cannot be scanned for malware, they refer only to tests and readiness checks.
When processing finishes, a plan settles into a stable state. Each successful stable state can also be reached with warnings or with errors (shown by the icon).
| Plan type | Stable states after processing | Testing state |
|---|---|---|
| Replica and CDP replica | HALTED, FAILOVER, UNDO FAILOVER, PERMANENT FAILOVER, PREPARE FOR FAILBACK, FAILBACK, UNDO FAILBACK, COMMIT FAILBACK | TESTING HALTED |
| Restore | HALTED, RESTORED | TESTING HALTED |
| Storage | HALTED, FAILOVER, UNDO FAILOVER | TESTING HALTED |
| Cloud | HALTED, RESTORED | None (no DataLab testing) |
While work is in progress, a plan shows an active state. These fall into three groups:
A plan that is being executed or tested is locked. If VMs are added, deleted or renamed, or Veeam ONE Business View groups change, Orchestrator does not apply those changes to a locked plan; they take effect only when the plan returns to VERIFIED, NEEDS VERIFIED or NOT VERIFIED.
| Mode | What the plan is ready for | Restrictions |
|---|---|---|
| ENABLED | Verify (readiness check), test, scan and execute | Editing not available; automatic report updates enabled |
| DISABLED | Edit, test and scan | Scheduled execution not available; automatic report updates disabled |
| IN-USE | Plan is in an active state (other than EDITING) or a stable state | Editing not available; automatic report updates disabled |
For cloud plans, ENABLED means ready to be verified, scanned and executed, and DISABLED means ready to be edited and scanned. For CDP replica plans in IN-USE mode, both editing and disabling are unavailable.
Common trap: Expecting to edit an ENABLED plan because it is “ready” - editing is available only in DISABLED mode; an ENABLED plan is ready to be checked, tested, scanned and run, but must be disabled before it can be changed.
This note is one section of Ultra Transcenders VRO-13: Veeam Recovery Orchestrator 13, an independent study guide that explains every topic the course covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to the Veeam Help Center.
Due on Amazon in January 2027, in Kindle and paperback editions.
About the book · VRO-13 terms in the glossary · All VRO-13 study notes
Replica, CDP replica, restore, storage and cloud plans: what each recovers from and where.
What each Orchestrator role can and cannot do, and why building and running plans are separate.
What a readiness check verifies, how often it runs and what it costs compared with a DataLab test.
How the embedded backup server restores and fails over in a clean room when production is lost.