Automated Database Backup & Restore for Odoo

Name: Automated Database Backup & Restore for Odoo
Brand: ECOSIRE
SKU: automated-database-backup

Key Features

Scheduled backups driven by an Odoo `ir.cron` automated action with per-database cron expressions (hourly, daily, weekly) and configurable run windows

Simultaneous multi-destination writes: local disk, one or more remote SFTP/SCP servers, and any S3-compatible object store (AWS S3, Backblaze B2, Wasabi, MinIO, DigitalOcean Spaces)

AES-256 encryption of every backup archive with server-side key management, so dumps are unreadable at rest and in transit

Encrypted transfer tunnel (SFTP over SSH / TLS to S3) for all off-site transfers — no plaintext database ever crosses the wire

Full database + filestore capture in each snapshot (pg_dump of the PostgreSQL DB plus the attachment filestore) so restores are complete, not partial

Configurable per-destination retention policies — keep N daily, N weekly, N monthly copies with automatic pruning of expired archives

Email alerts on every backup success and failure, with the log excerpt, archive size, duration, and destination status included

One-click guided restore from any retained snapshot, rebuilding both the database and the filestore in the correct order

Optional automatic restore-verification: each backup is test-restored into a disposable database to prove recoverability before it is trusted

`backup.config`, `backup.destination`, and `backup.log` models with `@api.depends` computed status/last-run/next-run fields visible in an OWL settings dashboard

QWeb-rendered backup history and audit report (PDF) listing every run, outcome, size, and destination for compliance evidence

Security via `ir.model.access.csv` + record rules — only the Backup Administrator group can view destination credentials or trigger a restore

Multi-database support: independent schedules, destinations, encryption keys, and retention rules per database on the same Odoo server

JSON-RPC / XML-RPC status endpoint and optional webhook so external monitoring (Uptime, Grafana, PagerDuty) can query backup health

Bandwidth-friendly transfers with compression and optional off-peak scheduling to avoid impacting production during business hours

Credential storage isolated from the standard config and never exposed in list views, logs, or exports

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

A self-hosted Odoo instance without off-site backups is one disk failure, bad migration, or ransomware event away from losing your entire business. Odoo's built-in /web/database/backup is manual, single-target, unencrypted, and depends on someone remembering to click it — which is exactly why so many recovery stories end badly.

Automated Database Backup & Restore is a build-to-order Odoo module that ECOSIRE designs, develops, installs, and supports on your Community or Enterprise instance (Odoo 17, 18, and 19). It turns backups into a hands-off, encrypted, verifiable discipline: scheduled dumps run from a ir.cron automated action, are AES-encrypted, streamed over an encrypted tunnel to multiple destinations — local disk, remote SFTP servers, and any S3-compatible object store (AWS S3, Backblaze B2, Wasabi, MinIO, DigitalOcean Spaces) — pruned by configurable retention policies, and confirmed by email alerts on every success and failure. When you do need to recover, a guided one-click restore rebuilds the database and filestore from any retained snapshot.

Because this is engineered specifically for your environment, we ship real Odoo architecture, not a black box. The module defines its own backup.config, backup.destination, and backup.log models (models.Model) with computed status fields via @api.depends, a settings UI built in XML/OWL views, QWeb-rendered backup history reports, and JSON-RPC/XML-RPC endpoints so your monitoring stack can query backup health programmatically. Access is locked down with ir.model.access.csv plus record rules so only the backup administrator group can view credentials or trigger a restore, and multi-database Odoo servers are handled — each database gets its own schedule, targets, and retention.

Every backup includes both the PostgreSQL dump and the filestore (attachments, documents, images), so a restore brings back a complete, working system — not just rows in a table. Optional automatic restore-verification spins each backup up into a throwaway database to prove it actually restores, closing the gap between "we have backups" and "our backups work."

ECOSIRE builds this to your exact retention rules, destinations, encryption keys, and alerting preferences, hardens it against your infrastructure, and hands over documented, supported code — typically within 2 to 4 weeks. This is not an instant apps.odoo.com download; it is a built-for-you engagement with a real delivery, testing, and handover process.

What you get

Complete, documented Odoo module (17/18/19-compatible) with `__manifest__.py`, models, views, security rules, cron actions, and QWeb reports, delivered as installable source in a private Git repository

Configuration of your live backup schedule, destinations (SFTP hosts and/or S3 buckets), encryption keys, and retention policy on your server

Encrypted, tested off-site connectivity — we provision and validate the SFTP/S3 targets and confirm end-to-end encrypted transfer

A verified full restore performed once during handover to prove backups actually recover on your infrastructure

