Supabase Backend as a Service · Lezione

Backup, ripristino e disaster recovery

Comprenda i meccanismi di backup di Supabase, impari a eseguire backup manuali e sviluppi un piano di disaster recovery per i Suoi dati

Lezione 2 di 411 passaggi

Backup, ripristino e disaster recovery è una lezione Supabase Backend as a Service gratuita su CoddyKit. Questa è la lezione 2 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Supabase Backend as a Service, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Supabase Backend as a Service include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

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!

Gratis per iniziare

Impara Supabase Backend as a Service con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi
11
Lezioni
40

Domande Frequenti

La lezione «Backup, ripristino e disaster recovery» è gratuita?

Sì — il testo completo di «Backup, ripristino e disaster recovery» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Supabase Backend as a Service, passa a CoddyKit PRO. Il corso Supabase Backend as a Service include 4 lezioni in totale.

Cosa imparerò in «Backup, ripristino e disaster recovery»?

Comprenda i meccanismi di backup di Supabase, impari a eseguire backup manuali e sviluppi un piano di disaster recovery per i Suoi dati Eserciti Supabase Backend as a Service con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Supabase Backend as a Service?

Non è richiesta alcuna esperienza precedente. Supabase Backend as a Service su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 2 di 4.

Quanto tempo richiede la lezione «Backup, ripristino e disaster recovery»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Supabase Backend as a Service?

Sì. Ogni lezione Supabase Backend as a Service include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Gestione degli ambienti e CI/CD
  2. Backup, ripristino e disaster recovery
  3. Audit di sicurezza e best practice
  4. Monitoraggio, logging e osservabilità
← Torna a Supabase Backend as a Service