Blog / Backup

Backup
July 15, 2026 · 6 min read · Nexus Team

A backup you've never restored is a hypothesis

The most dangerous state in backup operations is a dashboard that has been green for six months. Green means the job ran. It does not mean the data is complete, the retention window covers what you think it covers, the credentials to the backup store still work, or that anyone on the team can actually perform a restore before the client's patience runs out.

The only evidence that a backup works is a restore. Everything else — job status, success percentages, storage growth charts — is circumstantial.

What a restore drill actually verifies

  • The data is really there and really complete — not truncated by a quota, a misconfigured scope, or an exclusion rule someone added two years ago.
  • The path works end to end: credentials, encryption keys, and access to the storage target, all of which rot silently between real incidents.
  • The team knows the procedure — a restore performed for the first time during a real outage is a training exercise conducted at the worst possible moment.
  • The time-to-restore is a number you've measured, which means the recovery expectations you've set with the client are commitments, not guesses.

Why we built restore verification into the backup module's design

Nexus's Microsoft 365 backup follows the your-bucket-your-keys model we've written about before — and the same ownership logic extends here: if the backups are in your storage under your keys, restore drills are yours to run on your schedule, not a support ticket to a vendor. The design intent is that verification is scheduled work the platform tracks like any other recurring job, with the drill's outcome recorded against the client — evidence you can point to in a QBR or a compliance review, not a verbal "yes, we test restores."

Backup status tells you a job ran. A restore drill tells you the client's data survives. Only one of those is the actual product.

As always: the platform page shows the current, honest status of the backup module. What's described here is the operating model we're building to — written down now, in public, so you can hold us to it.

Follow the build as it ships.

Nexus is live in our own MSP operations and opening to a limited design-partner cohort. Join the private-preview list.