We’re on a Pro plan and trying to figure out the current best way to get a production backup we can actually test against locally.
We used to have backup downloads that restored much more cleanly. Now we’ve tried:
- raw pg_dump - supabase db dump
But restoring locally keeps running into managed schema/role issues (storage, auth, realtime, ownership/permissions, etc.), so it’s not behaving like the older backup-download flow.
What’s the recommended path now for a Pro project if we want to:
- get prod data? - restore/test safely outside prod? - ideally not rely on PITR unless that’s now the only real snapshot-style option?
Is the answer:
- enable PITR and use future restore points/backups - restore into another Supabase project - use supabase db dump - something else?
If helpful I can share exact commands/errors.
Main one is this but in general I've had to chagne sql migrations to get past certain failures when the snapshot backup i used to download which i have from nov just works
NOTICE (42P06): schema "kit" already exists, skippingERROR: schema "storage" does not exist (SQLSTATE 3F000)At statement: 6 revoke all PRIVILEGES on schema "storage" from "anon"
NOTICE (42P06): schema "kit" already exists, skippingERROR: schema "storage" does not exist (SQLSTATE 3F000)At statement: 6 revoke all PRIVILEGES on schema "storage" from "anon"
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.