Coolify is an open-source, self-hosted Platform as a Service (PaaS) solution for managing cloud infrastructure, applications, and databases. It provides built-in backup capabilities that automate database protection and enable recovery from storage failures or accidental data loss.

This article explains how to deploy a PostgreSQL database on Coolify, configure scheduled backups to S3-compatible storage, and restore the database from a backup file. It covers sample data creation, data loss simulation, and verification of the restored database.

Prerequisites

Before you begin, you need to:

• Have access to a Linux-based server (with at least 2 CPU cores and 4 GB of RAM) as a non-root user with sudo privileges.
• Install Coolify on the server.
• Have access to an S3-compatible storage service (such as Vultr Object Storage, AWS S3, Wasabi, Backblaze B2, or MinIO).

Deploy PostgreSQL in Coolify

Coolify manages databases as resources within projects. Each project can contain multiple services that share networking and configuration settings.

1. Open your Coolify dashboard at http://SERVER-IP:8000. Replace SERVER-IP with your server's IP address. Log in with your admin account.

2. Under Projects, click Add to create a new project.

3. Name the project (such as Pg Backup) and click Continue to finish creating the project.

4. Click Add New Resource to create a new resource.

5. Under Databases, select PostgreSQL.

6. In the Select a PostgreSQL type screen, select PostgreSQL (the standalone option with the elephant logo, not the PostgreSQL with Supabase or pgVector variants).

   

7. Click Start to deploy the PostgreSQL database.

Add Sample Data to the Database

PostgreSQL stores data in tables that contain rows and columns. Creating sample data provides a baseline to verify that backups capture the database state correctly.

1. In the PostgreSQL resource dashboard, navigate to the Terminal tab.

2. Connect to the database using the psql client.

   console Copy

   $ psql -U postgres
   

   Explain Code

   Output:

   psql (18.2)
   Type "help" for help.
   
   postgres=#

3. Create a sample table.

   psql Copy

   postgres=# CREATE TABLE users (
       id SERIAL PRIMARY KEY,
       name VARCHAR(100),
       email VARCHAR(100)
   );
   

   Explain Code

4. Insert sample data.

   psql Copy

   postgres=# INSERT INTO users (name, email) VALUES ('John Doe', 'john@example.com');
   postgres=# INSERT INTO users (name, email) VALUES ('Jane Smith', 'jane@example.com');
   

   Explain Code

5. Query the table to verify the data insertion.

   psql Copy

   postgres=# SELECT * FROM users;
   

   Explain Code

   Output:

    id |    name    |      email
   ----+------------+------------------
     1 | John Doe   | john@example.com
     2 | Jane Smith | jane@example.com
   (2 rows)

Configure Scheduled Backups to S3-Compatible Storage

Coolify uses cron-based schedules to create database dumps and upload them to S3-compatible storage. The backup files are compressed with gzip and stored in a structured directory hierarchy.

Set Up S3-Compatible Storage in Coolify

Coolify requires an S3 storage configuration to upload backup files. The configuration stores the endpoint, credentials, and bucket name used for all backup operations.

1. In your S3 storage provider's dashboard, create a new bucket for database backups (for example, pg-backups). Note the bucket name, endpoint URL, access key, and secret key.

2. In Coolify, navigate to S3 Storages in the side menu and click Add.

3. Configure the S3 storage connection with the following values:

   • Name: Enter a descriptive name (for example, Backup Storage).
   • Description: Add an optional description.
   • Endpoint: Enter your S3 provider's endpoint URL (for example, ewr1.vultrobjects.com for Vultr, s3.us-east-1.amazonaws.com for AWS, or s3.wasabisys.com for Wasabi).
   • Bucket: Enter the bucket name.
   • Region: Enter the bucket's region (for example, us-east-1).
   • Access Key: Enter the access key from your S3 provider.
   • Secret Key: Enter the secret key from your S3 provider.

4. Click Validate Connection & Continue to verify and save the configuration.

