- Industry
- Procure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Platform and Reliability Manager
- Code
- ENG-20
It checks that every platform store, from transactional PO and invoice databases to the contract repository, supplier master and spend warehouse, is backed up on schedule, retained for the financial-records period, encrypted, copied off site within its residency region and restorable. It rehearses restores into an isolated environment to measure real recovery time and data loss, reports against objectives and opens remediation tickets, never restoring over a live system without approval.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the backup system: the backup jobs, their last success, retention, copies and regions, and the restore history for the systems named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Platform and Reliability Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the backup system: it starts the restore rehearsal into the isolated environment, or the approved restore, and opens a ticket for each gap. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The backup and recovery policy: each system's recovery point and time objectives, client contract recovery commitments, retention rules for financial and contract records, encryption and off-site requirements, data-residency regions and the restore runbooks.
Reads from
the backup system: the backup jobs, their last success, retention, copies and regions, and the restore history for the systems named.
Acts in
the backup system: it starts the restore rehearsal into the isolated environment, or the approved restore, and opens a ticket for each gap.
Hands back
A list with one entry per system, each with system, last_backup (a timestamp or null), backup_age_minutes, rpo_met (true or false), retention_years, offsite_copy (true or false), region_compliant (true or false), encrypted (true or false), last_rehearsal (YYYY-MM-DD or null), measured_rto_minutes (or null), status (ok, at_risk or failed) and fix.
Asks a person when
The restore targets production or overwrites live data, restored client data would leave the isolated environment or its region, a backup would be deleted or its retention shortened, or a system misses its recovery objectives.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default recovery point objective (minutes) | 15 | The most data loss allowed for a system without its own objective; lost invoices or approvals are hard to recreate. |
| Default recovery time objective (minutes) | 240 | The longest a restore may take for a system without its own objective. |
| Rehearse a restore every (days) | 90 | A system not rehearsed within this long is flagged. |
| Minimum retention for financial records (years) | 7 | Backups or archives of PO, invoice, payment and audit-trail data kept for less than this break the policy. |
| Require an off-site, immutable copy | On | When on, a system without an immutable off-site copy in its residency region is at risk. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Measure each system against its own objectives and client contract commitments, falling back to 15 minutes of data loss and 240 minutes to restore.
- A backup counts only when its last job succeeded and it is encrypted; when on is true it also needs an immutable off-site copy in the same residency region.
- Flag any financial or contract store whose archive retention is below 7 years, and never shorten retention or delete a backup itself.
- Rehearse each system at least every 90 days into an isolated environment, recording measured recovery time and data loss.
- Restore into production or over live data only with the Platform and Reliability Manager's approval and a fresh backup of what it replaces, and reconcile restored invoices and payments against the ERP so nothing is paid twice.
- Restored copies holding client or supplier data stay in the isolated environment and are destroyed after the rehearsal.
See the Backup and Recovery Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.