Backup and disaster recovery in Supabase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of backup in cloud infrastructure?

The main goal of backup is to create copies of data so it can be restored if the original data is lost or corrupted.

beginner

What does disaster recovery mean in cloud services like Supabase?

Disaster recovery means having a plan and tools to quickly restore services and data after a major failure or disaster.

intermediate

How does Supabase handle backups for its databases?

Supabase automatically creates daily backups of your database and stores them securely to allow point-in-time recovery.

intermediate

Why is it important to test your disaster recovery plan regularly?

Testing ensures that backups work and recovery steps are clear, so you can restore data quickly when needed.

intermediate

What is point-in-time recovery in the context of Supabase backups?

Point-in-time recovery lets you restore your database to a specific moment before data loss or corruption happened.

What is the purpose of a backup in cloud infrastructure?

A To save copies of data for recovery

B To speed up the internet connection

C To delete old files automatically

D To monitor user activity

Backups save copies of data so you can restore it if lost or damaged.

Which of the following best describes disaster recovery?

A A method to encrypt data

B A way to increase storage space

C A plan to restore services after failure

D A tool to create user accounts

Disaster recovery is about restoring services and data after a failure or disaster.

How often does Supabase create automatic backups of your database?

A Every hour

B Daily

C Weekly

D Monthly

Supabase creates daily backups to protect your data.

What does point-in-time recovery allow you to do?

A Monitor database performance

B Backup data faster

C Delete old backups

D Restore database to a specific past moment

Point-in-time recovery restores data to a chosen time before an issue occurred.

Why should you test your disaster recovery plan?

A To ensure backups and recovery steps work

B To increase backup storage

C To speed up recovery time automatically

D To create more backups

Testing confirms your recovery plan works when needed.

Explain in simple terms what backup and disaster recovery mean and why they are important in cloud services like Supabase.

Think about how you save copies of important photos and what you do if your phone breaks.

Describe how Supabase supports backup and disaster recovery for its users.

Focus on the automatic backup schedule and recovery options.

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