← All guides

Cursor backup guide

Back up your Cursor app database before going live

CursorSupabaseVPS

Short answer

Automated daily backups with a tested restore path for your Cursor app database.

Why this matters

Your app has real data but no backups. If the database breaks during migration, you lose everything.

Walkthrough

  1. 01

    Export the current database

    Get a dump of your current database before doing anything risky.

    • Use pg_dump or your database dashboard to export the full database.
    • Verify the dump file contains your tables and data.
    • Store the dump in a secure location outside the server.
  2. 02

    Set up automated backups in production

    Configure regular backups that run without manual intervention.

    • Use your deploy panel backup feature or set up pg_cron for scheduled dumps.
    • Store backups in a separate location from the database server.
    • Keep at least 7 days of daily backups.
  3. 03

    Test the restore path

    A backup you have not tested is not a backup.

    • Restore a backup to a temporary database and verify the data.
    • Document the restore steps in plain English.
    • Schedule a monthly restore test to keep the process fresh.

Where RepoAssistant fits

RepoAssistant sets up database backups with tested restore paths during Cursor app deployment.