Backups and restore
Backups and restore flows exist for the moments when confidence and correctness stop matching.
Backup flow
Creating a backup records a backup job against the project and stores the resulting backup key in metadata once the job completes.
Restore flow
A restore request references a backup key and targets either a new preview database, an existing preview database, or the current project when that project is explicitly marked non-production.
Clusters with wal-g backed storage also expose point-in-time restore by RFC3339 timestamp through the same restore surface.
Project overwrite restore requires an explicit confirmation flag. Production projects stay out of that path.
Operational note
Cluster responses now include backup storage mode and whether point-in-time recovery is available, so the dashboard and CLI can show the right restore options for the selected region.