Bỏ qua để đến Nội dung
Menu
Câu hỏi này đã bị gắn cờ
2 Trả lời
331 Lượt xem

please delete - Thank you.

Ảnh đại diện
Huỷ bỏ

"Odoo 18.0 CE" is not a question. A question is a substantial phrase that ends with "?"

We get close to 1,000 posts a month and not everyone will open a post to find out what your question is.

I have edited your post to make the title a question.

In the future, please consider (1) using a Question that makes it clear what you ask without requiring people to open your post and (2) adding Tags. This will often increase the chances people will respond and also make everything clearer for others who may come along later searching for the same thing.

Failing that, you can paste your future posts into an AI Chatbot and ask it to "please generate a question of no more than 16 words that summarizes what I am asking" and use that as your question.

See also https://www.odoo.com/forum/help-1/meta-why-do-some-questions-get-answers-and-others-do-not-25620

Câu trả lời hay nhất

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

Ảnh đại diện
Huỷ bỏ
Tác giả Câu trả lời hay nhất

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

Ảnh đại diện
Huỷ bỏ
Bài viết liên quan Trả lời Lượt xem Hoạt động
0
thg 8 25
1015
1
thg 3 25
1387
1
thg 12 24
19
1
thg 4 25
1918
0
thg 2 25
1496