Agent skill · operations · sickn33
odoo-backup-strategy
Complete Odoo backup and restore strategy: database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures.
Why this skill is useful
Adds executable backup and restore scripts for Odoo that automate and enhance data safety beyond standard practices.
What it needs
Requires aws-cli, docker installed locally. Requires aws account access. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Odoo Backup Strategy Overview A complete Odoo backup must include both the PostgreSQL database and the filestore (attachments, images). This skill covers manual and automated backup procedures, offsite storage, and the correct restore sequence to bring a down Odoo instance back online. When to Use This Skill Setting up a backup strategy for a production Odoo instance. Automating daily backups with shell scripts and cron. Restoring Odoo after a server failure or data corruption event. Diagnosing a failed backup or corrupt restore. How It Works 1. Activate: Mention @odoo-backup-strategy and describe your server environment. 2. Generate: Receive a complete backup script tailored to your setup. 3. Restore: Get step-by-step restore instructions for any failure scenario. Examples Example 1: Manual Database + Filestore Backup Example 2: Automate with Cron (daily at 2 AM) Example 3: Upload to S3 (after backup) Example 4: Full Restore Procedure Best Practices ✅ Do: Test restores monthly in a staging environment — a backup you've never restored is not a backup. ✅ Do: Follow the 3-2-1 rule: 3 copies, 2 different media types, 1 offsite copy (e.g., S3 or a remote server). ✅ Do: Back up immediately before every Odoo upgrade — this is your rollback point. ✅ Do: Verify backup integrity: pgrestore --list backup.dump should complete without errors. ❌ Don't: Back up only the database without the filestore — all attachments and images will be missing after a restore. ❌ Don't: Store backups on the same disk or same server as Odoo — a disk or server failure destroys both. ❌ Don't: Run pgrestore --clean against a non-existent database — always create the database first. Limitations Does not cover Odoo.sh built-in backups — Odoo.sh has its own backup system accessible from the dashboard. This script assumes a single-database Odoo setup. Multi-database instances require looping over all databases. Filestore path may differ between installations (Docker volume vs. bare-metal). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/odoo-backup-strategy--41ee7f