DB Backup
DB Backup
Daily backups of your MySQL, MariaDB, PostgreSQL or MongoDB database, zipped into File Storage, with an email when one fails.
DB Backup takes a copy of a database every day and puts it in your File Storage. It works with databases you host anywhere — a VPS, AWS RDS, DigitalOcean, MongoDB Atlas, Supabase — as long as the database can be reached over the internet. You reach it from DB Backup in the left menu.
It is part of the Pro plan. On Free the page shows what it does and an upgrade link.
What you get
| Pro | |
|---|---|
| Auto backups | 2 databases |
| How often | Every day, at a time you pick (UTC), plus Back up now (3 a day) |
| Size | Up to 50 MB per backup, zipped — roughly a 250–500 MB database |
| Kept | The newest 7. Older ones are removed after each new backup lands |
| Where | File Storage → Backups → your backup's name. Counts against your 1 GB |
| When it fails | One email that says why, to the account owner |
Need more backups, bigger databases or longer retention? Email support@devops-agent.io.
Which databases
| Engine | Versions we take today |
|---|---|
| MySQL | 5.7, 8.0, 8.4 and 9 |
| MariaDB | 10.6, 10.11, 11.4 and 11.8 |
| PostgreSQL | 15, 16, 17 and 18 |
| MongoDB | 6, 7 and 8 |
We test every major version before adding it, so a newer or older server is refused at Test connection with a message. Email us and we'll test and add it.
Setting one up
- Name it —
shop-prod, say. That becomes the folder in File Storage and the start of every file name. - Database. Pick the engine, then either paste a connection string
(
mysql://user:password@host:3306/db,postgres://…,mongodb+srv://…) or fill in host, port, database, username and password. The string is only used to fill the fields; it is not stored. - Allow our IP in your database's firewall: the page shows the address with
a copy button and short notes for RDS, DigitalOcean, Atlas, Supabase and a
plain server. Allow only that address, never
0.0.0.0/0. Tip: make a read-only user for backups — Show the SQL gives you the statement for your engine. - Test connection. We log in with the engine's own client and answer in one line: "Connected. MySQL 8.0.36 · database is 212 MB · zip ≈ 30 MB". If it fails, the message says what to fix.
- Every day at. Pick the time (UTC; your local time is shown next to it). Create unlocks once the test passes, and the first backup runs straight away so you can see it land.
What's in a backup
Each backup is one zip, named like shop-prod_2026-10-12_02-00-UTC.zip (date
and time in UTC, so files sort by name). Inside:
- the dump —
shop.sqlfor MySQL, MariaDB and PostgreSQL (plain SQL),shop.archivefor MongoDB (mongodumparchive) README.txtwith the source, the time, a checksum and the exact restore command for that engine
Backups hold your customers' data, so only an Owner or Admin can download one, and the AI assistant never reads them. It can tell you when the last one ran — ask "when was my database last backed up?".
When something goes wrong
| The page says | What to do |
|---|---|
| We couldn't reach the database | Check that our IP is allowed in the firewall and the port is right |
| The database rejected the username or password | Check the login; edit the backup to enter a new one |
| The database and the TLS setting disagree | Turn TLS off if the server has no certificate, or on if it requires one |
| The backup went past 50 MB | The database is too big for the plan. Email us |
| File Storage is full | Delete something in Files, or email us for more space |
| Paused — 7 failures in a row | Fix the problem (usually the firewall or the login), then Resume |
A failed night never touches earlier backups: they stay until a new one succeeds and pushes the oldest out.
Good to know
- A backup is a logical dump taken while the database is running: consistent for InnoDB and PostgreSQL; MyISAM tables are locked for a moment; MongoDB is dumped collection by collection, not as a point-in-time snapshot.
- The dump runs on our server inside a locked-down container with the database's own client tools, then is zipped and saved.
- Databases that only listen on
localhostcan't be reached this way. Managed databases created from the Databases page have their own daily backups. - Dropping to Free pauses the backups; the zips stay. Upgrading again resumes them.