TedRed Apps
Odoo Backup Pro — Backup & Disaster Recovery
Full backups, one-click restore, S3 cloud storage, SSH server migration and staging databases for Odoo 18.
Odoo 18.0 · Community & Enterprise · by TedRed
Odoo Backup Pro is a complete backup and disaster recovery suite for self-hosted Odoo 18. It captures your PostgreSQL database, filestore, custom addons and configuration in one run, verifies every archive with a SHA256 checksum, and stores it locally and on AWS S3 or Wasabi. When things go wrong, restore in one click — or migrate the whole instance to a new server over SSH and spin up neutralized staging databases for safe testing.
See it in action
A short tour: backup history, one-click backup and restore, storage configuration, SSH servers, staging databases and the full workflow.
Every backup, verified and accounted for
The backup history lists every run — scheduled, manual or pre-update — with size, duration, storage location, checksum verification status and a one-click Restore button. Filter by status, type or storage in one click.
One record per backup — start, verify, restore
Each backup tracks its UUID, timing, live progress, included components (database, filestore, addons, config) and per-component sizes. Verify integrity or open the restore wizard straight from the form — with a full audit trail in the chatter.
Storage that fits your setup — local, S3, Wasabi or both
Auto-detect your paths, pick the components to include, and point the configuration at a local directory, an S3 bucket, a Wasabi endpoint — or both for belt-and-braces safety. Schedules, retention, notifications and Traefik settings live on the same form.
Migrate servers over SSH
Register target servers with password or key auth, test the connection (disk space and PostgreSQL checks included), then push a backup and restore it remotely.
Staging databases on demand
Clone production into a neutralized staging copy — mails and crons disabled — with a symlinked or fully copied filestore and an instant traefik.me URL.
How it works
Configure storage once, let schedules do the work, and every verified backup becomes a restore point, a migration source or a staging copy.
Everything a self-hosted Odoo needs to sleep at night
Full instance backup
One run captures the PostgreSQL database (pg_dump), the filestore with all attachments, your extra addons directory and odoo.conf — with a JSON manifest recording UUID, checksums and components.
One-click restore with a safety net
Pick a backup, run a dry-run pre-flight validation, and restore. The wizard can take an automatic pre-restore backup and requires typing the database name before anything destructive happens.
S3 and Wasabi cloud storage
Upload to AWS S3 or any S3-compatible endpoint such as Wasabi. Large archives are sent in 100 MB chunks with multipart upload, and you can restore straight from the bucket.
Scheduled backups and retention
Daily, weekly, monthly or custom-interval schedules, each tied to a configuration and backed by an Odoo cron. Retention policies clean up old archives; success rates are tracked per schedule.
SHA256 integrity verification
Every archive gets a SHA256 checksum, re-checkable at any time from the backup form — so a corrupted file never masquerades as a good restore point.
SSH server migration
Move to a new host without console gymnastics: transfer the backup over SSH/SFTP, restore the remote database, deploy filestore and addons, and restart the remote Odoo service automatically.
Neutralized staging copies
Create staging databases from production with Odoo's native neutralization (90+ module scripts): outgoing mail and crons disabled, API keys sanitized. Filestore is symlinked instantly or fully copied.
Email alerts and audit trail
Get notified on success or failure with ready-made mail templates. Every backup, server and staging record carries a full chatter log for compliance.
Runs in the background
Long operations — backups, migrations, staging builds — run in background threads with live progress bars and current-step display, so the UI never blocks.
Built and tested on Odoo 18. Works on self-hosted Community and Enterprise (requires server access; not for Odoo.sh or Odoo Online).
All labels and messages are fully translatable through standard Odoo i18n.
Local backups need no external service. S3/Wasabi (boto3) and SSH migration (paramiko) are optional add-ons you enable when you need them.
Frequently asked questions
Does restore work on a different server?
Yes. The SSH migration wizard transfers a completed backup to a remote server you have registered and tested, restores the database there, deploys the filestore and addons, and restarts the remote Odoo service — a practical path for moving hosts or standing up a disaster-recovery machine.
What exactly is included in a backup?
Four components, each toggleable per configuration: the PostgreSQL database via pg_dump, the Odoo filestore (attachments and images) as tar.gz, your extra addons directory, and odoo.conf. A JSON manifest with SHA256 checksums ties the set together.
What does the module need on my server?
A self-hosted Odoo 18 with access to pg_dump/pg_restore and disk space for local archives. The Python packages boto3 (for S3/Wasabi) and paramiko (for SSH migration) are required and installable with pip. Odoo.sh and Odoo Online are not supported because they do not expose the server.
TedRed
Tech, design, media & marketing under one roof. Questions, customization or onboarding help? We respond within one business day.
support@tedred.comtedred.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 4820 |
| Technical Name |
odoo_backup_pro |
| License | LGPL-3 |
| Website | https://tedred.com |
Please log in to comment on this module