Backups and restore

Stackarr backs up its settings, presets, hooks, service configuration, and durable database state. The default schedule is weekly on Sunday at 02:00 and keeps 52 archives.

Choose the backup folder during setup. For an external disk or network share, make sure Docker can write to that folder and run System → Status → Audit permissions.

Run a backup now

Use the dashboard, ask your agent, or run:

docker exec app /app/bin/stackarr backup run

If a required database cannot be read, Stackarr fails the backup instead of creating an incomplete archive.

Lite or full

lite is recommended. It keeps restore-critical databases, settings, and custom artwork while skipping caches, logs, generated metadata, and other rebuildable files.

Choose full when you intentionally want cache-heavy service data and have enough backup storage.

Restore

Keep the stack quiet during a restore. Start from Setup → Restore, ask an admin-profile agent to prepare a dry-run, or use an archive already visible inside the container's backup folder:

docker exec app /app/bin/stackarr backup restore /path/inside/container/stackarr-backup.tar.gz

Review the folders, databases, and services that will be replaced before approving the restore. Stackarr accepts .tar.gz, .tgz, and .zip archives.