Loading page
Automatic Database Backup
by TechnoVision · Odoo App
Almost every Odoo backup story ends the same way: there was a scheduled job, it had been failing for eleven weeks, and nobody knew because nothing was watching it. This one verifies, records and speaks up.
Security Center
Live82
Score
1.2k
Events / 24h
3
Alerts
Export volume · 14 days
Unusual export detected
res.partner · 4,812 rows · outside business hours
Illustrative UI. Product screenshots to be dropped into this frame.
What it does
The finished archive is re-opened, checked for corruption and checked to contain a real database dump before the run counts as a success.
One destination or several at once, each on its own schedule.
Chosen explicitly, with the consequence spelled out - only ZIP restores your attachments.
Every attempt with its file, size, duration, result and error, plus a size graph - because a dump that suddenly halves is the earliest warning you get.
Carrying the server own message. A nightly it-worked notice is deleted unread within a week, and then so is the one that matters.
Applied in days, and only after a successful run. Deleting a good backup because today failed is the wrong moment to be tidy.
Checks the folder or connection without dumping a whole database first.
The scheduled action ships switched off. Installing a module should not start dumping your database somewhere nobody has chosen.
Matched by database name and its own timestamp pattern. A backup tool that deletes the wrong file is a catastrophe, not a bug.
Screenshots
4 reserved slots at 16:10, ready for real captures of the dashboard, activity log, sensitive-change detail and report builder.
How it works
Depends on base and mail only. SFTP additionally needs paramiko, imported only when an SFTP destination actually runs.
A local folder or an SFTP server, with the format and retention you want. Configuration is Settings-level only.
Use Test Destination, then Back Up Now for a first real run.
Then leave it alone - you will hear from it when something breaks.
FAQ
No, deliberately. Restoring destroys a database, and that belongs at the command line rather than behind a button somebody can click by accident. The exact commands ship with the module.
No. A module there has no filesystem access, and Odoo backs those databases up itself. On Odoo.sh platform backups already exist, so this is useful there only for pushing an extra copy to your own SFTP.
You get an email carrying the server message, no cleanup runs, and any half-written file is deleted so the next sweep cannot mistake it for a backup.
Settings-level users only. A read-only History group exists for people who only need to know whether it ran.
Install from Odoo Apps, or talk to us about a guided rollout across multiple companies.