Skip to content

Fixes #872 - Add ES reindexing to Docker restore process #874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralf401 merged 2 commits into from
Jul 22, 2026
Merged

Fixes #872 - Add ES reindexing to Docker restore process #874

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41e8bd5
Add ES reindexing for Docker restore process
ralf401 Jul 22, 2026
8a46582
Fixed command; added link to install instructions
ralf401 Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 14 additions & 10 deletions appendix/backup-and-restore/docker-compose.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,15 +49,19 @@ Restore
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 in the ``zammad-backup``
service if the ``restore`` directory is detected and the backup files are in place.

.. 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.

service if the ``restore`` directory is detected and the backup files are in
place. As a part of this process, the Rails cache will be cleared. All other
containers wait for the restore to finish before they resume their normal
operations.
#. After the restore process has finished, the ``restore`` directory got renamed.
You can safely delete it now.
#. Rebuild the Elasticsearch index. You can use Zammad while the rebuild is
running, but search performance is degraded and some data may be temporarily
unavailable in search results. Use the command below for Docker Compose
deployments. When using GUIs like portainer, have a look at the
:ref:`docker-run-commands` section in
the installation documentation.

.. include:: /install/update.rst
:start-after: **Docker Compose:**
:end-before: **Portainer:**
1 change: 0 additions & 1 deletion install/elasticsearch/connect-configure-elasticsearch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,6 @@ Build/rebuild the searchindex

$ zammad run rake zammad:searchindex:rebuild[8]


Optional settings
-----------------

Expand Down
3 changes: 3 additions & 0 deletions install/update.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,9 @@ using `Zammad hosting`_ for your and your customers' safety.
Only needed if the release note tells you to rebuild the Elasticsearch
index.

.. Rebuild commands used in appendix/backup-and-restore/docker-compose-rst
.. When changing, make sure to adjust the reference there as well

**Docker Compose:**

Without specifying CPU cores:
Expand Down
Loading