Administrator documentation and a written disaster-recovery runbook (how to restore, rotate keys, add destinations, read alerts)

A live training/handover session for your admin team covering scheduling, monitoring, alerts, and the restore procedure

A post-delivery support and bug-fix window (defect fixes and adjustments), plus optional ongoing support/maintenance retainer

Who this is for

Self-hosted Odoo system administrator

Runs Odoo Community or Enterprise on their own VPS, EC2, or on-prem server and is personally accountable if data is lost. Wants scheduled, encrypted, off-site backups with proof they can restore — without babysitting a manual export every day.

Odoo implementation partner / MSP

Manages Odoo for multiple client databases and needs a repeatable, auditable backup discipline across every instance, with per-client destinations, retention, and failure alerts they can monitor centrally.

Finance or operations owner at an SMB

Non-technical business owner who knows their ERP holds invoices, inventory, and payroll, and needs assurance — in the form of alerts and a documented recovery runbook — that a server failure or ransomware attack will not end the company.

How Automated Database Backup & Restore for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor
Scheduled, unattended backups	Included	Partial support	Partial support
Encrypted off-site to SFTP + S3-compatible storage	Included	Partial support	Partial support
Configurable retention with automatic pruning	Included	Partial support	Partial support
One-click restore of database + filestore	Included	Partial support	Partial support
Email alerts on success and failure	Included	Partial support	Partial support
Automatic restore-verification (test-restore)	Included	Not included	Not included
Role-locked access via record rules to backups/restore	Included	Partial support	Partial support
Multi-database schedules, keys and retention	Included	Partial support	Partial support
Built, installed, tested and supported for you	Included	Not included	Not included
Runs on Odoo 17, 18 and 19 (Community + Enterprise)	Included	Partial support	Partial support

Frequently Asked Questions about Automated Database Backup & Restore for Odoo

How long until the module is delivered and installed?

This is a build-to-order engagement, not an instant download. Typical delivery is 2 to 4 weeks from the point we confirm your requirements (Odoo version, destinations, retention rules, encryption preferences). The timeline covers development, testing against your Odoo 17/18/19 environment, installation, a verified test restore, documentation, and a handover session. Straightforward single-database setups land nearer 2 weeks; multi-database or unusual destination/security requirements nearer 4.

What support and updates do I get after delivery?

Every engagement includes a post-delivery support and bug-fix window during which we fix any defects and make reasonable adjustments at no extra charge. Because we build to your specific environment, you own the delivered source and it will keep working on your instance. When you upgrade Odoo (for example 18 to 19) or want new destinations, retention rules, or alerting channels, we offer an optional ongoing support/maintenance retainer to keep the module current and compatible.

Which storage destinations and Odoo editions are supported?

The module writes to local disk, remote SFTP/SCP servers, and any S3-compatible object store — AWS S3, Backblaze B2, Wasabi, MinIO, and DigitalOcean Spaces are all supported. It runs on Odoo Community and Enterprise, versions 17, 18, and 19. You can enable several destinations at once (for example local plus S3 plus an off-site SFTP box) each with its own retention policy.

Are the backups actually encrypted, and can they really be restored?

Yes on both counts. Each archive is AES-256 encrypted before it leaves the server, and all off-site transfers travel over an encrypted tunnel (SFTP over SSH or TLS to S3), so no plaintext database is ever exposed. Every snapshot bundles the PostgreSQL dump and the filestore, so a restore rebuilds a complete, working system. We include optional automatic restore-verification that test-restores backups into a disposable database, and we perform one full verified restore with you during handover.

Will scheduled backups slow down my production Odoo instance?

Backups run from an `ir.cron` job, so you schedule them for off-peak windows (for example overnight). Transfers are compressed and can be throttled, and large filestores can be streamed incrementally to keep memory and bandwidth impact low. On busy servers we tune the schedule and concurrency during setup so backups do not compete with business-hours traffic.

How is access to backups and the restore function secured?

Access is controlled with `ir.model.access.csv` and record rules that restrict backup configuration, destination credentials, and the restore action to a dedicated Backup Administrator group. Destination secrets (SFTP keys, S3 credentials, encryption keys) are stored isolated from standard config and are never shown in list views, logs, or exports. Regular users cannot see or trigger backups or restores.

Can external monitoring tools check that backups are succeeding?

Yes. The module exposes backup status through JSON-RPC / XML-RPC and an optional webhook, so tools like Grafana, Uptime Kuma, or PagerDuty can query last-run time, outcome, and next-run schedule. Combined with the success/failure email alerts and the QWeb audit report, you get layered proof that backups are running — not just an assumption.