Can't restore a project from backup after missing 90 days cut off
I had to take some time away from my supabase project. Unfortunately, after 90 days you can no longer restore the project but have to re-build it in a new project from a backup.
I'm following the guide outlined here
https://supabase.com/docs/guides/platform/migrating-within-supabase/dashboard-restore
I've pulled down the .backup file but the psql commands don't seem to work.
psql -d 'postgresql://postgres.[PROJ_REF]:[DB_PASSWORD]@aws-0-eu-west-1.pooler.supabase.com:5432/postgres' -f db_cluster-24-05-2025@14-20-28.backup
psql: error: connection to server at "aws-0-eu-west-1.pooler.supabase.com" (108.128.216.176), port 5432 failed: FATAL: Tenant or user not found
connection to server at "aws-0-eu-west-1.pooler.supabase.com" (108.128.216.176), port 5432 failed: FATAL: Tenant or user not found
I can't ping aws-0-eu-west-1.pooler.supabase.com but I can telnet to it on port 5432?
Has anyone encountered similar?
Restore Dashboard backup | Supabase Docs
Learn how to restore your dashboard backup to a new Supabase project
1 Reply
Ouch I had to go into the connect on my project
and switch the connection from Direct Connection to Session Pooler
where it showed that the pooler url was aws-1-eu-west-1.pooler not aws-0-eu-west-1.pooler
(1 not 0)