Enable Backups for the PostgreSQL Service

Each PostgreSQL service in Coolify has its own backup configuration. The schedule determines when backups run, and the storage destination determines where files are saved.

1. Navigate to the PostgreSQL resource dashboard and select the Backup tab.

2. Click Add to create the backup schedule.

3. In the schedule creation form, configure the following:

   • Frequency: Set to */1 * * * * to run every minute for testing.
   • Save to S3: Check this checkbox.
   • Click Save.

   

4. Click the schedule you created, then under Settings, check the Backup All Databases checkbox and save.

   Note

   Without this option enabled, the schedule backs up only the default postgres database. Additional databases on the server are excluded from the backup.

5. Wait one minute for the first scheduled backup to run. Open the S3 bucket in your provider's dashboard and verify that the backup file appears.

Simulate Data Loss

Dropping a table removes both the table structure and all data it contains. Use this operation to simulate the type of accidental data loss that backups protect against.

1. Navigate to the Terminal tab in the PostgreSQL resource dashboard. Connect to the database.

   console Copy

   $ psql -U postgres
   

   Explain Code

2. Drop the users table to delete all sample data.

   psql Copy

   postgres=# DROP TABLE users;
   

   Explain Code

3. Attempt to query the table to confirm the data loss.

   psql Copy

   postgres=# SELECT * FROM users;
   

   Explain Code

   Output:

   ERROR:  relation "users" does not exist
   LINE 1: SELECT * FROM users;
                         ^

Restore the Database from S3-Compatible Storage

Coolify's restore process downloads the backup file from S3 storage, decompresses it, and executes the SQL statements to recreate the database objects and data.

1. Open the S3 bucket in your provider's dashboard and locate the backup file. Coolify stores backups in a path structure like data/coolify/backups/databases/.... Click the backup file (for example, pg-dump-all-1771242721.gz) to view its details.

   

2. Copy the object key (the path portion without the bucket name). For example, if the full path is:

   pg-bucket/data/coolify/backups/databases/root-team-0/postgresql-database-k8480c44sogcswc0w4oskg4c-k8480c44sogcswc0w4oskg4c/pg-dump-all-1771242721.gz

   The object key is:

   data/coolify/backups/databases/root-team-0/postgresql-database-k8480c44sogcswc0w4oskg4c-k8480c44sogcswc0w4oskg4c/pg-dump-all-1771242721.gz

3. In the PostgreSQL resource dashboard, navigate to the Configuration tab and scroll to the Import Backup section.

4. Under Choose Restore Method, click Select from S3.

5. Under Restore from S3, select the S3 storage you configured earlier (for example, Backup Storage).

6. Under S3 File Path, enter the object key you noted earlier.

   For PostgreSQL servers with multiple databases, enable the Backup includes all databases checkbox to restore all databases from the backup file.

7. Click Check File. A success message confirms the file is accessible. Click Restore Database from S3 to proceed.

8. Type the case-sensitive confirmation text exactly as shown and click Continue.

   

9. Enter your Coolify password in the prompt, then click Confirm.

   

Test the Restored Database

Querying the restored data confirms that the backup file captured a complete and consistent snapshot of the database state.

1. In the Terminal tab, connect to the database using psql.

   console Copy

   $ psql -U postgres
   

   Explain Code

2. Query the users table to verify the restoration.

   psql Copy

   postgres=# SELECT * FROM users;
   

   Explain Code

   Output:

    id |    name    |      email
   ----+------------+------------------
     1 | John Doe   | john@example.com
     2 | Jane Smith | jane@example.com
   (2 rows)

   The output matches the original data, confirming the backup captured the complete database state before the table was dropped.

Conclusion

You have configured automated PostgreSQL backups to S3-compatible storage in Coolify, created sample data, simulated data loss, and restored the database from the backup file. This configuration provides data protection against accidental deletions and storage failures. For more information about Coolify's backup features, visit the official Coolify documentation.