Note: Snapshots and daily backups are part of GOLDNET Cloud, available when it opens to the public. Until then, request access and we'll set you up.
The short answer
- A snapshot is a copy of your server that you take, whenever you want, and keep until you delete it.
- A backup is a copy that we take for you every day, automatically. The last seven are kept.
Both are complete copies of the server's disk, stored away from the server itself. Both can be restored onto the server, or used to deploy a brand-new server.
Side by side
| Snapshots | Automatic backups | |
|---|---|---|
| Who starts it | You, from the server's page or the API | We do, daily, in the early hours (from 01:00 SAST) |
| How many are kept | Up to 20 per team; you delete the ones you no longer need | The newest 7; older ones are removed |
| How you pay | Per GB of snapshot, per month, billed by the hour while you keep it | A percentage of the server's monthly price, while backups are switched on |
| When you destroy the server | Snapshots stay, and keep being billed until you delete them | Backups are deleted with the server |
| Restore onto the same server | Yes | Yes |
| Deploy as a new server | Yes | Yes |
Current prices: Cloud pricing.
When to use a snapshot
- Before a risky change: a big upgrade, a new PHP or database version, a change to the firewall you're not sure about.
- Before you destroy a server you might need again. Take a snapshot, destroy the server and stop paying for it; deploy from the snapshot later.
- To clone a server: set one up once, snapshot it, then deploy copies.
When to rely on backups
- Every day, for mistakes you don't notice straight away: a deleted folder, a broken update, a plugin that went wrong on Tuesday night.
- For servers that change all the time, such as a shop or a database, where yesterday's copy is worth a lot.
Switch daily backups on when you deploy, or later from the server's page.
Good to know
- Restoring replaces what's on the server now. If you're unsure, deploy the snapshot or backup as a new server instead, check it, and then decide.
- Disk size matters. A snapshot needs a server with at least as much disk as the one it came from. Because disks can only grow, a snapshot of a larger server can't go onto a smaller plan.
- Neither is an off-site copy of your data. Both are stored with us in Durban. For data you truly can't lose, also keep a copy somewhere else: another provider, your office, or an export to your own computer. A good rule of thumb is three copies, on two kinds of storage, with one somewhere else.
- Block storage volumes are separate. Volumes you attach live on their own and outlive the server. Treat their data like any other data you need to back up.
More about volumes, snapshots and backups: Storage and backups.