Backup Recovery Assurance Agent
Finds out what would not come back
6 of 10 systems cannot prove they can be recovered.
10 systems checked. 6 are flagged, worth 55 risk points; the longest gap is 240 days.
Customer CRM is the most exposed. Tier T2 holds the most flagged systems.
A backup that exists may still not restore: only a restore test shows it works.
Why rows were flagged
- Backup older than target50%
- Never restore-tested30%
- Restore test over 180 days old20%
Value flagged by Tier
- T24
- T31
- T11
Systems to fix, worst first
| Item | Tier | Value | Days | Why |
|---|---|---|---|---|
| Customer CRM | T3 | 18 | 4 | Backup older than target, Never restore-tested |
| Analytics DB | T2 | 12 | 15 | Backup older than target, Never restore-tested |
| File server | T2 | 8 | 240 | Backup older than target, Restore test over 180 days old |
| Build server | T2 | 8 | 200 | Backup older than target, Restore test over 180 days old |
| Email archive | T2 | 6 | 10 | Backup older than target |
| Marketing site | T1 | 3 | 0 | Never restore-tested |
What to do this week
- Run a fresh backup and a restore test on Customer CRM now.
- Fix the T2 systems first: they carry the most weight.
- Schedule a restore test at least twice a year for every system, and monthly for tier 3.
Do
- Test a restore, not just a backup: a restore test is the only proof.
Don't
- Don't count a green backup job as recoverability.
How to improve
- Add the time each restore took so the next report can check it against your recovery time target.
- Add backup size and location so the next report can flag single-site copies.
Demo
Overview
Almost every organisation backs things up and almost none can say what would come back. The job reports success, the dashboard is green, and everyone treats that as the answer. A successful backup job proves a file was written. It proves nothing about whether the data is complete, whether it can be read, or how long it would take to make the business work again.
The failures are found in a crisis, which is why the story is always the same. A system nobody added to scope because it was created after the last review. Backups running successfully to a location the same event would destroy. Retention shorter than the time it takes to notice corruption, so by the time you know, the clean copy has aged out. A recovery time nobody has measured against one the business has promised customers.
And the one that ends companies: the backups are reachable with the same credentials as the systems they protect, so whoever reaches the primary reaches the copies.
This agent reviews the arrangement from your records and configuration and reports what would not come back, ranked by what it would stop. It restores nothing and tests nothing — a restore is a live operation on real systems, and it belongs to the people who own them.
Benefits
You find out before the incident
Which is the only useful time to find out.
The gap between promise and reality
Named, with what it would take to close it.
Evidence for auditors and customers
Beyond a screenshot of a green dashboard.
What it does
Finds what is not backed up at all
Usually a system created after the last scope review. Nobody decided to exclude it.
Checks the copies are isolated
Backups reachable with the same credentials as the systems they protect are not backups. This is the one that ends companies.
Tests retention against detection time
If corruption takes six weeks to notice and retention is thirty days, the clean copy is already gone.
Compares measured recovery to promised recovery
Against what you told customers and auditors, not against what the tool claims.
Distinguishes a job from a restore
A green dashboard proves a file was written. Nothing more, and everyone reads it as everything.
Restores nothing
A restore is a live operation on real systems. It reviews the arrangement and reports.
What this changes
What this changes about your week
- It takes over
- Establishing what would actually come back after a failure.
- Done today by
- Assumed from a green dashboard.
- How often
- Annually, on paper.
- Typical manual effort
- Coverage, isolation, retention and tested recovery times read against what was promised.
Why IT & Service Management in particular. A successful backup job proves a file was written and nothing else. And backups reachable with the same credentials as the systems they protect are inside the blast radius rather than the recovery from it.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Backup Recovery Assurance Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-opus-5 with automatic fallback
- 3Toolssearch_knowledge, extract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Requirements
Integrations
No integrations required.
Before you start
- Systems in scope, with their business criticality
- Backup configuration: schedule, retention, destination, credentials model
- Restore test history, if any
- Your stated recovery time and recovery point objectives
- Requires the All-Access plan or higher
Use cases
Annual continuity review
What would actually come back, and how fast.
Before a certification audit
The questions an auditor asks, answered first.
After adding systems
Whether backup scope followed them.
Ransomware preparedness
Whether the copies survive an attacker who reaches the primary.
Pricing
All-Access
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Does it perform test restores?
No. A restore is a live operation on real systems with real consequences. It reviews configuration, records and test history, and reports what has never been tested — which is usually the finding.
Does it connect to our backup system?
No. It works from exports and documentation you supply, so it needs no access to anything that could be used to alter or delete a backup.
What if we have never tested a restore?
Then that is the report's first line. An untested backup is a belief, and saying so plainly is more useful than any other finding it could produce.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent