1
Issue While Restoring Supabase Database Backup
Source: supabase/supabase#46035 · opened by @Ithachiuchiha
I encountered an issue while restoring a database backup downloaded from my Supabase project. The downloaded backup had the same name for both the folder and the backup file: [email protected] Initially, this caused confusion during restoration because PostgreSQL commands were targeting the directory instead of the actual backup file. The restore process returned errors such as: Permission denied does not appear to be a valid archive ("toc.dat" does not exist) After investigation, I found that the actual backup file was located inside a folder with the exact same name, and the restore succeeded only after explicitly providing the complete file path. I would appreciate clarification on the backup packaging structure and whether this naming behavior is expected. It may help to avoid confusion if the extracted folder and contained backup file use different names or if additional documentation is provided for restoration steps. Environme…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add Storage Backups in Sync with Database Backups
4 votes · 0 comments
Taking Backup's and Restoring from Backup's should be very easy
5 votes · 0 comments
Feature idea/request: native backup functionality for the PostgreSQL database
2 votes · 0 comments
Configure External PostgreSQL for Supabase Instead of supabase-db
3 votes · 0 comments
NoSQL (Document) Database Alternative?
1 vote · 0 comments
No comments yet.