Skip to main content

R1. Backups

What this page helps you do​

Make sure your important production data can be recovered.

Why it matters​

A surprising number of launches fail safely until the first real mistake. Someone deletes data, a database breaks, a provider issue happens, or a bad migration lands. Without backups, recovery becomes guesswork or panic.

You should already have​

  • a live or nearly live app
  • some understanding of what data actually matters

Skip this page if​

  • your app stores no important data

Even then, think carefully before skipping.

What to do​

First, identify what must survive:

  • database records
  • uploads and files
  • important configuration
  • any user-generated content that cannot be rebuilt easily

Then make sure you have:

  1. a backup method
  2. a backup schedule
  3. a place backups live
  4. a basic restore plan

If you have never tested recovery, do not assume the backups are real.

Use your managed provider’s backup feature if it exists, then document it in plain English.

If you run your own server, make backups automatic as early as possible.

Common mistakes​

  • assuming the hosting provider automatically backs up everything
  • backing up the database but not uploads
  • never testing whether a restore is possible
  • having backups that only one person understands

Next step​

Go to R2. Secrets and then R8. Launch checklist.

Advanced notes​

If your app lets users upload files, make sure file storage and database backups stay in step. Restoring one without the other can still leave you with broken data.