Skip to main content
Updated October 11, 2026 Raff backs up every managed database every night and keeps the backups in Raff Object Storage, three copies each. PostgreSQL and MySQL also keep a continuous change log, so you can restore to any second, not only to last night.

​
How it works

​
Per engine

The first backup of a new database runs right after it starts. Back up now takes one at any time.

​
Restore into a new database

The default. Raff creates a new database on the same plan from the backup or point in time, named <name>-restored unless you choose. The original keeps running, so you can compare, copy back a table, or switch your app over. The new database is a normal, billed database; high availability is off unless you turn it on.

​
Restore in place

Overwrites the live database with the older state. Raff first takes a safety snapshot of the current data, then rebuilds the database; it is offline for a few minutes. Writes made after the restore point are gone, except in the safety snapshot.

​
Free databases

Free databases are backed up every night and restore in place. Point-in-time restore and restoring into a new database come with paid plans.

​
When to use it

  • A bad deploy or a wrong DELETE: restore into a new database to just before it, then copy the rows back.
  • A test copy of production: restore last night’s backup into a new database.
  • Rolling the whole database back: restore in place.

​
Trade-offs

  • Point-in-time restore reaches back to the oldest backup kept, shown in the Backups tab as Restore to any second since….
  • Valkey snapshots are nightly: a restore can lose up to a day of keys.
  • After a database is deleted, its backups are kept 14 days; within that time only support can restore them.

Back up and restore

Step by step in the dashboard.

High availability and replicas

Protection against server failures.
Last modified on October 11, 2026