Backups

When you configure a server you can switch on backups. With backups on, the server is backed up every day, and you make an extra copy yourself from the console whenever you want one, for example before an upgrade. You put a copy back when a change goes wrong. See Make and put back a backup for the steps.

Your own schedule

The daily backup follows the schedule we set for every server. Want another time, or more or fewer copies? Open Storage & backups, then Backup policies, and make a policy of your own: the time in your own time zone, daily or weekly, the number of incremental backups between two full ones, and how many of those chains to keep. Attach it to the server; a server has one policy at a time. The price stays the same whatever a policy keeps.

What it costs

A share of the plan price, shown in the summary before you start the server. It is billed by the hour with the server, with the same monthly ceiling.

While a server is paused

Backups keep billing while a server is paused for lack of credit, because they keep taking up space. They are removed together with the server.

What a backup is not

A backup on our platform is a help, not a guarantee. Keep a copy of what you cannot miss somewhere outside our platform as well.

Through the API

With an API token a script can do the same. Putting a backup back removes what is on the disk now, so send the name of the server as confirm, exactly as you would type it in the console.