From d15ef4c9334f2faa43e0a12edc65027008783d1d Mon Sep 17 00:00:00 2001 From: Martin Gruner Date: Thu, 25 Jun 2026 12:08:28 +0000 Subject: [PATCH 1/3] Improve docker restore manual --- appendix/backup-and-restore/docker-compose.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/appendix/backup-and-restore/docker-compose.rst b/appendix/backup-and-restore/docker-compose.rst index 4bc35cc9..605fa8a4 100644 --- a/appendix/backup-and-restore/docker-compose.rst +++ b/appendix/backup-and-restore/docker-compose.rst @@ -52,3 +52,12 @@ Restore directory is detected and the backup files are in place. #. After the restore process has finished, the ``restore`` directory got renamed. You can safely delete it now. + +.. hint:: + + If you restored into a stack that had data before, you need to perform final clean-ups. + + #. You need to clear the cache of Zammad by running ``Rails.cache.clear``. + #. The Elasticsearch index is out of date now, and you should + :ref:`trigger a rebuild ` to synchronize it with + the restored state of Zammad. From b9e692a024e691a322c88e48e5a3e95e8b56224b Mon Sep 17 00:00:00 2001 From: Martin Gruner Date: Tue, 30 Jun 2026 12:11:00 +0000 Subject: [PATCH 2/3] Update message --- .../backup-and-restore/docker-compose.rst | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/appendix/backup-and-restore/docker-compose.rst b/appendix/backup-and-restore/docker-compose.rst index 605fa8a4..77498b60 100644 --- a/appendix/backup-and-restore/docker-compose.rst +++ b/appendix/backup-and-restore/docker-compose.rst @@ -48,16 +48,17 @@ Restore Only backups from package and Docker installations are supported by this built-in backup method. Don't provide the ``latest_zammad_*.gz`` files because they link to an unknown location for the restore process. -#. Start the stack. The restore process is triggered if the ``restore`` - directory is detected and the backup files are in place. -#. After the restore process has finished, the ``restore`` directory got renamed. - You can safely delete it now. +#. Start the stack. The restore process is triggered in the ``zammad-backup`` + service if the ``restore`` directory is detected and the backup files are in place. -.. hint:: + .. hint:: + As a part of this process, the cache will be cleared and any pre-existing + Elasticsearch indexes will be dropped. + All other containers will be waiting for the restore to finish. When that is the case, + they will resume their normal operations, which includes an automatic Elasticsearch + reindexing (depending on the ENV variables). You can check the container logs for + details. - If you restored into a stack that had data before, you need to perform final clean-ups. +#. After the restore process has finished, the ``restore`` directory got renamed. + You can safely delete it now. - #. You need to clear the cache of Zammad by running ``Rails.cache.clear``. - #. The Elasticsearch index is out of date now, and you should - :ref:`trigger a rebuild ` to synchronize it with - the restored state of Zammad. From b7687a48c528a18fa3f72026dad22ec55bed5436 Mon Sep 17 00:00:00 2001 From: Martin Gruner Date: Tue, 30 Jun 2026 12:12:38 +0000 Subject: [PATCH 3/3] Remove trailing line --- appendix/backup-and-restore/docker-compose.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/appendix/backup-and-restore/docker-compose.rst b/appendix/backup-and-restore/docker-compose.rst index 77498b60..a7fb9d39 100644 --- a/appendix/backup-and-restore/docker-compose.rst +++ b/appendix/backup-and-restore/docker-compose.rst @@ -61,4 +61,3 @@ Restore #. After the restore process has finished, the ``restore`` directory got renamed. You can safely delete it now. -