Odoo Disaster Recovery: Backups, RTO/RPO and Restore Tests by Hosting
Odoo disaster recovery by hosting: official backup, RPO and RTO facts for Odoo Online, Odoo.sh and on-premise, plus a step-by-step restore test plan.
Most companies find out how their Odoo recovery really works on the worst day of the year. Our Odoo ERP support team helps you set up Odoo disaster recovery, backups and restore tests before that day comes.
Related service: DevOps and hosting services — Odoo.sh, self-hosting and CI/CD run by people who do it daily.
This guide is for owners and IT leads who need a recovery plan that matches their hosting. If you are still choosing a platform, start with our Odoo Online vs Odoo.sh vs on-premise comparison.
What is Odoo disaster recovery, and how is it different from a go-live rollback plan?
Odoo disaster recovery is how you get Odoo and its data back after a failure, at any point in the system's life, not only at go-live. It covers server crashes, data center outages, ransomware, bad updates and human mistakes such as a mass delete.
A rollback plan is a one-time decision at cut-over, covered in our ERP rollback plan for Odoo cut-over. Disaster recovery is the ongoing plan for every day after it.
Odoo business continuity is the wider goal: keeping orders, invoices and stock moving while Odoo is down, with manual workarounds and a catch-up plan.
Two numbers frame every plan:
- RPO (Recovery Point Objective): how much recent work you can afford to lose, measured in time.
- RTO (Recovery Time Objective): how long the business can run without Odoo before the damage is serious.
What RTO and RPO does Odoo publish for each hosting type?

