Backup & Restore
Cette page est dédier à la sauvegarde et restoration des services sur le serveur.
Services
As of 25/08/08 → 20 GiB approximatly. It should not grow very fast, since it is mostly configuration files and a text wiki.
Media is backed up seperatly where necessary:
- jellyfin
- navidrome
Otterwiki
OtterWiki being a flatfile wiki, we can back it up by simply copying the
/mnt/data/otterwiki folder.
Forgejo
Backup
Based on the documentation and this analysis of gitea backups, we can run
docker compose exec -u git forgejo forgejo dump --file /tmp/forgejo-dump.zip
Then copy out the file and rename it at the same time:
docker compose cp forgejo:/tmp/forgejo-dump.zip /mnt/data/backups/forgejo/forgejo-backup-$(date +%Y%m%d-%H%M%S).zip
Pour finir, on supprime l'archive du dossier /tmp dans le container:
docker compose exec forgejo rm /tmp/forgejo-dump.zip
Restore
Move all relevant files to their location in the mounted volumes.
Jellyfin
Backup and Restore → jellyfin.org
Stop the container completly, then copy the config folder (maybe nothing else ?)
→ /mnt/data/jellyfin/config
Kavita
Backups → wiki.kavitareader.com
Backups are already generated, in /mnt/data/kavita/config/backups.
Navidrome
Automated Backup → navidrome.org
Backup can be automated via config file or env variables. Location is
/mnt/data/navidrome/backup.
Miniflux
postgresql dump restore → postgresql.org
Miniflux stores all it's data in the postgresql db. We can dump it:
sudo bash -c "docker compose exec db pg_dump -U miniflux miniflux" > miniflux_backup.sql
And use the file to restore it later.
Readeck
docker exec -i readeck sh -c 'readeck export "/readeck/readeck_backup_$(date +%Y%m%dT%H%M%S).zip"'
to import, do the same and specifying the config file.
Needs to be recuring via cron job or script. Could also be built by script that does the overall backup, since backup is quick.
Caddy
It is sufficient to backup the /mnt/data/caddy. The most important folders
inside are:
./Caddyfile./html/
To restore, the both should be in the same folder, for the Caddyfile contains the paths to the different root folders for the websites hosted.
OpenWebUI
We do not backup the ollama models. We only handle the openwebui data.
Dir structure:
├── audit.log ├── cache/ ├── uploads/ ├── vector_db/ └── webui.db
- Cold backup approach - Stops the container before backup for data integrity
- Copies the entire
/webuifolder including:- webui.db (main database with chats, users, settings)
- uploads/ (uploaded files)
- cache/ (cached data)
- vector_db/ (RAG/Knowledge embeddings)
Missing or broken installs
- archivebox
- bookstack
- etherpad
- synapse