Skip to content

Add support for restore mode #491

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.

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

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

Add support for restore mode #491

wants to merge 6 commits into from

Conversation

mgruner
Copy link
Collaborator

@mgruner mgruner commented Jun 5, 2025

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
Copy link
Contributor

waja commented Jun 5, 2025

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
Copy link
Collaborator Author

mgruner commented Jun 5, 2025

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
Copy link
Collaborator Author

mgruner commented Jun 5, 2025

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.

Copy link

github-actions bot commented Aug 5, 2025

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