Help Center/Admin Operations/How to open "Backup Status" (Resilience) and read it
Admin Operations•Last updated: 2026-10-20•3 min read

How to open "Backup Status" (Resilience) and read it

Backup runs recorded by the backup scripts, with age, size and verification.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the screen

In the admin sidebar open the "Resilience" group and click "Backup Status" (address /admin/resilience). Under the title the line "Data: ..." names where the figures come from: Live: i8_database_backups (written by the backup scripts).

2

Read the KPI tiles

Tiles: "Last successful backup", "Off-box freshness", "Runs succeeded / failed", "Last run verified", "Off-box storage configured". A tile that says "unavailable" means its source could not be read; it is never shown as zero.

3

Read the table

Columns: Started, Status, Stored, Trigger, Bytes, Age, Duration, Verification, Error. Each row is one backup run, recorded when it starts and closed as succeeded or failed. "Stored" says off-box (a storage bucket) or local disk (the same machine, so not a real backup). Verification is VERIFIED only when a verification run re-read the archive and matched its checksum.

4

Make a backup appear here

See "How to run a backup so it appears in Backup Status".

5

Know the limits

The platform has no built-in scheduler: backups happen only when something runs the script. "STALE" means no off-box backup in the last 26 hours; "NO OFF-BOX BACKUP" means none ever succeeded.

Expected Operational Outcome

You can read the live data and use the actions this screen really implements.

Troubleshooting & Failure Modes

Symptom: Failed to load resilience/overview: HTTP 403
Likely Cause: The operations API requires an administrator principal.
Resolution: Sign in with an administrator account and click "Retry".
Symptom: A tile or the description says a table "has not been created in this database"
Likely Cause: A database section (918 or 919) has not been applied yet.
Resolution: Ask the platform owner to run npm run db:apply:insight-security. Until then the screen reports it and offers no write buttons.

Was this guide helpful?

Help us refine our platform documentation