Skip to content
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

Document how to back up a synapse server #2046

Closed
matrixbot opened this issue Dec 16, 2023 · 1 comment · Fixed by #17931
Closed

Document how to back up a synapse server #2046

matrixbot opened this issue Dec 16, 2023 · 1 comment · Fixed by #17931

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 16, 2023

This issue has been migrated from #2046.


We should give users some guidance on what they need to do to effectively back up and restore a synapse.

Off the top of my head:

  • database
  • media repo
  • homeserver.yaml
  • log config, where present
  • signing key (maybe, but it's fine just to use a new one)
@matrixbot matrixbot changed the title Dummy issue Document how to back up a synapse server Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
@LaXiS96
Copy link

LaXiS96 commented Mar 16, 2024

It looks like all that really needs to be backed up (apart from database, configuration and keys) is the local_content media folder.
It could be the case that on restoring, remote media may not be redownloaded by synapse, in that case it should be possible to use the Media Admin API to purge all remote references from the database (see https://element-hq.github.io/synapse/latest/admin_api/media_admin_api.html#purge-remote-media-api).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants