Hi,

You are trying to create a clean backup and restore workflow for Odoo 18 running in Docker, where both the database and the filestore need to be cloned in sync. The main challenge is that your attempts with pg_dump/pg_restore and rsync end up with permission mismatches, authentication errors, or Odoo failing to connect properly, even when the containers appear healthy.

The recommended approach is to handle three parts carefully: the PostgreSQL database, the Odoo filestore, and the configuration. The database can be backed up using pg_dump and restored into a new staging database with pg_restore. The filestore should be copied using rsync or docker cp, making sure permissions match the Odoo container’s user (odoo:odoo or UID 1000). The Odoo config also needs to be duplicated and updated so that the staging database is recognized, with db_name or dbfilter adjusted as needed.

To prevent conflicts, staging should never connect to production services like email or payments, and the db_uuid in the ir_config_parameter table should be updated so that the staging DB has a unique identifier. The best practice is to script the workflow, database dump, filestore copy, restore, permission fix, and config update, and ensure consistency by either stopping Odoo during backup or using --single-transaction with pg_dump. With this setup, you’ll have a reproducible, stable staging copy of your production Odoo instance inside Docker.

Hope it helps

Thanks for the warm welcome! 

Got it - my sincere apologies if i did anything bad with reaching out here in the forum, that was not my intention! 

Please delete my post - my Karma does not allow me. 

Best regards, Angel