Skip to content

Add support for restore mode#491

Merged
mgruner merged 8 commits into
zammad-70from
restore-mode
Feb 16, 2026
Merged

Add support for restore mode#491
mgruner merged 8 commits into
zammad-70from
restore-mode

Conversation

@mgruner

@mgruner mgruner commented Jun 5, 2025

Copy link
Copy Markdown
Collaborator

Zammad 7.0 will feature restoring backups in docker. This happens inside the zammad-backup container, which therefore needs to mount the zammad-storage volume in rw mode rather than ro so that files can actually be restored.

Breaking Change

This change of the mount point must be transferred to any local docker-compose.yml definitions that are already deployed and need to be updated.

@mgruner mgruner added the feature label Jun 5, 2025
@waja

waja commented Jun 5, 2025

Copy link
Copy Markdown
Contributor

Is this something that can be done via GUI or is there CLI work needed? If there is operational work required, the write mount can be overridden when a restore is needed. This is a bit more safety but a bit more uncomfortable.

@mgruner

mgruner commented Jun 5, 2025

Copy link
Copy Markdown
Collaborator Author

The admin needs to provide the restorable backups in the restore folder in the zammad-backup volume. This can be done via CLI, but also via Portainer for example by running docker images like filebrowser which provide a browser based UI for managing the volume content.
More changes incoming.

@mgruner

mgruner commented Jun 5, 2025

Copy link
Copy Markdown
Collaborator Author

Is this something that can be done via GUI or is there CLI work needed? If there is operational work required, the write mount can be overridden when a restore is needed. This is a bit more safety but a bit more uncomfortable.

This is right, but it would not work with scenarios like Portainer based deployments, as it requires modification of the yaml file.

@mgruner mgruner mentioned this pull request Jun 27, 2025
@github-actions

github-actions Bot commented Aug 5, 2025

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has not had recent activity.
It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions Bot added the stale label Aug 5, 2025
@mgruner mgruner added pinned Don't stale issues and removed stale labels Aug 5, 2025
Comment thread .github/workflows/ci.yaml
Comment on lines +64 to +65
env:
VERSION: 'develop' # TODO: revert before merging!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: revert before merging

@mgruner
mgruner changed the base branch from master to zammad-70 February 16, 2026 07:54
@mgruner
mgruner marked this pull request as ready for review February 16, 2026 08:12
@mgruner
mgruner merged commit 11fb608 into zammad-70 Feb 16, 2026
13 checks passed
mgruner added a commit that referenced this pull request Mar 4, 2026
* Switch to Zammad 7.0
* Add support for Redis Sentinel variables (#510)
* Add support for restore mode (#491)
  * Zammad 7.0 features restoring backups in docker. This happens inside the zammad-backup container, which therefore needs to mount the zammad-storage volume in rw mode rather than ro so that files can actually be restored.
  * Breaking Change: This change of the mount point must be transferred to any local docker-compose.yml definitions that are already deployed and need to be updated.
* Update to Elasticsearch 9 and Redis 8 (#531)
* Automatically configure trusted RAILS_TRUSTED_PROXIES for proxy scenarios (#532)
@mgruner
mgruner deleted the restore-mode branch March 4, 2026 12:42
Olli pushed a commit to Olli/zammad-docker-compose that referenced this pull request Mar 11, 2026
* Switch to Zammad 7.0
* Add support for Redis Sentinel variables (zammad#510)
* Add support for restore mode (zammad#491)
  * Zammad 7.0 features restoring backups in docker. This happens inside the zammad-backup container, which therefore needs to mount the zammad-storage volume in rw mode rather than ro so that files can actually be restored.
  * Breaking Change: This change of the mount point must be transferred to any local docker-compose.yml definitions that are already deployed and need to be updated.
* Update to Elasticsearch 9 and Redis 8 (zammad#531)
* Automatically configure trusted RAILS_TRUSTED_PROXIES for proxy scenarios (zammad#532)
mleem97 pushed a commit to mleem97/zammad-docker-compose that referenced this pull request Mar 30, 2026
* Switch to Zammad 7.0
* Add support for Redis Sentinel variables (zammad#510)
* Add support for restore mode (zammad#491)
  * Zammad 7.0 features restoring backups in docker. This happens inside the zammad-backup container, which therefore needs to mount the zammad-storage volume in rw mode rather than ro so that files can actually be restored.
  * Breaking Change: This change of the mount point must be transferred to any local docker-compose.yml definitions that are already deployed and need to be updated.
* Update to Elasticsearch 9 and Redis 8 (zammad#531)
* Automatically configure trusted RAILS_TRUSTED_PROXIES for proxy scenarios (zammad#532)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature pinned Don't stale issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants