Skip to main content

Infrastructure & Cloud

Backup & Recovery

Backups that have actually been restored, because an untested backup may not exist at all.

A technician runs a restore test on a laptop with a checklist and stopwatch, beside a labelled backup unit

Nearly every company has backups. Far rarer is the company that has actually restored one, and knows how long it took.

An IT manager and a partner engineer review a restore drill report with downtime and data-loss targets while a technician watches a restore with a stopwatch

Two numbers we set with you up front: how long the service may be down, and how much data may be lost. Both drive the cost, and agreeing them beforehand is far cheaper than discovering them during an incident.

Restore drills are scheduled rather than left to good intentions. The report states the real elapsed time — and if that number exceeds what was agreed, the setup changes, not the number.

What is included

  • Two agreed numbers

    Downtime and data-loss limits written down before any setup begins.

  • Off-site copy

    One copy lives somewhere that does not go down with the main system.

  • Scheduled restore drills

    A real restore is run on a schedule, with the actual elapsed time reported.

When was your backup last restored?

If the answer is "never", that is not embarrassing — it is the most common answer we get.