Check what a recovery point contains

Use the coverage details on a recovery point to confirm what was captured before you rely on it for a restore.

1. Open the recovery point

1. Open the ReviveDB dashboard and select the protected project.
2. Open Backup history and expand the recovery point you want to inspect.
3. Check that the run finished successfully and note when it was created.

2. Check the component badges

Review the status shown for Database, Auth, Storage, Edge Functions, project configuration and secrets.

• A covered component was captured and passed the check shown for that component.
• An incomplete or unavailable component needs attention before you can treat the recovery point as complete.
• Secret values always remain a manual recovery action. Only their names are recorded, never the values.

3. Record the manual work

1. Read every incomplete-component warning shown below the recovery-point summary.
2. Record the secret values, external service credentials and DNS changes your own application needs.
3. Assign those actions in your recovery runbook before a real incident.

4. Decide whether the recovery point is usable

• Use it for a database-only rollback only when the database is verified.
• Use it for whole-project recovery only after checking every component and manual action you depend on.
• Run a new backup after fixing access or capacity problems. A previous incomplete recovery point does not become complete retroactively.

Background information

For a general explanation of what a backup covers, read the Supabase backup overview. For the platform limitation behind unavailable configuration, read the Management API coverage note.