Odoo Backup: The Complete 2026 Guide

Odoo holds your business: sales orders, invoices, inventory, payroll, and customer data. A single hardware failure, ransomware attack, or accidental deletion without a working backup can mean days of lost data and weeks of recovery work — if recovery is possible at all.

Yet the majority of small and mid-size Odoo deployments run with no automated backup at all. The most common backup "strategy" is: someone manually exports a ZIP from the Odoo web interface once in a while, remembers to do it less and less over time, and stops entirely after a few months.

This guide covers what a proper Odoo backup looks like and how to get there without a dedicated sysadmin on staff.

An Odoo instance has two data stores you must back up together:

1. The PostgreSQL database
This is the source of truth for all structured data: partners, products, orders, journal entries, users, configuration. It is backed up with pg_dump, which produces a compressed SQL file.

2. The filestore
Odoo stores attachments — PDF invoices, uploaded documents, product images — in a directory on disk (usually /opt/odoo/data/filestore/). If you only back up the database and lose the filestore, every attachment in your system will be broken.

A complete backup = pg_dump + filestore. Never back up one without the other, or your restore point is incomplete.

The right backup frequency depends on how much data loss your business can tolerate (the Recovery Point Objective, or RPO):

• Daily — minimum acceptable for most businesses. Lose at most 24 hours of data.
• Every 6 hours — good for businesses with high transaction volume (retail, distribution).
• Hourly — for critical operations where even an hour of data loss is significant.

For most Odoo SMBs, a daily backup running at 2 AM (when server load is lowest) plus a weekly full backup retained for 90 days is a solid starting point.

Never store backups only on the same server as your Odoo instance. If the server fails, you lose both Odoo and the backups.

Cloud storage is the right answer. The most common destinations for Odoo backups:

• Google Drive — free up to 15 GB, easy OAuth setup, familiar to most teams
• Microsoft OneDrive — good choice for Microsoft 365 organizations
• Amazon S3 — cost-effective at scale, fine-grained access control
• Backblaze B2 — S3-compatible, cheaper than AWS for storage-heavy workloads
• SFTP — for organizations that must keep data within a specific jurisdiction

Ideally, keep backups in at least two different destinations (the 3-2-1 rule: 3 copies, 2 media types, 1 offsite).

A backup you have never tested is not a backup — it is a hope.

At least once per quarter, pick a recent backup and restore it to a staging server. Verify that:

• Odoo starts correctly
• You can log in with a known user
• A recent transaction (invoice, sale order) is present
• Attachments (PDFs, images) open correctly

If the restore fails at any of these steps, your backup process has a gap you need to fix before a real disaster forces you to find out.

ServerChest handles the entire backup lifecycle from a web dashboard — no SSH, no cron editing, no manual uploads:

• Set a schedule (daily, every 6h, custom cron) and a time in your local timezone
• Configure one or more cloud destinations (Google Drive, OneDrive, S3, Backblaze, SFTP, Dropbox)
• Enable per-destination retention policies (keep 7 daily, 12 monthly)
• Every backup run sends a real-time step-by-step progress feed to your dashboard
• Each completed backup is verified: the cloud file is checked to exist and be non-zero size
• Failure alerts go out by email (or Slack, webhook) immediately

You get a full backup history table with size, duration, destination status, and a one-click restore — all without a terminal.