Skip to main content
DevOps // Disaster recovery

A backup you've never restored is just a rumor.

We design backup and disaster recovery around agreed recovery targets, automate it, and rehearse it, so the worst day becomes a well-practiced procedure.

~/anvexis/devops/backup-disaster-recovery

$ anvexis tldr

3-2-1 copies, encrypted, monitored, and restored on a schedule.

$ anvexis facts

Rule
3 copies · 2 media · 1 offsite
Targets
RPO & RTO agreed
Proof
Scheduled restore drills

Building a recovery plan

  1. Stage 01

    Set targets

    Agree how much data you can lose (RPO) and how long you can be down (RTO).

  2. Stage 02

    Automate backups

    Databases, file stores, and configuration, encrypted and copied offsite.

  3. Stage 03

    Monitor

    Alert when a backup is missing, late, or suspiciously small.

  4. Stage 04

    Write the runbook

    Step-by-step recovery instructions anyone on call can follow.

  5. Stage 05

    Drill

    Restore to a clean environment on a schedule and time it.

Ransomware changes the rules

Keep at least one immutable or offline copy that production credentials can't delete. Attackers know where backups live too.

Why backups fail when you need them

Almost every company has backups. Far fewer have tested restores. The common surprises are always the same: the backup job had been failing quietly for months, the backups were on the same server that died, the files restored but the application wouldn't start, or the restore took a full day nobody had planned for.

Disaster recovery is the discipline of making sure that doesn't happen. It covers what is backed up, where copies are kept, how quickly systems can be rebuilt, who does what during an incident, and how often all of it is tested. For Odoo, that means the database, the filestore with all its attachments, configuration, and custom code, restored together and consistent.

We design recovery around two agreed targets: how much data you can afford to lose and how long you can afford to be down. Then we prove the plan works with regular drills.

Backup layers

LayerWhat it protects against
Point-in-time database recoveryAccidental deletes, bad imports, faulty upgrades
Nightly full backupsCorruption that spreads over time
Off-site copies in another regionLosing a data center or cloud region
Immutable or offline copiesRansomware and compromised admin accounts
Configuration and code in GitRebuilding servers and applications from scratch

What a recovery plan includes

Recovery targets

Agreed RPO and RTO for each system, signed off by the business.

Complete backups

Database, filestore, configuration, and secrets, kept consistent with each other.

Geographic separation

Copies in a different location and account from production.

Immutability

Backups that cannot be deleted or encrypted by an attacker with admin access.

Runbooks

Step-by-step recovery instructions anyone on the team can follow.

Regular drills

Scheduled restore tests with measured times and written results.

Building and proving the plan

  1. Stage 01

    Inventory

    Week 1

    List systems, data, dependencies, and current backup coverage.

  2. Stage 02

    Targets

    Week 1

    Agree recovery targets with the business for each system.

  3. Stage 03

    Implement

    Week 2–3

    Configure backups, off-site copies, immutability, and monitoring.

  4. Stage 04

    Drill

    Week 3

    Restore to an isolated environment and time every step.

  5. Stage 05

    Schedule

    Ongoing

    Set a drill calendar and keep runbooks current.

Backup myths

Myth: Replication is a backup.

Reality: Replication copies mistakes instantly. A deleted table on the primary is deleted on the replica too. You need point-in-time backups as well.

Myth: Cloud providers back everything up for us.

Reality: Providers protect their infrastructure. Protecting your data, including from your own mistakes, is usually your responsibility.

Myth: Testing restores is too disruptive.

Reality: Restores are tested in an isolated environment, without touching production.

Common pitfalls we help you avoid

The first pitfall is backing up the database but not the files. Odoo stores attachments in its filestore, and a database restored without matching files leaves broken documents everywhere.

The second is keeping backups within reach of an attacker. If the same admin account can delete production and its backups, ransomware can take both, so copies are separated and made immutable.

The third is never timing a restore. A plan that assumes a one-hour recovery is useless if the actual restore takes nine, so every drill records how long each step really took.

What we measure

