Backups
What to keep so you can recover KumoYami, and how to restore it.
KumoYami's image can be downloaded again at any time. What's yours, and what you need to keep, lives in the install folder:
| What | Holds |
|---|---|
datos/ | The panel's storage and its credentials, OneDrive tokens, appearance, share links, the activated license… |
.env | Your variables: ADMIN_PASSWORD, KUMOYAMI_PORT, tokens… |
docker-compose.yml | With your volumes and services. |
docker-compose.override.yml, Caddyfile | If present: the installer's Caddy, your proxy or your own changes. |
The local folders you publish (your photos, documents…) aren't in here: they're yours, and belong in your own backup.
Making the backup
In the install folder:
cd /opt/kumoyami
sudo tar czf ~/kumoyami-backup-$(date +%F).tgz .env docker-compose.yml datos/ \
$(ls docker-compose.override.yml Caddyfile 2>/dev/null)For a fully consistent copy, stop the site for a few seconds first (docker compose stop web) and start it again
afterwards (docker compose start web).
Keep the file somewhere other than the server: your computer (scp), another server or external storage. .env and
datos/ hold passwords and tokens, so treat the backup as private.
If you lose datos/ without a backup, you'll have to add your storage again and reconnect OneDrive.
The panel's own backup
The admin panel also has its own backup of the configuration. It's handy for keeping your settings, but it's no
substitute for backing up datos/ and .env.
Restoring
On a server with Docker and the docker login session in place:
sudo mkdir -p /opt/kumoyami && cd /opt/kumoyami
sudo tar xzf ~/kumoyami-backup-2026-11-01.tgz
sudo chown -R 1000:1000 datos
sudo docker compose up -dIf you're restoring on another server, also follow Moving to another server for the license.