Skip to content

Improve docker restore manual #866

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 1 commit into from
Jun 30, 2026
Merged

Improve docker restore manual #866

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 11 additions & 2 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 @@ -48,7 +48,16 @@ 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.
#. 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.

#. After the restore process has finished, the ``restore`` directory got renamed.
You can safely delete it now.
Loading