Backups and restore
Every AOZUMI DB database is backed up as it changes. Restore it to any moment of your plan's window, into a new database or in place, or download a copy.
How backups work
- Snapshots. Each database that changed is copied whole every hour, while it keeps taking writes. Writes wait a moment for the copy; reads never do.
- Every change in between. The pages each commit writes are saved within about five seconds, so a restore can stop at any moment, not only at a snapshot.
- Where. In a private Amazon S3 bucket in Mumbai, apart from the database server.
- Back up now. On a database's page, before a migration or a risky change. One a minute per database; the newest 10 you take are kept.
A database's page shows how its backups are going: when every change was last saved, the moments it can be restored to, and each backup, marked Scheduled, Taken by hand or Before a restore. If saving fails, the page says since when; AOZUMI retries on its own.
How long they're kept
| Plan | Restore to any moment of the last |
|---|---|
| Free | 3 days |
| Plus | 7 days |
| Pro | 14 days |
A database that stopped changing keeps its newest backup, however old. Deleting a database deletes its backups too.
Restore
On the database's page, under Backups, choose Restore. Pick where to start, a backup or a moment, and where the data goes:
- A new database. A standalone database with the name you give it, made from the backup, while the original stays as it is. It counts toward your workspace's databases. Connect to it with a token from its page.
- In place. The database's data becomes the backup's. Its URL, its tokens and the app it serves stay, and the app sees the restored data at once. Type the database's name to confirm. Writes wait for a few seconds while it runs.
Agents can do the same over MCP with database_backups, database_backup and database_restore; see AOZUMI DB from a coding agent.
Download a copy
Each backup downloads as one SQLite file, named after the database and the moment it holds. Open it with sqlite3 or any SQLite tool. Each download is recorded in the workspace's audit log.
Who can do what
- Everyone in the workspace, and every API key, sees a database's backups and how they are going.
- Owners and admins, and their Manage keys, back up now, restore and download. Each of these is in the audit log.
AOZUMI DB is experimental and keeps each database on one server, so keep your own copy of anything you cannot lose. See data safety.
Questions
- How often is an AOZUMI DB database backed up?
- Every change. The server takes a snapshot of each database every hour while it changes, and saves every change in between within about five seconds, so you can restore it to any moment, not only to the last snapshot.
- How long are AOZUMI DB backups kept?
- 3 days on Free, 7 on Plus and 14 on Pro. The newest backup of a database is always kept, however old.
- Does restoring change the database's URL or token?
- No. A restore in place keeps the database's URL, its tokens and the app it serves; the app sees the restored data at once, without a redeploy. A restore into a new database makes a new standalone database with its own token.
- Can I undo a restore?
- Yes. A restore in place first keeps what it replaces as a backup marked Before a restore. Restore that backup to go back.
Checked against the product on .