Note: Backups (new)

Users on our Beta programme will see a new item alongside Backups in the Dashboard of their projects: Backups (new)

This provides early access to our new backup system, which offers improved speed and flexibility, and which we expect to roll out to all users over the coming weeks.

In the meantime, existing backups will continue to work as usual.

What’s backed up?

The three components of a Divio Cloud project are its:

  • codebase - the files containing application code, configuration, frontend styling and JavaScript and so on
  • database - in our case, the Postgres database that Django uses for persistent storage
  • media files - files uploaded/processed/stored by the project’s applications

All three are saved in our project backups. 

The backup is a compressed archive that, when expanded, contains all you need to recreate your project, and if you so wish, deploy it on another host. This is in accordance with our principle that a project on Divio Cloud belongs to you, and should be as open and portable as possible, so that you can sign up to our services confident that you will never find yourself locked in to them.

Note that the codebase is also already versioned in Git - every code change that is pushed to the server is recorded as a step in its history, and your code’s history can be rewound to any of those steps in its past. That history is shared wherever your code is saved: on our system’s Git server, your computer, even on another Git server if you choose to use one.

Automated and on-demand backups

Backups are initiated in two different ways:

  • automatically, according to a schedule
  • on-demand, when the user requests it

Scheduled backups

Scheduled backups of the Live server are provided on our Professional and higher (Business, Business Protection+) plans.

Enterprise plans can have custom schedules and retention policies to meet customer needs.

Retention policies for scheduled backups

Scheduled backups are retained according to the following scheme:

  • Each daily backup  is retained for a week - in other words, you’ll always have access to daily backups from each of the past seven days.
  • After seven days, the last backup is retained for four weeks - so you’ll also have access to a series of weekly backup covering the last four weeks.
  • Each month, a backup will be retained for a year - giving you a series of twelve backups for the previous year (Business Protection+ plans only).

Backup on demand

You can initiate backups at any time from the Control Panel, to create a saved state or in order to download a copy.

Backups can also be initiated optionally as part of a deployment, without requiring a separate operation. It is recommended to choose the option to backup when performing a deployment that contains Django migrations, that will make changes to the database.

On-demand backups can be made whenever you need and as often as you need.

Retention policies for on-demand backups

Although you can make as many on-demand backups as required, we don’t keep them all indefinitely. Retention policies depend on the project plan:

  • All backups are saved for 24 hours.
  • The latest three (Free and Personal plans) or five (Custom and higher plans) for each server, Test and Live, are saved for 30 days.

This is in addition to any scheduled backups that have been made.


For projects on Managed Cloud plans, encryption of backups is available on request. Please contact Divio support to request encryption. 

Did this answer your question?