Supabase backup & recovery guide

Supabase is a platform that provides you with a PostgreSQL database, authentication, storage, and APIs.
In this video, I will show you how to backup and restore your Supabase database using the command-line tools pg_dump and pg_restore.
You will learn how to create a custom-format dump file, and how to restore it to an existing database.
I will also show you how to install pg_dump and pg_restore on different operating systems, such as macOS, Ubuntu, Arch Linux, and Redhat. By the end of this video, you will be able to backup and restore your Supabase database with ease and confidence.
Install pg_dump & pg_restore:
Ubuntu: www.cyberithub.com/how-to-ins...
macOS: www.cyberithub.com/how-to-ins...
Arch Linux: man.archlinux.org/man/pg_rest...
Checkout SimpleBackups for a free 7 day trial.
simplebackups.com

[@alastairtheduke]

very helpful

[@simplebackups]

Glad you found it helpful!

[@djmixerlover8633]

By mistake I reset my whole database please help me I don't have backup

[@simplebackups]

Unfortunately without a backup in place, there is not much you can do... Happy to help you configure your backup though.

[@wilkensgomes]

I'm getting this error --> pg_restore: error: COPY failed for table "customers": ERROR: duplicate key value violates unique constraint "customers_pkey"

[@simplebackups]

It looks like you're encountering a duplicate key value error while trying to restore a PostgreSQL database. This typically happens when there are conflicting primary key values in the "customers" table. To resolve this, you might want to check for any duplicate keys or conflicts in your data. You can also consider updating the database dump to ensure it doesn't contain conflicting primary key values. If the issue persists, feel free to provide more details, and I'll do my best to assist you.

[@joshikroshan5584]

got this pg_dump: error: connection to server at , port 5432 failed: Connection refused

[@simplebackups]

The error message you're encountering indicates that **pg_dump** is unable to connect to the PostgreSQL server on port **5432**. Let's troubleshoot this issue: 1. **Check PostgreSQL Server Status**: - First, ensure that the PostgreSQL server is running. You can use the following command to check its status: ``` sudo service postgresql status ``` - If the server is not running, start it using: ``` sudo service postgresql start ``` 2. **Verify Port and Configuration**: - Confirm that PostgreSQL is configured to listen on the correct port (usually **5432**). - Check the **postgresql.conf** file for the following settings: ``` listen_addresses = '*' port = 5432 ``` - Also, verify the **pg_hba.conf** file for proper authentication settings. 3. **Check Port Availability**: - Run the following command to see if port **5432** is open: ``` sudo netstat -plunt | grep postgres ``` - If you don't see port **5432**, it might be blocked or not configured correctly. 4. **Restart PostgreSQL**: - Try stopping and restarting the PostgreSQL server: ``` sudo service postgresql stop sudo service postgresql start ``` 5. **Alternative Port**: - If you suspect port **5432** is the issue, try starting PostgreSQL on a different port (e.g., **5433**): ``` sudo service postgresql stop sudo service postgresql start -o "-p 5433" ``` Remember to adjust the commands based on your system configuration. If the problem persists, check the PostgreSQL logs for more details. Hopefully, this helps resolve the connection issue! 🚀🔍🐘.