Odoo publishes RPO and RTO objectives for databases hosted on odoo.com, describes backup schedules for Odoo.sh in its docs, and leaves on-premise targets entirely to you. The table puts the official facts side by side.
| Factor | Odoo Online | Odoo.sh | On-premise |
|---|---|---|---|
| Who runs backups | Odoo | Odoo, for production | Your team or partner |
| Backup frequency | Daily | Daily for production | Whatever you set up |
| Retention | 7 daily, 4 weekly, 3+ monthly | 7 daily, 4 weekly, 3 monthly | Your policy |
| Stated RPO | 24 hours | Not stated in the docs | Your design |
| Stated RTO | 6 hours (server), 24 hours (data center) | Not stated in the docs | Your design |
| Restore testing | Duplicate a database for testing | Restore a production backup into staging | Restore to a separate server |
On the Odoo Cloud Hosting SLA, Odoo states an RPO of 24 hours and an RTO of 6 hours for a single server failure. For a full data center failure, the RPO stays at 24 hours and service should be restored from backup within 24 hours in another data center.
The same page sets a 99.9% monthly uptime target, or at most 45 minutes of unplanned downtime a month. Near real-time replication within the region aims for minimal to no data loss after a hardware failure.
Read one line carefully: Odoo says these objectives "are not legally binding guarantees". Plan around this Odoo SLA, but do not treat it as a contract promise.
How do Odoo Online backups and restores work?
On Odoo Online, Odoo backs up every database daily and keeps copies in several data centers, while you control downloads and test copies from the database manager. You cannot change the schedule or the backup regions.
The SLA lists 14 full backups kept for at least 3 months: daily for 7 days, weekly for 4 weeks and monthly for 3 or more months. Copies sit on at least 3 machines in data centers in Europe and Canada, plus a fourth in immutable cold storage.
You cannot choose or restrict the regions where backups are replicated. If backups must stay in one country, check this early with our Odoo GDPR and hosting guide.
The Odoo Online database manager gives you these recovery tools:
- Download Backup: a ZIP of the database; if disabled, the database is too large and Odoo Support offers another route.
- Duplicate: a test copy with emails, payments and deliveries disabled by default.
- Limits: duplicates expire after 15 days, with at most five per database.
- Delete: permanent; a deleted database cannot be restored.
Odoo's docs list no self-service restore of an older backup on Online. Recovering an earlier copy means a ticket with Odoo Support, so count that wait in your RTO.
How do Odoo.sh backups work?
Odoo.sh backs up the production branch daily and keeps 7 daily, 4 weekly and 3 monthly copies, each with the database dump, the filestore, logs and sessions. Staging and development branches are a different story.
The Odoo.sh branches documentation says the production server keeps one month of Odoo.sh backups. Dedicated backup servers add 3 monthly backups, which you request through Odoo Support.
| Branch stage | Automatic backup | Manual backup |
|---|---|---|
| Production | Yes, up to 3 months | Yes, kept 3 days |
| Staging | No | Yes, kept 3 days |
| Development | No | No |
Manual backups are limited to five a day. Take one before any risky change, such as a large import or a mass update by script.
When a merged commit changes a module version, Odoo.sh takes an automatic backup first. If the update fails, it reverts to the last good revision and rolls the database back.
Watch storage too; our guide for when Odoo.sh storage is full shows how to find and clean what uses space.
How do you back up on-premise Odoo?
On-premise, you own the whole Odoo database backup and restore chain, so the plan must cover the PostgreSQL database, the filestore, the code and the server configuration. Nobody else holds a copy unless you send one.
Odoo's on-premise deployment guide says to back up databases and filestore daily and copy them to a remote server not accessible from the Odoo server. That protects you if ransomware reaches the main server.
The guide also warns that the web database manager is a demo tool, not built for production or large databases. Turn it off with `list_db = False` and leave backups to your administrator.
A sound on-premise Odoo backup policy usually includes:
- Database: a PostgreSQL dump at least daily, plus WAL archiving if your RPO is under a day.
- Filestore: copied at the same time as the dump, so attachments match records.
- Code and config: custom modules in Git, plus the config file and Python packages.
- Off-site copies: one copy in another location, with deletion locked.
- Monitoring: an alert when a backup job fails or a file is too small.
On-premise can beat Odoo Online's targets, but only with standby servers and people on call. Sizing affects restore speed too; see our Odoo performance tuning checklist.
What does a complete Odoo backup restore need?
A complete Odoo backup restore needs the database, a matching filestore, the same code and modules, and a working set of integrations, all from the same moment. Miss one and Odoo starts, but parts of the business do not.
The common gap is the filestore. One Odoo forum user restored a recent dump with an older filestore and found some attachments were still missing because the database was newer than the files.
Check these items in every restore:
- Database and filestore: taken together, restored together.
- Custom and third-party modules: the exact versions that ran when the backup was taken.
- Outgoing mail and scheduled actions: confirm they will not resend emails or rerun jobs that already ran.
- Integrations: eCommerce, bank feeds and carriers may hold orders from the lost RPO window.
- Access and DNS: logins, API keys and the domain all point at the restored server.
How do you run an Odoo restore test?
An Odoo restore test proves that a backup can become a working system within your RTO, and it should run at least quarterly. Treat it as a drill with a stopwatch.
- Pick the backup: use a real production backup, not one made specially for the test.
- Restore to a safe place: an Online duplicate, an Odoo.sh staging branch, or a separate on-premise server.
- Keep it neutral: make sure emails, payments and carriers stay in test mode so customers are not contacted.
- Time every step: from the decision to restore until users can log in and post a sales order.
- Check the data: compare record counts, trial balance, stock value and the last invoice number with production.
- Open attachments: pick 20 random documents and confirm each file opens.
- Test key flows: quote to invoice, purchase to receipt, a payment and a report your managers use daily.
- Record and fix: log the time taken, every problem found and who will fix it before the next drill.
On Odoo.sh, restore a production backup into staging. On Odoo Online, use Duplicate with the testing option on. On-premise, restore onto a second server.
Odoo's upgrade documentation notes a production upgrade cannot be reverted, so test a backup before each version move with our Odoo upgrade services.
How do you set RTO and RPO for your Odoo business continuity plan?
Set Odoo RTO and RPO from the cost of downtime and lost data in your own business, then check whether your hosting can meet them. Start with the processes that hurt most when they stop.
| Business process | Illustrative RPO | Illustrative RTO | What it usually needs |
|---|---|---|---|
| eCommerce orders and payments | Under 1 hour | Under 4 hours | Replication or frequent backups, plus order re-sync |
| Warehouse shipping | 4 hours | Same working day | Paper pick lists as a fallback |
| Accounting and invoicing | 24 hours | 1 to 2 days | Daily backups usually enough |
| Payroll | 24 hours | Before the next pay run | Payroll export kept off Odoo |
| Manufacturing orders | 4 to 8 hours | Same shift | Printed work orders and BOMs |
These figures are illustrative, not industry benchmarks. If a process needs an RPO under 24 hours, Odoo Online's stated objective may not be enough, and you may need extra backups or replication.
Write the plan down: who declares a disaster, who calls support, how staff work meanwhile and how missed transactions are re-entered.
Who owns which part of Odoo disaster recovery?
Odoo owns the hosting layer on Odoo Online and Odoo.sh, but you always own the decisions, the testing and the business workarounds. This split is where most plans have gaps.
| Task | Odoo Online | Odoo.sh | On-premise |
|---|---|---|---|
| Server and data center recovery | Odoo | Odoo | You |
| Daily backups | Odoo | Odoo, for production | You |
| Custom module code | Not allowed | Your Git repository | Your Git repository |
| Off-platform copy | You download it | You download it | You keep it |
| Restore tests | You | You | You |
| Integration catch-up | You | You | You |
| Odoo high availability | Odoo, in region | Odoo platform | You design it |
Odoo high availability on-premise needs a standby PostgreSQL server, a load balancer and synced filestore storage; our DevOps services team can scope it.
Odoo disaster recovery needs by industry
Recovery targets differ by industry because the cost of an hour without Odoo differs. The table shows where we usually start the conversation.
| Industry | Pain or cost driver | Odoo approach | How iVentureTeam helps |
|---|---|---|---|
| eCommerce and retail | Lost orders and double-sold stock | Short RPO, order re-sync from the store | Map channels and test re-sync after restore |
| Manufacturing | Stopped production lines | Printed work orders, same-shift RTO | Drill a restore during a planned shutdown |
| Distribution | Missed shipments and carrier cut-offs | Fast restore of Inventory and Delivery | Build a manual shipping fallback |
| Professional services | Timesheets and billing gaps | Daily backups usually enough | Set up downloads and quarterly tests |
How iVentureTeam helps with Odoo disaster recovery

