- Industry
- Banking
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Chief Risk Officer
- Code
- ENG-20
It checks that every system supporting the bank's important business services (core banking, card processing, payments hub, internet and mobile banking) is backed up on schedule, retained for the regulatory period, encrypted, copied to the secondary site and restorable. It rehearses restores and failovers in isolation and reports against recovery objectives and impact tolerances.
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, retention, copy status and rehearsal records..
- 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 Chief Risk Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the operational resilience register: it records the recovery check against each business service's resilience record. 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 important business service, impact tolerances, retention periods for transaction and customer records, immutable backup copies against ransomware, the secondary site, and rehearsal frequency.
Reads from
the backup system: the backup jobs, retention, copy status and rehearsal records.
Acts in
the operational resilience register: it records the recovery check against each business service's resilience record.
Hands back
A list with one entry per system, each with system, last_backup, rpo_met, last_rehearsal, rto_achieved_minutes, immutable_copy (true or false), retention_ok and gaps.
Asks a person when
A backup is missing or failed, a rehearsal missed its RTO, a restore would touch a live system, or a gap breaches an impact tolerance.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Recovery point objective (minutes) | 15 | For important business services. |
| Recovery time objective (minutes) | 120 | For important business services. |
| Rehearse every (days) | 90 | Restores and failovers are rehearsed this often. |
| Retention (years) | 7 | Transaction and customer records are kept this long. |
| Immutable copy | On | When on, every backup has an immutable offline copy. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check each important service meets 15 minutes RPO and 120 minutes RTO.
- Rehearse every 90 days in an isolated environment, never against live systems.
- Retain transaction and customer records for 7 years.
- When on is true, every backup has an immutable offline copy.
- Report any gap against the impact tolerance to the Chief Risk Officer.
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.