- Industry
- Retail
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Platform
- Code
- ENG-20
It verifies the backups of the order, stock, loyalty, product and payment-token databases and the store servers, and rehearses restores to prove the recovery time and data loss targets hold. It reports any backup that failed or any restore that took too long, and files the fix.
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 service: the backup jobs, results, encryption and retention 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 Head of Platform with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it files a ticket for each failed backup or missed target and records the rehearsal. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The backup and recovery plan: the systems and their recovery time and recovery point objectives, the backup schedules and retention, the restore runbooks, the store server recovery steps, and the data protection rules for backups.
Reads from
the backup service: the backup jobs, results, encryption and retention for the systems named.
Acts in
the issue tracker: it files a ticket for each failed backup or missed target and records the rehearsal.
Hands back
An object with backups (a list of system, last_success, encrypted and status), rehearsals (a list of system, restore_minutes, data_loss_minutes, target_met and notes) and fixes (a list).
Asks a person when
A critical system misses its recovery target, or a backup of payment tokens or shopper data failed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Orders data loss target (minutes) | 5 | The order database may lose no more than this much data in a recovery. |
| Orders recovery time target (minutes) | 60 | The order database must be back within this. |
| Rehearse each restore every (days) | 90 | Each critical system's restore is rehearsed this often. |
| Require encrypted backups | On | When on, an unencrypted backup is a failure. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- The order database must recover within 60 minutes with no more than 5 minutes of data lost; other systems follow their own targets.
- Rehearse each critical system's restore every 90 days, into an isolated environment.
- When on is true, an unencrypted backup is a failure; payment-token backups follow PCI DSS key management.
- Never rehearse a restore into production or onto store servers during trading.
- Report every failed backup and every missed target with the fix.
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.