iVentureTeam turns Odoo backups into a tested recovery plan, on Odoo Online, Odoo.sh or your own servers. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.
- Recovery review: we map your RTO and RPO needs against your hosting and current backups.
- Backup setup: on-premise backup jobs, off-site copies and alerts, or Odoo.sh manual backup routines.
- Restore drills: timed quarterly tests with a written report and fixes.
- Ongoing support: monitoring and incident help through our Odoo support guide and support plans.
- Health check: start with our free Odoo health check tool to spot weak points.
Odoo business continuity case study: DeenSqure
A multi-region D2C brand kept its old Odoo running while the new one was built, so the business never stopped during a major change. DeenSqure sells across the USA and UAE.
DeenSqure had run Odoo 14 for 5 years with 23 custom modules. Two earlier upgrade attempts had failed during version testing, and stock drift across Shopify, Amazon and its stores caused overselling.
We used a parallel-run strategy: Odoo 14 stayed in use while Odoo 19 was built alongside. Automated migration scripts were validated row by row across 6 years of records, and an inventory reconciliation pass before cut-over caught 14% drift.
The project took 11 weeks. Three months after go-live, stock accuracy across all 6 channels sat at 99.7%. Read the DeenSqure Odoo 14 to 19 migration case study.
The bottom line on Odoo disaster recovery
Odoo Online and Odoo.sh give you good backups by default, but only a timed restore test tells you whether you can recover in time. On-premise gives you full control and full responsibility.
Set RTO and RPO per process, check them against your hosting, keep an off-platform copy and drill a restore every quarter.
Ready to test your Odoo recovery plan?

