Typical delivery is 2–4 weeks. This is not an instant app-store download; it is a module ECOSIRE develops, hardens and installs for you. After purchase we hold a short scoping call to confirm your Odoo version, storage destinations, encryption preferences, schedule and retention. We then build the module, deploy it to your instance, run a live backup-and-restore drill, and hand over documentation and training. Timeline depends mainly on how many storage targets you need and any bespoke requirements.

Every engagement includes a post-launch support window for bug fixes and configuration help. Because the module uses Odoo's core dump routines and standard APIs, it is version-resilient — but if you upgrade across Odoo majors (17 → 18 → 19) we can provide a compatibility update. We also offer ongoing support/maintenance retainers if you want us to monitor backups, add new storage targets, or adjust retention over time.

Both. A database-only dump is a common and dangerous mistake — you would lose every attachment, product image, invoice PDF and QWeb report asset stored in Odoo's filestore. This module captures the full PostgreSQL data and the entire filestore in each archive, so a restore rebuilds a complete, working instance rather than a database full of broken file links.

You choose one or more of: Google Drive, Dropbox, OneDrive, Nextcloud, Amazon S3 (or any S3-compatible bucket like Backblaze B2, Wasabi or MinIO), SFTP, or a remote server over SSH. Each archive is AES-encrypted at rest before it leaves your server, so the storage provider only ever holds ciphertext. Credentials and encryption keys live in dedicated models protected by ir.model.access.csv and record rules so only administrators can see them.

It works on Odoo 17, 18 and 19, Community and Enterprise. The backup runs as a scheduled ir.cron job that you can set for off-peak hours, and we tune compression and stagger multi-database runs to keep the impact minimal. On very large databases we use chunked/resumable uploads so a big transfer does not block Odoo's worker processes.

Three ways. First, every run writes to a backup log model with status, size, duration, destination and a SHA-256 checksum — a full audit trail in the Odoo UI. Second, the archive checksum is verified after upload, so a truncated or corrupted transfer is flagged. Third, any failure triggers an immediate email and/or Slack alert. During handover we deliberately fail a test run with you to prove the alerts reach your team.

Yes. Restoration uses Odoo's standard restore path plus filestore reinstatement, and the module includes a test-restore action so you can validate a specific archive against a scratch database without touching production. Your deliverables include a step-by-step restore runbook, and as part of delivery we perform a real restore drill together so you have seen it work before you ever need it in an emergency.