- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Service Delivery
- Code
- ENG-20
It checks that every system on the SaaS platform and in managed-services client environments is backed up on schedule, retained as the client contract requires, encrypted, copied to a second region and restorable within the contracted RPO and RTO. It rehearses restores on schedule and files the evidence ISO 27001 and SOC 2 auditors and clients ask for.
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 cloud monitoring and observability stack: backup job history, encryption and replication status and restore test results..
- 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 Head of Service Delivery with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it files the recovery check as audit evidence and opens a ticket per failure. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The backup and recovery standard: RPO and RTO per client contract, retention terms, encryption, second-region rules within data residency, and the restore rehearsal procedure.
Reads from
the cloud monitoring and observability stack: backup job history, encryption and replication status and restore test results.
Acts in
the ticketing and service management system: it files the recovery check as audit evidence and opens a ticket per failure.
Hands back
A list of systems, each with system, client_or_platform, backup_ok (true or false), rpo_met, rto_met, encrypted, second_region, last_rehearsal (YYYY-MM-DD or null) and actions.
Asks a person when
A system misses its RPO or RTO, a backup is not encrypted, or a restore rehearsal fails for a client system.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default RPO (minutes) | 60 | Used where the contract names none. |
| Default RTO (minutes) | 240 | Used where the contract names none. |
| Rehearse restores every (days) | 90 | Each system is restored in a test at least this often. |
| Default retention (days) | 35 | Used where the contract names none. |
| Require a copy in a second region | On | When on, a backup without a second copy within the allowed regions fails. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check each system against its contracted RPO and RTO, or 60 and 240 minutes when none are set.
- A system without a successful backup inside its RPO fails at once.
- Rehearse a restore at least every 90 days and record the restore time against RTO.
- Retain for the contract's period or 35 days, and delete client backups when the contract ends as it requires.
- When on is true, a second copy is required, and only within the client's allowed regions.
- Every backup is encrypted.
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.