Find out how long your Odoo restore really takes before you need it. Schedule an Odoo restore drill with our support team, call +91-90235-15208, or email business@iventureteam.com.
Frequently Asked Questions
Does Odoo back up my database automatically?
+
On Odoo Online, yes: databases are backed up daily under the Cloud Hosting SLA. On Odoo.sh, the production branch is backed up daily, but staging and development are not. On-premise, nothing is backed up unless you set it up.
What is the RPO and RTO for Odoo Online?
+
Odoo's Cloud Hosting SLA states an RPO of 24 hours and an RTO of 6 hours for a single server failure, and 24 hours for a data center failure. Odoo says these objectives are not legally binding guarantees.
How long does Odoo.sh keep backups?
+
Odoo.sh keeps 7 daily, 4 weekly and 3 monthly backups of production. The production server holds one month; the 3 monthly backups sit on backup servers and are restored through Odoo Support. Manual backups last 3 days.
Can I restore an old backup myself on Odoo Online?
+
Odoo's docs list download and duplicate actions but no self-service restore of an older backup on Odoo Online. To roll back to an earlier copy, contact Odoo Support and allow for that wait in your RTO.
What should an Odoo backup include?
+
The PostgreSQL database and the filestore, taken at the same moment, plus your custom module code and server configuration. Without a matching filestore, attachments such as invoices and signed PDFs go missing after a restore.
How often should I test an Odoo backup restore?
+
At least once a quarter, and before every major upgrade or hosting move. Time the full restore, check data and attachments, and test key flows such as quote to invoice.
Can I choose where Odoo Online stores my backups?
+
No. Odoo's SLA says backups are replicated in data centers in Europe and Canada, and you cannot choose or restrict those regions. Your live database stays in the hosting region you picked.
Is Odoo.sh better than Odoo Online for disaster recovery?
+
Odoo.sh adds manual backups, staging restores and automatic backups before module updates, which help with risky changes. Odoo Online publishes clearer RPO and RTO objectives. The better choice depends on your custom code and targets.
How do I make on-premise Odoo highly available?
+
Use a standby PostgreSQL server with replication, synced filestore storage, a load balancer and a tested failover procedure. Keep off-site backups too, because replication copies mistakes and ransomware as fast as good data.
Free project rescue review
Is your Odoo project off track?
Tell us where the project stands. A senior consultant reviews it and sends a recovery plan with the effort involved, before you commit to anything.
Free, with no obligation. A senior consultant replies within 12 business hours.
Free Odoo tools
All tools- Odoo Health CheckVersion, modules, findings and upgrade cost
- Odoo App SelectorWhich apps you need, by industry
- Odoo Project EstimateIndicative cost and timeline in minutes
- Odoo Implementation Cost CalculatorImplementation cost and timeline, in minutes
- Odoo Migration Cost CalculatorVersion jump or legacy ERP, priced in minutes
Continue reading
Odoo Hosting and Saudi PDPL: Data Residency Checklist for KSA Firms
Saudi PDPL and Odoo hosting: where Odoo Online and Odoo.sh store KSA data, backup transfers, the draft storage rule, and a 10-step compliance checklist.
How to Install Third-Party Modules on Odoo.sh, On-Premise and Online
How to install third-party and custom modules on Odoo.sh, on-premise and Odoo Online in Odoo 19 and 20: GitHub, submodules, addons path, limits and fixes.
Odoo.sh Storage Full: Find What Uses Space, Clean Up, or Upgrade
Odoo.sh storage full? What counts, what it costs per GB, how to find what uses space, how to clean attachments safely, and when to upgrade to Dedicated.
