Snapshots and backups
Copies of a server's disk, on demand or daily.
Both snapshots and backups copy a server's disk into an image stored outside the server's host. You can create new servers from them or rebuild an existing server with them. Neither includes attached volumes.
| Snapshots | Backups | |
|---|---|---|
| Created | When you ask (create_image) | Automatically, once a day |
| Kept | Until you delete them | The newest 7; older ones are deleted |
| When the server is deleted | Kept | Deleted with the server |
| Price | Per GB of snapshot size per month | 20 % of the server's price |
Snapshots
odx server create-image --description "before upgrade" web-1
odx image list --type snapshotA snapshot is billed per GB of its size per month (at least 1 GB) for as long as it exists, independently of the
server, which you can delete afterwards. Snapshots are uploaded one after another per location, so a snapshot can
take a while to become available; an organization can have two snapshots in progress at a time. While a snapshot
is being taken, other actions on the server are refused with 409 resource_busy.
For a consistent snapshot of a database, stop the database or power off the server first.
Backups
Turn on backups per server (enable_backup). The server is then backed up once a day in its backup window, a
four-hour slot in UTC shown as backup_window (for example "22-02" means between 22:00 and 02:00 UTC). The window
is assigned automatically to spread backups over the day.
- The seven newest backups are kept; the oldest is deleted when a new one is made.
- Backups cost 20 % of the server's price, charged hourly together with the server and capped monthly like the server.
- Turning backups off deletes all of the server's backups. So does deleting the server.
- To keep a backup longer, create a server from it and take a snapshot, or keep the server's snapshots instead.
odx server enable-backup web-1
odx image list --type backupRestoring
- Rebuild the server from the snapshot or backup: its disk is replaced, the server keeps its IPs. Everything written since the snapshot or backup is lost.
- Or create a new server with the snapshot or backup ID as the image, then move your floating IP to it.