0Pricing
Supabase Backend as a Service · Lesson

Backup, Restore, and Disaster Recovery

Understand Supabase's backup mechanisms, learn how to perform manual backups, and develop a disaster recovery plan for your data.

Backup, Restore, and Disaster Recovery is a free Supabase Backend as a Service lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Supabase Backend as a Service learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Data Safety: Why Backups?

In the world of applications, your data is one of your most valuable assets. Losing it due to an accident, corruption, or malicious activity can be catastrophic.

This lesson will guide you through Supabase's backup mechanisms, how to perform manual backups, and how to create a solid Disaster Recovery Plan (DRP).

Supabase's Automatic Backups

Supabase provides robust automatic backup solutions to protect your database. These backups are taken daily and stored securely.

  • Daily Snapshots: Your entire database is backed up automatically every 24 hours.
  • Retention: These backups are typically retained for 7 days on the free plan and up to 30 days on paid plans.
  • Managed Service: Supabase handles the complexity of these backups for you, ensuring data durability.

Understanding Backup Types

When discussing database backups, it's helpful to understand the difference between logical and physical backups:

  • Logical Backups: These export your database schema and data as a series of SQL commands. They are flexible and portable, great for migrating data. pg_dump creates logical backups.
  • Physical Backups: These are direct copies of the database files on disk. They are faster for large databases but less portable. Supabase's automatic backups are typically physical snapshots.

Performing Manual Database Dumps

While Supabase handles automatic backups, performing manual dumps gives you direct control over specific data points or for local development. You can use the standard PostgreSQL tool pg_dump via your terminal.

Remember to replace <YOUR_DB_HOST> with your actual database host (e.g., db.<PROJECT_REF>.supabase.co) and set the PGPASSWORD environment variable before running.

PGPASSWORD="<YOUR_DB_PASSWORD>" pg_dump \
  -h <YOUR_DB_HOST> -p 5432 \
  -U postgres -d postgres > my_supabase_backup.sql

Restoring from a Manual Backup

To restore your database from a .sql backup file, you can use the psql command-line client. This is useful for migrating data or recovering to a specific state.

Important: Restoring usually involves dropping existing tables, so be extremely careful and ensure you have a fresh backup of your current state before proceeding!

PGPASSWORD="<YOUR_DB_PASSWORD>" psql \
  -h <YOUR_DB_HOST> -p 5432 \
  -U postgres -d postgres \
  < my_supabase_backup.sql

Point-in-Time Recovery (PITR)

For business-critical applications, Supabase offers Point-in-Time Recovery (PITR) on higher-tier plans. This advanced feature allows you to restore your database to *any* specific second within a given retention period.

PITR is crucial for minimizing data loss in scenarios where you need to undo a specific accidental change or recover from a precise moment before an incident occurred.

Backing Up Supabase Storage

Beyond your database, Supabase Storage holds your application's files (images, videos, documents). Unlike the database, Storage buckets are not automatically backed up by Supabase in the same way.

You should implement your own strategy for backing up critical files from your Storage buckets. This might involve:

  • Regularly downloading files using the Supabase CLI.
  • Using a custom script that interacts with the Storage API.
  • Integrating with cloud storage backup services.

What is a Disaster Recovery Plan?

A Disaster Recovery Plan (DRP) is a documented process for an organization to recover from an unplanned event that disrupts normal operations. It's more comprehensive than just backups.

A DRP outlines steps to ensure your application can quickly resume critical functions after a major incident, such as a regional outage, data center failure, or severe data corruption.

Key DRP Components

A robust Disaster Recovery Plan (DRP) should include:

  • Recovery Time Objective (RTO): The maximum acceptable downtime.
  • Recovery Point Objective (RPO): The maximum acceptable amount of data loss.
  • Roles & Responsibilities: Who does what during a disaster.
  • Communication Plan: How to inform users and stakeholders.
  • Testing Schedule: Regularly testing the DRP to ensure it works.
  • Runbooks: Step-by-step guides for recovery procedures.

DRP Quick Check

Consider the core components of a Disaster Recovery Plan (DRP).

Recap: Data Safety First

Congratulations! You've learned about the critical aspects of data safety with Supabase.

  • Supabase provides automatic daily database backups.
  • You can perform manual logical backups and restores using pg_dump and psql.
  • Point-in-Time Recovery offers advanced restoration capabilities.
  • Remember to plan for backing up your Supabase Storage files.
  • A comprehensive Disaster Recovery Plan (DRP) is essential for business continuity, defining RTO, RPO, roles, and testing.

Always prioritize your data's safety!

Frequently asked questions

Is the “Backup, Restore, and Disaster Recovery” lesson free?

Yes — the full text of “Backup, Restore, and Disaster Recovery” is free to read here on the web, and the Supabase Backend as a Service course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Supabase Backend as a Service course, upgrade to CoddyKit PRO.

What will I learn in “Backup, Restore, and Disaster Recovery”?

Understand Supabase's backup mechanisms, learn how to perform manual backups, and develop a disaster recovery plan for your data. You practise Supabase Backend as a Service with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Supabase Backend as a Service?

No prior experience is required. Supabase Backend as a Service on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Backup, Restore, and Disaster Recovery” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Supabase Backend as a Service lesson?

Yes. Every Supabase Backend as a Service lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Environment Management & CI/CD
  2. Backup, Restore, and Disaster Recovery
  3. Security Auditing and Best Practices
  4. Monitoring, Logging & Observability
← Back to Supabase Backend as a Service