Backups
A backup is a copy of an instance's data, captured while it runs and stored on the platform's backup pool. For PostgreSQL, MySQL and MariaDB it is a logical dump made with the engine's own tools, not a disk image; for a game server it is an archive of the server's files, its worlds and settings among them. Backups are on the instance page's Backups tab.
PostgreSQL, MySQL, MariaDB and the game servers — Minecraft, Terraria and Valheim — can be backed up from the dashboard. For the other engines, use their own tooling against the instance's endpoint. The three SQL engines can also export a dump you download, and import one.
Take a backup
On a running instance, open Backups and choose Back up now. The backup is captured asynchronously: the row appears immediately as pending, moves through creating while the platform takes the copy, and lands on ready with its size filled in. A stopped instance can't be backed up — there is nothing running to copy from — so start it first.
An instance takes one backup at a time: Back up now is refused while one is still pending or being created. Each instance keeps its seven most recent backups — when a new one lands, the oldest beyond that is deleted for you — and a workspace keeps at most 50 backups in all.
Backups count against your disk quota: the space they take is part of the disk the Usage page shows, rounded up to the next whole GB. A new backup needs some of that quota left, so a workspace whose disk quota is already full is refused one until it frees space or the quota grows.
There's no artifact download from the dashboard — restoring into an instance is how you get a backup's data back out. To take a copy of the data with you, use the instance's Export tab instead.
Restore
Restoring never touches the source instance. It provisions a new instance seeded from the backup: same engine and size as the source, on your workspace's private network, with no public endpoint until you decide it needs one. The new instance runs through the normal provisioning steps plus a restore step that loads the backup after the engine is installed — you can watch it on the provisioning log like any other launch.
Because the restore reads the source instance for its engine and size, it needs the source to still exist. Restore what you need before deleting an instance, not after.
The new instance counts against your quota like any other — a restore is a create, and the form's quota rules apply.
Delete a backup
Delete on a backup row marks it for removal and the platform cleans up the artifact asynchronously. Deleting an instance deletes its backups too, so restore any you need to a new instance first.
Export and import
PostgreSQL, MySQL and MariaDB instances also have Export and Import tabs, which move a database out and in as a file. Both need the instance to be running, and an instance runs one export and one import at a time.
- Export dumps the database with the engine's own tools into a gzip-compressed SQL file that restores anywhere: on this platform, on your machine, or at another provider. Choose schema and data, schema only, or data only, and on PostgreSQL which schemas. The file can be downloaded once: it is removed when you download it or when its retention period ends, whichever comes first. Our support team can't download it in a support session, since a dump can't be masked.
- Import loads a dump into the instance: a
.sqlfile, a gzip-compressed.sql.gz, or on PostgreSQL apg_dumpcustom-format archive. Replace existing data empties the database first, which cannot be undone, so the dashboard names the database and asks you to typeconfirmbefore the import starts. The file is stored encrypted, read only by that instance, and deleted as soon as the import ends.
Unlike a restore, an import writes into the instance you run it on.
Who can do this
Backup, restore, and delete all sit behind the workspace's instance:backup permission: owners, admins, and developers hold it, viewers don't. Exporting a database to a file takes the same permission, and so does downloading a game server's files — a copy of the data is a backup, not a read. Importing a dump needs instance:update, which owners, admins, and developers hold. See Workspaces & roles for the full matrix.
Next steps
- Instances — sizes, lifecycle, and the provisioning steps a restore runs through
- Connecting — reach the restored instance once it's running