Backup and disaster recovery in Supabase - Mini Project: Build & Apply

Backup and Disaster Recovery with Supabase

📖 Scenario: You are managing a small web application that uses Supabase as its backend database. To protect your data from accidental loss or corruption, you want to set up a simple backup and disaster recovery plan.This project will guide you through creating a backup schedule, configuring storage for backups, and setting up a recovery process.

🎯 Goal: Build a basic backup and disaster recovery setup for a Supabase project by creating a backup schedule, configuring storage for backups, and defining a recovery process.

📋 What You'll Learn

Create a backup schedule configuration

Set up a storage bucket for backups

Write a function to trigger backups

Configure recovery steps to restore from backups

💡 Why This Matters

🌍 Real World

Backing up data regularly protects your application from data loss due to mistakes or failures.

💼 Career

Cloud engineers and developers must implement backup and disaster recovery plans to ensure data safety and business continuity.

1

Create a backup schedule configuration

Create a dictionary called backup_schedule with these exact entries: 'frequency': 'daily', 'time': '02:00', and 'retention_days': 7.

Supabase

# Your code here

Hint

Think of the backup schedule as a simple plan that says when and how often to save your data.

2

Set up a storage bucket for backups

Create a variable called backup_bucket and set it to the string 'supabase-backups' to represent the storage location for backups.

Supabase

backup_schedule = {
    'frequency': 'daily',
    'time': '02:00',
    'retention_days': 7
}
# Your code here

Hint

The backup bucket is like a folder where all your backup files will be stored.

3

Write a function to trigger backups

Define a function called trigger_backup that takes no parameters and returns a string formatted as "Backup started and saved to {backup_bucket}" using an f-string.

Supabase

backup_schedule = {
    'frequency': 'daily',
    'time': '02:00',
    'retention_days': 7
}

backup_bucket = 'supabase-backups'

# Your code here

Hint

This function simulates starting a backup and tells where it is saved.

4

Configure recovery steps to restore from backups

Create a dictionary called recovery_plan with these exact entries: 'restore_from_bucket' set to backup_bucket, and 'restore_point_days' set to 3.

Supabase

backup_schedule = {
    'frequency': 'daily',
    'time': '02:00',
    'retention_days': 7
}

backup_bucket = 'supabase-backups'

def trigger_backup():
    return f"Backup started and saved to {backup_bucket}"

# Your code here

Hint

The recovery plan tells where to get backups and how far back to restore.

Practice

1. What is the main purpose of backups in Supabase?

easy

A. To save copies of data to prevent loss

B. To speed up database queries

C. To increase user authentication security

D. To reduce storage costs

Solution

1. Step 1: Understand what backups do

   Backups create copies of your data so you can restore it if something goes wrong.

2. Step 2: Identify the main goal in Supabase context

   Supabase backups protect your data from accidental loss or corruption.

3. Final Answer:

   To save copies of data to prevent loss -> Option A

4. Quick Check:

   Backups = Data safety [OK]

Hint: Backups always save data copies for safety [OK]

Common Mistakes:

• Confusing backups with performance improvements
• Thinking backups reduce costs
• Mixing backups with security features

2. Which Supabase feature allows you to create backups manually?

easy

A. Automated backups

B. Real-time replication

C. Database indexing

D. Manual snapshots

Solution

1. Step 1: Identify manual backup options in Supabase

   Manual snapshots let you create backups whenever you want, on demand.

2. Step 2: Differentiate from automated backups

   Automated backups happen on a schedule, not manually triggered by users.

3. Final Answer:

   Manual snapshots -> Option D

4. Quick Check:

   Manual backup = Manual snapshots [OK]

Hint: Manual backups are called snapshots in Supabase [OK]

Common Mistakes:

• Confusing automated backups with manual ones
• Thinking real-time replication is a backup
• Mixing indexing with backup features

3. Given this Supabase backup command snippet:

const backup = await supabase.storage.from('backups').upload('backup-2024-06-01.sql', file);
console.log(backup.error);

What will be the output if the upload succeeds?

medium

A. undefined

B. Error: File not found

C. null

D. Upload failed

Solution

1. Step 1: Understand Supabase upload response

   If the upload is successful, the error property is null, meaning no error occurred.

2. Step 2: Check console.log output

   Logging backup.error will print null on success, not a string or undefined.

3. Final Answer:

   null -> Option C

4. Quick Check:

   Success error = null [OK]

Hint: Successful upload error is null, not a message [OK]

Common Mistakes:

• Expecting error to be undefined on success
• Confusing error messages with success
• Assuming upload returns a string on success

4. You wrote this code to restore a backup but get an error:

const { data, error } = await supabase.rpc('restore_backup', { backup_id: 123 });
if (error) console.log(error.message);

What is a likely cause of the error?

medium

A. The 'restore_backup' function does not exist in the database

B. The backup_id parameter is missing

C. Supabase storage bucket is full

D. The file format is incorrect

Solution

1. Step 1: Check the RPC function existence

   If the 'restore_backup' function is not defined in the database, calling it causes an error.

2. Step 2: Verify parameters and storage

   The backup_id is provided, and storage fullness or file format errors usually cause different messages.

3. Final Answer:

   The 'restore_backup' function does not exist in the database -> Option A

4. Quick Check:

   Missing function = error [OK]

Hint: Check if the called function exists in the database [OK]

Common Mistakes:

• Assuming parameter missing without checking code
• Blaming storage when error is function-related
• Confusing file format issues with RPC errors

5. You want to ensure your Supabase project recovers quickly after a disaster. Which combination of backup strategies is best?

hard

A. Only automated backups with daily frequency

B. Automated backups daily plus manual snapshots before big updates

C. Manual snapshots only when major changes occur

D. No backups, rely on real-time replication

Solution

1. Step 1: Understand backup types and frequency

   Automated backups provide regular safety, while manual snapshots add extra protection before big changes.

2. Step 2: Combine strategies for fast disaster recovery

   Using both ensures you can restore recent data and specific points before updates, minimizing data loss and downtime.

3. Final Answer:

   Automated backups daily plus manual snapshots before big updates -> Option B

4. Quick Check:

   Combine automated + manual for best recovery [OK]

Hint: Use both automated and manual backups for safety [OK]

Common Mistakes:

• Relying only on manual snapshots risks missing backups
• Ignoring manual snapshots before big changes
• Assuming real-time replication replaces backups