Multiple Backup Destinations

Back up each Odoo service to several storage destinations, each with its own schedule and retention.

A single copy of your backups is a single point of failure. hav.sh lets you back up each Odoo service to multiple destinations at once โ€” for example the platform's storage and your own S3 bucket โ€” each with its own schedule and retention policy.

#Why multiple destinations?

  • Redundancy โ€” If one storage provider has an outage or data loss, your backups still exist elsewhere.
  • Customer-owned copies โ€” Keep a copy of every backup in a bucket you control, independent of the platform.
  • Different schedules per destination โ€” Hourly backups to fast nearby storage, daily backups to long-term archival storage.
  • Different retention per destination โ€” Keep 7 backups on the primary, but 30 days of history in your archive bucket.

#How it works

Each service has a list of backup configurations. A configuration links the service to one backup destination and defines:

Setting Meaning
Backup Destination The S3-compatible storage backups are uploaded to
Backup Frequency Hourly, daily, weekly, monthly โ€” or empty for manual-only backups
Retention Count How many automatic backups to keep on this destination before old ones are rotated out
Primary Exactly one destination is the primary (see below)

Scheduled backups run independently per destination: a service with an hourly configuration and a daily configuration creates separate backups on each, on each one's own schedule. Rotation is also per destination โ€” each configuration's retention count only counts the backups stored on that destination.

#The primary destination

One configuration per service is always flagged as Primary. The primary destination is used by default for:

  • Manual backups (you can pick a different destination in the dialog)
  • Safety backups created automatically before a restore
  • Uploaded backups (Upload & Restore)
  • Copies created from the service

You can change which destination is primary at any time in the service's backup settings.

#Setting up multiple destinations

#1. Create the destinations

Under Infrastructure Settings > Backup Destinations, create each storage destination you want to use. Any S3-compatible provider works.

#2. Open the service's backup settings

Edit the Odoo service and find the Backup Settings section.

#3. Add configurations

Click Add backup destination for each destination. Choose its frequency and retention count, and mark one as Primary.

#4. Save

Save the service. Scheduled backups now run for every configuration with a frequency set.

A destination without a frequency is "manual only" โ€” it never receives scheduled backups, but you can target it explicitly when creating a manual backup.

#Manual backups with a chosen destination

When a service has more than one destination, the Create Backup dialog lets you choose where the backup should go. The primary destination is preselected.

#Provisioning templates

Provisioning templates support multiple backup destinations too. Configure the same set of backup configurations on the template, and every service provisioned from it starts with those destinations โ€” primary flag included.

Backups whose destination is later removed from a service remain visible and restorable. They are never rotated automatically โ€” only destinations with an active configuration are rotated.