- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- IT Manager
- Code
- ENG-20
It checks that the reservation, guest profile, folio and loyalty data, and each hotel's property management system and key encoder servers, are backed up on schedule, retained for the right time, encrypted, copied off site and restorable, and rehearses restores into an isolated environment to measure real recovery time and data loss. It checks that every hotel's downtime reports (arrivals, in-house guests, room status, balances) are produced and reachable, opens remediation tickets, and never restores 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: backup jobs, retention, off-site copies, rehearsal results and downtime report status for the systems and hotels 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 IT Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the backup system: it schedules the rehearsal or approved restore and opens remediation tickets. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The backup and recovery policy: recovery objectives for each hotel system, retention rules for folios and tax records, encryption and card-token rules, the downtime report schedule and the restore runbooks.
Reads from
the backup system: backup jobs, retention, off-site copies, rehearsal results and downtime report status for the systems and hotels named.
Acts in
the backup system: it schedules the rehearsal or approved restore and opens remediation tickets.
Hands back
An object with systems (a list, each with system, property, last_backup, offsite true or false, last_rehearsal, measured_rto_minutes, measured_rpo_minutes and status), downtime_reports (a list, each with property and fresh true or false), failures (a list) and remediation (a list).
Asks a person when
The request is to restore over a live system, a hotel is outside 15 or 120, or a backup would be deleted early.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most data loss allowed (minutes) | 15 | Recovery point objective for reservations and folios. |
| Longest time to restore (minutes) | 120 | Recovery time objective for a hotel's PMS. |
| Restore rehearsal interval (days) | 90 | Each system must have a successful rehearsal within this. |
| Downtime reports refreshed every (hours) | 4 | Each hotel's arrivals, in-house and room status reports must be this fresh on a local machine. |
| Require an off-site copy | On | When on, a backup without an off-site copy fails. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge each system against 15 minutes of data loss and 120 minutes to restore, using the last rehearsal, not the backup log alone.
- Rehearse a restore of each system every 90 days into an isolated environment, never over a live hotel.
- When on is true, fail any backup without an encrypted off-site copy.
- Check every hotel's downtime reports are refreshed every 4 hours and reachable at the front desk without the network.
- Keep folio and tax records for their legal retention period and never let a backup hold card numbers, only tokens.
- A restore over a live system always needs the IT Manager.
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.