Backup and disaster recovery in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Supabase Backup Frequency

Supabase automatically creates backups of your database. How often are these backups typically created to ensure minimal data loss?

A Every 24 hours

B Every 7 days

C Every 1 hour

D Every 30 minutes

💡 Hint

Think about a balance between resource use and data safety.

Supabase creates daily backups every 24 hours to balance storage costs and data safety.

❓ Architecture

intermediate

Choosing a Disaster Recovery Strategy with Supabase

You want to design a disaster recovery plan using Supabase that minimizes downtime and data loss. Which approach best achieves this?

A Use Supabase's continuous replication to a secondary region for failover

B Rely on client-side caching to recover data after failure

C Manually export data weekly and store it locally

D Use Supabase daily backups and restore from the latest backup after failure

💡 Hint

Consider strategies that reduce downtime and data loss automatically.

Continuous replication to a secondary region allows quick failover with minimal data loss and downtime.

❓ Configuration

advanced

Configuring Automated Backups in Supabase

Which configuration snippet correctly enables automated daily backups for a Supabase project using the CLI?

A supabase db backup --auto --daily

B supabase backups schedule --interval 24h

C supabase backup enable --frequency daily

D supabase backup schedule --daily

💡 Hint

Look for the correct CLI command syntax for scheduling backups.

The correct command to schedule daily backups is supabase backup schedule --daily.

❓ security

advanced

Securing Backup Data in Supabase

What is the best practice to secure your backup data stored by Supabase to prevent unauthorized access?

A Disable encryption to speed up backup and restore

B Store backups in public buckets for easy access

C Encrypt backups at rest and restrict access with IAM policies

D Share backup credentials with all team members

💡 Hint

Think about protecting sensitive data and limiting access.

Encrypting backups and restricting access with IAM policies ensures backup data is secure.

❓ service_behavior

expert

Supabase Backup Restore Behavior

After restoring a Supabase database from a backup, what happens to the existing data and connections?

A The existing data is archived, and the backup data is loaded alongside it

B The existing data is replaced by the backup data, and active connections are terminated

C The backup data is merged with existing data, and connections remain active

D The restore fails if there are active connections, and data remains unchanged

💡 Hint

Consider what happens to live data and users during a restore.

Restoring replaces all current data with backup data and disconnects active users to ensure consistency.

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