Section 6 Orchestration & Disaster Recovery

• Orchestrator Server service: manages orchestration plans, users and roles.
• Orchestrator Web UI: the main interface.
• Embedded Veeam ONE: VRO uses it for inventory and resource groups.
• Connected VBR servers do the actual failover and restores. VRO automates and documents them.
• A SQL Server database stores the configuration.

• Replica plan · Recovers from: Veeam replicas (needs a replication job in VBR)
• CDP replica plan · Recovers from: Veeam CDP replicas
• Restore plan · Recovers from: Backups (needs a backup or backup copy job) into vSphere, at the original or an alternate location
• Cloud plan · Recovers from: Backups restored as VMs in Azure
• Storage plan · Recovers from: Replicated storage snapshots (NetApp, HPE)

Building a plan: scope → plan type → recovery location (restore plans) → inventory groups → VM recovery options → plan steps (built-in steps plus custom PowerShell steps) → credentials → target RTO and RPO → report template → report schedule.

• Readiness check: fast and low-impact. Confirms the plan's configuration matches the DR environment and that restore points meet the target RPO. Runs automatically every day for enabled plans, or on demand.
• DataLab test: actually recovers the plan's VMs into an isolated DataLab and runs the plan steps. On demand, or scheduled with the Lab Calendar.
• Running a plan: Run, Schedule, Halt (stop mid-run) and Reset (clear the state so it can run again).
• Replica plans: Failover → then Undo failover, or Failback → Commit failback / Undo failback.

• A DataLab is VRO's view of a VBR virtual lab, with a one-to-one link. Build the virtual lab in VBR first.
• SureBackup labs: verification of recoverability.
• Sandbox: an on-demand isolated copy of production for dev/test, patch testing or security analysis.
• Automated testing: scheduled plan tests through the Lab Calendar.

• Plan Definition · When it is produced: Describes the whole plan. Updated automatically every day for enabled plans.
• Plan Readiness Check · When it is produced: After each readiness check
• DataLab Test · When it is produced: After each test, with per-VM results and timing
• Plan Execution · When it is produced: After a real run (failover or restore)

Reports come from a Word template. Clone and edit it to add your logo or text. They serve as compliance and audit evidence that DR was tested and works.