Back to blog
engineering

A Backup Nobody Has Restored Is a Hope

By Daniel

A Backup Nobody Has Restored Is a Hope

Open the backups page of almost any hosting tool and you see a green tick and a time: last backup, 3 hours ago.

That tick proves a file was uploaded. It does not prove the file opens, that it holds your tables, or that it holds the data you had when it was taken. You find that out on the worst day to find it out.

We ran our own apps this way for a while. The only proof our backups restored was a script someone ran by hand. So we changed what the tick means.

Every backup gets restored, every week

Each project on RunMist has its own hour of the week. In that hour, its newest backup is downloaded, unpacked and opened on its server, away from the live app, and compared with what the app had when the backup was taken.

The Backups card shows the result, not just the upload time: when the last restore test ran, and whether it passed. If it failed, it says why in plain words, for example that a database existed when the backup was taken and is not in the archive. You can also run a test yourself, any time, with one click.

A difference that a later write explains is not a failure. Only data the backup should hold, and does not, is reported.

The backups are yours

Backups go to a bucket in your own Cloudflare R2 or S3 account. RunMist never stores your data. Setup is one pasted token per server, and backups are then on by default for every project on it.

You choose hourly, daily or both. On R2 buckets that RunMist sets up for you:

  • hourly copies are kept for 1 day,
  • daily copies are kept for 14 days,
  • daily copies are locked for 7 days, so nothing can overwrite or delete them in that time, including a server that has been broken into.

That last point matters more than it sounds. A backup that the server can overwrite is one bad script away from being gone, and ransomware knows where backups live.

What is covered

SQLite databases, which is where apps on RunMist keep their data by default. If your app uses a hosted Postgres or another outside database, that provider's backups cover it, not ours.

Restoring

Today a restore is one command on your server, run with your admin login. It takes the newest backup, or the one you name, and it saves a copy of the current data first, so the restore itself can be undone. It is not a button in the dashboard yet.

Because the weekly test has already restored that archive on that server, the real restore is not a first attempt.