MeasureWhy it matters
Last successful backupConfirms backups are actually running
Measured restore timeThe real recovery time from drills
Data loss windowGap between backups, against the agreed target
Drill completionWhether scheduled tests actually happen

Who does what

We handle

  • Backup design and configuration
  • Restore drills and measurement
  • Runbooks and monitoring

Your team handles

  • Agreeing recovery targets
  • Joining drills and verifying data
  • Keeping contacts and priorities current

A worked example

Consider a company whose backups run every night to a disk on the same server. A recovery plan adds point-in-time archiving to a separate cloud account, immutable weekly copies, and a quarterly restore drill to an isolated environment.

The first drill reveals that the filestore wasn't included and the restore took far longer than assumed. Both are fixed, the runbook is updated, and the next drill meets the targets agreed with the business.

Before you start

  • A list of systems and their data
  • Agreed recovery targets per system
  • A separate location for off-site copies
  • Time set aside for regular drills

What success looks like

Success is confidence backed by evidence: restores tested on schedule, recovery times measured against the agreed targets, and a runbook that anyone on the team can follow at three in the morning. When something does go wrong, recovery is a routine procedure.

Rules that have stood the test of time

A long-standing US government guide recommends the 3-2-1 rule: keep three copies of important files, one primary and two backups, on two different media types, with one copy stored offsiteSource [1]. Cloud storage makes it easy to follow, as long as the offsite copy is genuinely separate from the systems it protects.

For databases, PostgreSQL's continuous archiving supports point-in-time recovery to any moment since the base backupSource [2]. The documentation is explicit that the WAL archiving procedure should be set up and tested before the first base backup, and recommends keeping several backup sets to be certain of recoverySource [2]. We schedule restore drills so recovery time is known, not guessed.

Frequently asked questions

How often should we back up?
As often as your recovery point target requires. Continuous archiving supports minutes-level targets.
Does Odoo need special handling?
Yes: the database and the filestore must be backed up together and consistently.
Where should backups be stored?
In a separate account or provider from production, with restricted delete permissions.
How long should we keep backups?
Long enough for your recovery and legal retention needs, balanced against storage cost.
Can you run a drill for us?
Yes, with a report on recovery time and gaps found.
How often should we test restores?
At least quarterly for critical systems, and after any major change to infrastructure or backup tooling.
How long are backups kept?
It depends on your policy and legal requirements. A common pattern keeps daily backups for weeks and monthly backups for longer.
Does Odoo.sh handle backups?
Odoo.sh provides backups. You may still want independent off-site copies and your own restore tests, depending on your risk tolerance.
What about laptops and office files?
Our focus is servers and business systems. We can advise on endpoint backup or work with your IT provider.
What happens during a real incident?
The runbook is followed: assess, communicate, restore in order of priority, verify data, and review afterwards.
Can you recover a single deleted record?
Yes. Point-in-time recovery restores a copy from just before the mistake, so the record can be retrieved without rolling back everything.
Where should off-site backups be stored?
In a separate account and region from production, ideally with immutability enabled.
How do we know backups aren't corrupted?
By restoring them regularly and checking that the application starts and the data is complete.
Do you back up SaaS tools like Microsoft 365 or Google Workspace?
We can advise on dedicated SaaS backup tools and integrate them into your overall recovery plan.
What is a reasonable recovery target for Odoo?
It depends on your business. Many companies aim for minutes of data loss and a few hours of downtime; the plan is built to whatever you agree.
Can backups be encrypted?
Yes. Backups are encrypted in transit and at rest, with keys stored separately from the backups themselves.
Is cloud storage enough as a backup?
It can be one layer. The 3-2-1 rule asks for multiple copies, different media, and one copy offsite from your main systemsSource [1].
Can we recover to just before a mistake?
With point-in-time recovery, yes: PostgreSQL can restore to any moment since the base backupSource [2].

Sources

  1. [1]Data Backup Options (opens in a new tab)US-CERT / CISA (Ruggiero & Heckathorn), 2012
  2. [2]Continuous Archiving and Point-in-Time Recovery, PostgreSQL 18 documentation (opens in a new tab)The PostgreSQL Global Development Group