Skip to content

Documentation / Backups

Creating Backups

Create manual backups of your Odoo services.

You can create a backup of any running Odoo service at any time. This is especially useful before making significant changes.

When to create a manual backup #

  • Before upgrading Odoo or addons
  • Before importing large amounts of data
  • Before making configuration changes you might want to undo
  • Before deleting records or modules

Creating a backup #

1. Open the service #

Navigate to the service you want to back up.

2. Click Create Backup #

In the service actions, click Create Backup. If the service has multiple backup destinations, pick where the backup should go — the primary destination is preselected.

Switch on Include addon code to put the addons deployed to the service into the archive as well, in an addons/ folder. That is meant for moving the Odoo to another host; a restore ignores the folder. The switch appears once the service has an addon, and on a shared service it needs the Developer role or higher.

3. Wait for completion #

The backup process will:

  1. Dump the PostgreSQL database and stream it to your configured backup destination
  2. Compare the filestore with what the destination holds already, and stream the files that are new (skipped when the service is set to back up the database only). See Only new files are stored.

Nothing is written to the server's disk on the way, so a backup needs no free disk space on the server, however large the filestore.

Progress is shown in the Actions tab.

Once complete, the backup appears in the service's Backups tab with a "Completed" status.

Backup destination #

Before creating backups, you need to configure a Backup Destination — the cloud storage where backups are saved.

4. Go to Infrastructure Settings #

In the sidebar, navigate to Infrastructure Settings > Backup Destinations.

5. Add a destination #

Click New Backup Destination and provide:

  • Name — A label for this storage (e.g., "AWS S3 Backups")
  • Endpoint — The S3-compatible endpoint URL
  • Bucket — The storage bucket name
  • Access Key and Secret Key — Your storage credentials
  • Region — The storage region

calmo.cloud supports any S3-compatible storage provider, including AWS S3, DigitalOcean Spaces, Backblaze B2, and MinIO. A service can back up to several destinations at once, each with its own schedule and retention.

Downloading backups #

You can download completed backups directly from the Backups tab. calmo.cloud generates a temporary download link that is valid for 60 minutes. A download that is still running when the link expires finishes normally. A backup that includes addon code can only be downloaded by people who may manage the service's addons.

A backup with the filestore is first put together into one archive, because its files are spread over the backups before it. Click Prepare Download: calmo.cloud collects the files on the service's server and writes the archive to your backup destination, next to the backup. The service keeps running meanwhile. For a large filestore this takes a while; you get a notification when it is done, and Download then gives you the link. The archive stays available for 72 hours and is removed after that. Click Prepare Download again for a new one.

The server needs free space for the database archive and for the files of the backup that the service no longer has. Files the service still holds are linked, not copied.

For downloading a large archive and taking it to another host, see Moving to another host.

Multiple destinations Restoring