Veeam · Software · YoctoIT tech page

Orchestrator

DR as a documented process: recovery plans executed and TESTED automatically, with the report as the evidence.

FOCUS · THE PLAN THAT TESTS ITSELFExecutable runbooks and scheduled tests: disaster recovery with automatic dress rehearsals
Request the Free Assessment Learn more
YoctoIT material for clients and partners · Veeam, Kasten, Coveware and the other products mentioned are trademarks of Veeam Software.
01 · What it is

Recovery Orchestrator, made clear.

Recovery Orchestrator turns the DR plan from a document into software: the runbooks define order, scripts and verifications; the execution is one click (or a trigger); and above all the TESTS run by themselves, in an isolated bubble, generating the compliance report. The declared RTO becomes a measured number, with a signature.

Runbook
the executable plan: order, scripts, verifications — not a PDF
Auto-test
the rehearsals scheduled in an isolated environment: the DR commissioned every month
Report
the documentation generated at every test: the evidence always fresh
Recovery Orchestrator
OFFICIAL VEEAM BRANDING · ORCHESTRATOR
CONSOLE REALE · RECOVERY ORCHESTRATOR · FONTE: VEEAM
REAL CONSOLE · RECOVERY ORCHESTRATOR · SOURCE: VEEAM
02 · How to use it well

The things that make the difference.

The cycle

The DR plan per applicationwhat restarts, in what order
Orchestration
Tests in a bubble
Reports & compliance
executes · tests · proves
From backups or from replicasthe two ways to restart
RTO/RPO measuredthe real numbers, not declared
The DR that trains itself

Plans per application

Not 'the VMs' but 'the ERP': groups, dependencies and application checks in the runbook.

Monthly tests in a bubble

The rehearsal without touching production: the deadline in the calendar, the report in the archive.

Assisted real cutovers

When it's really needed, the orchestrator executes and we stand watch: the hard night, together.

The compliance dossier

RTOs measured and tests signed: the NIS2 audit with the folder ready.

03 · In depth

DR as an executable document

Recovery Orchestrator turns the DR plans into automation: the plans (replica failover, restore from backup, or CDP) define sequences, dependencies and application checks (the script that verifies the DB responds), the DataLab runs the scheduled rehearsals without touching production, the documentation (actual RPO/RTO, test outcomes) generates itself: the NIS2/ISO audit has the evidence, the plan doesn't age in the drawer.

  • Piani eseguibili — the runbook you launch, not read: the human error out
  • Verifiche applicative — not 'the VM is on' but 'the application responds'
  • DataLab — the rehearsals in an isolated bubble, scheduled: the DR tested at night
  • Docs automatiche — RPO/RTO measured and minuted: the evidence writes itself
  • Orchestrated restore — from the pure backup too: DR without replication infrastructure
  • Ruoli — who can launch what: the failover governed
04 · Numbers and lifecycle

The numbers that matter.

1-click
the orchestrated failover
mensile
the automatic rehearsal possible: far more than once a year
RTO
measured at every test, not estimated
audit
reports ready for NIS2/ISO 22301
The DR is worth as much as its last rehearsal: plans, DataLab and reports kept alive by us — the failover that really starts.
05 · Use cases

Where it really pays off.

Corporate DR

The plan that works because it trains.

Audits and insurance

The automatic evidence, always up to date.

Cyber recovery

The orderly restart even after the ransomware.

A DR is real if its last rehearsal has a recent date: here the rehearsal is scheduled — forever.