Simply taking a backup isn't enough. If your primary server burns down, how long will it take to build a new server and restore the data? That is your true risk.
Recovery Point Objective (RPO) defines how much data you can afford to lose. With WAL archiving, we guarantee an RPO of less than 5 minutes.
Recovery Time Objective (RTO) is how fast we can get you back online. Our automated Infrastructure-as-Code (IaC) spins up replacement servers in under an hour.
If a hacker compromises your Odoo server, they will try to delete your backups too. We use strict IAM roles to ensure the Odoo server can "write" to the backup vault, but cannot "delete" from it.
A stolen database dump means stolen customer data. We encrypt all PostgreSQL dumps with AES-256 before they ever leave the primary server.
A backup is useless if it's corrupted. We run automated scripts that restore your backup to a hidden staging server weekly, just to verify it actually works.
For ISO 27001 or SOC2 compliance, you must prove you have an offsite disaster recovery plan. We provide the architecture and the documentation to pass your audits.
How data moves safely from your active server to an immutable, off-site vault.
If your primary hosting provider physically burns down (as happened to OVH in 2021), we use our IaC scripts to rebuild your Odoo infrastructure in a completely different geographic region, pulling the latest backup from S3.
A hacker breaches your network and encrypts the Odoo server. Because they don't have the AWS IAM permissions to delete the offsite S3 backups, we simply wipe the infected server and restore from yesterday's clean backup.
An employee accidentally deletes 1,000 products instead of archiving them. Standard backups would mean losing a whole day of work to revert. With Point-in-Time recovery, we restore the database to the exact minute before they hit delete.
A hard drive sector goes bad, subtly corrupting PostgreSQL data over weeks. Because we run automated weekly restoration tests, we catch the corruption immediately, rather than discovering it 6 months later when it's too late.
Odoo.sh provides daily backups automatically. However, many enterprises require an independent, offsite backup stored in a vault they fully control (like their own AWS account) to comply with strict ISO security policies. We provide this independent layer.
Odoo stores data in two places: The PostgreSQL database (text data) and the Filestore (physical files like PDF invoices, product images, and Excel exports). A proper backup strategy MUST grab both at the exact same time, otherwise links will break upon restoration.
This is fully customizable based on your legal requirements. A standard strategy is: Keep daily backups for 30 days, keep weekly backups for 3 months, and push monthly backups to deep freeze (Amazon Glacier) for 7 years for tax compliance.
A full `pg_dump` can lock tables and cause lag. To prevent this, we schedule full dumps at 2:00 AM during lowest traffic, and use lightweight WAL (Write-Ahead Logging) archiving during the day, which has zero performance impact.
Don't wait until a server crashes to find out your backup script stopped working 6 months ago. Let us audit and secure your data pipeline.