Backups Overview

Backups are essential for protecting your business data. calmo.cloud provides a complete backup system that captures your Odoo database and all uploaded files, storing them safely in cloud storage.

What's included in a backup? #

Unless the service is set to back up the database only, each backup contains:

• Database — The full PostgreSQL database with all your Odoo data (contacts, invoices, orders, settings, etc.)
• Filestore — All uploaded files (attachments, images, documents)

Together, these give you a complete snapshot of your Odoo instance at a specific point in time.

Backup features #

Manual backups #

Create a backup at any time with a single click. Useful before making major changes, like upgrading addons or migrating data.

Scheduled backups #

Set up automatic backup schedules to run hourly, daily, weekly, or monthly. Never worry about forgetting to back up.

Cloud storage #

Backups are stored in S3-compatible cloud storage (such as AWS S3, MinIO, or Backblaze B2). This means your backups are safe even if your server fails.

Multiple destinations #

Back up each service to several destinations at once — for example the platform's storage plus your own S3 bucket. Each destination has its own schedule and retention, so you can keep hourly backups nearby and a longer archive in a bucket you own. See Multiple Backup Destinations.

Retention policies #

Configure how long backups are kept — independently per destination. calmo.cloud can automatically delete old backups to manage storage costs.

Database-only backups #

Turn on Back up the database only in the Backup Settings of a service, and every backup of that service contains the database but leaves out the filestore (attachments, images, documents). This applies to scheduled backups, manual backups, and backups started through the API or an AI assistant. Use it when the filestore is backed up another way, or when it is too large to back up regularly. Database-only backups are smaller and faster.

The Contents column in the Backups tab shows for each backup whether it holds "Database and filestore" or "Database only". Turning the setting on does not change existing full backups. They rotate out as usual under the retention count.

Restoring a database-only backup replaces the database and keeps the service's current filestore. The safety backup taken before a restore follows the backup you restore, not this setting: restoring a full backup first saves the current filestore too, because the restore replaces it. See Restoring from Backup.

Backup status #

Getting started #