Repository navigation
Releases
Arkive 0.7.0
Arkive 0.7.0 makes long backups workable and visible: the time limit per storage target is now a setting, and a running backup shows how far it is. It also brings restic 0.20.0 (which fixes a security problem in restore) and rclone 1.76.0, and fixes two problems found on real servers. The time limit and the progress display were contributed by @Roalkege.
Upgrade by recreating the container with the same /config volume. This release has one database migration (9, a column for the new per-target numbers); it runs by itself on the first start. Upgrading was tested from 0.2.4, 0.5.0 and 0.6.0.
- The time limit stays at 60 minutes per target and attempt unless you change it under Settings → General. Raise it if a large first backup was being stopped after an hour. With 0 there is no limit: an upload that stalls then holds the backup lock until you cancel the run.
- Per-target numbers (data stored, new, changed and unchanged files) are recorded from this release on; runs made before the upgrade show none.
- If your server starts and removes containers often (CI jobs, scheduled containers, image builds), upgrade soon: on 0.6.0 and earlier a backup that starts at such a moment can end
partialwithout dumping any database.
Added
- Backup progress shows source data processed, file counts, average processing speed and estimated time remaining for the current target. Run details keep each target's newly stored data size and counts of new, changed and unchanged files (migration 9; unavailable for older runs).
- Settings → General includes a backup timeout in minutes per target and attempt. The default remains 60 minutes; 0 disables the runtime limit while keeping manual cancellation available. Timeout errors explain where to change the limit.
Changed
- rclone 1.76.0 (was 1.75.2). It already includes the
golang.org/x/netfix that 0.5.0 had to add by rebuilding 1.75.2. - Dependency updates. Backend: FastAPI 0.163.1, sse-starlette 3.7.0, Apprise 2.2.0, pydantic-settings 2.16.3,
croniter 7.0.0, structlog 26.1.0, python-dateutil 4.0.0 (used only through croniter); development tools
pytest-asyncio 1.5.0, ruff 0.17.5, mypy 2.4.1. Frontend: SvelteKit 3.2.0, Vite 8.3.8, lucide-svelte 1.0.1,
jsdom 31.0.1, Playwright 1.65.1, @types/node 26.6.6. lucide 1.0 dropped brand icons, so the footer's GitHub
mark is now an inline icon. TypeScript stays on 6: SvelteKit 3 does not accept TypeScript 7 yet.
Security
- restic 0.20.0 (was 0.19.1). It fixes a problem in
restic restorewhere a crafted snapshot could make a restore
write through a symbolic link to files outside the restore folder; restic now refuses such a snapshot. Someone
would need write access to the backup repository to plant one. It also carries restic's other fixes since 0.19.1
(truncated key or config files no longer make a repository unreadable, hard-linked files restore correctly over
existing ones) and already includes the dependency updates Arkive used to add when building 0.19.1.
Fixed
- The sidebar's active link updates when navigating between pages, including nested routes and browser back navigation.
- A new install no longer reports
degradedfor its first minutes. A storage target that had not had its first
health check yet was counted as unhealthy, so the dashboard and/api/statussaiddegradedright after setup
(and after adding a target) even when the first backup had already succeeded. - A container that is removed while Arkive is listing containers no longer fails the whole scan. On a server that
starts and removes short-lived containers (CI jobs, scheduled containers, image builds), a backup run could end
partialwith "container discovery failed, databases were not dumped"; the vanished container is now skipped.
Full changelog: v0.6.0...v0.7.0
Arkive 0.6.0
Arkive 0.6.0 closes the gaps 0.5.0 listed as known limitations: MariaDB and MySQL users and grants are now part of the backup, and guided restore covers MongoDB and Redis as well as PostgreSQL, MariaDB/MySQL and SQLite.
Upgrade by recreating the container with the same /config volume. There are no database migrations in this release.
- Each MariaDB/MySQL container gets one more file per backup, the accounts dump. If Arkive connects as root and that dump fails, the run becomes
partialand the message says why. A container without a root password in its environment is recorded as skipped, not as a problem. - Guided restore of a MongoDB database replaces it in place. For a MongoDB server that Arkive dumps whole (listed as
admin), it replaces every database exceptadmin,configandlocal. A safety dump is taken first and Undo loads it back. - Restore plans generated by earlier versions have Redis steps that leave Redis empty when the append-only file is on. Download the plan again after upgrading.
Added
- MariaDB and MySQL users and grants are backed up. Each MariaDB/MySQL container gets an accounts dump next to its database dumps (
<container>_accounts-<hash>_<timestamp>.sql) that recreates the application users and roles with their passwords, and gives back their grants and default roles. On a new server, load it after that server's databases; the restore plan lists the step.rootand the server's own accounts are left out, so the new container keeps its own root password. This needs the root password in the container's environment (MYSQL_ROOT_PASSWORDorMARIADB_ROOT_PASSWORD); without it the accounts dump is recorded as skipped. This closes the 0.5.0 known limitation that the application's database user had to be recreated by hand. - Guided restore for MongoDB and Redis. MongoDB is restored in place like PostgreSQL and MariaDB: Arkive checks every collection's checksum in the archive first, takes a safety dump, drops the database (or, for a server dumped whole, every database except
admin,configandlocal) and loads the archive withmongorestore; Undo puts the safety dump back the same way. The MongoDB password never appears on a command line. Redis is prepared like SQLite: Arkive restores the.rdbfile, checks its checksum and that the running Redis can read it, saves the current data and gives you the exact steps to swap it in, including a new append-only file whenappendonlyis on (moving the old one aside alone makes Redis start empty).
Changed
- Backups give
mongodumpthe MongoDB password on its input (--config=/dev/stdin) instead of on the command line, so it no longer shows in process listings. Images with the legacy tools of MongoDB 4.2 and older have no--config; there the password still goes on the command line, and the log says so. - Backend dependencies updated: sse-starlette 3.6 (live event and log streams), FastAPI 0.162, uvicorn 0.54, pydantic 2.14, docker 7.2, python-multipart 0.0.33 and click 8.5.1; test and lint tooling moves to pytest 9.2, ruff 0.17.4 and bandit 1.9.4.
Fixed
- The restore plan's Redis steps copied the dump to a guessed folder while Redis ran, and with the append-only file on Redis would have started empty. They now stop the container, find the data folder, file name and append-only settings (from Redis while it runs, otherwise the image's defaults, its command line and the files in the folder), copy the dump in, rebuild the append-only file from it when it is on and start Redis again.
- The manual MongoDB and Redis restore steps in the restore guide: a
.archive.gzdump is decompressed withgunzip -c(notmongorestore --gzip), and Redis with the append-only file needs a new one made from the dump.
Full changelog: v0.5.0...v0.6.0
Arkive 0.5.0
Arkive 0.5.0 answers the questions that come after "do my backups work?": is there a copy somewhere else, is each database healthy, what is still missing after setup, and how do I get one database back without doing it by hand. It is also the first release prepared for Unraid Community Applications.
Upgrade by recreating the container with the same /config volume; database migrations run on start.
- If every storage target your jobs upload to is on the server itself, the dashboard now says there is no offsite copy. It is a warning only: it does not change the system status or the heartbeat. Notification channels that already get backup failures also get the new "No offsite copy" event.
- A database whose dump suddenly shrinks to half its usual size or less now makes that run
partialuntil the size comes back or you accept the new size on the Databases page. - PostgreSQL dumps now carry owners and grants. Restore the roles dump (
globals) before a database dump, as the restore plan describes. - The Unraid template and the example Compose file follow release tags (
islamdiaa/arkive:0andlatest), no longer every build ofmain.
Added
- Offsite warning (3-2-1). Arkive works out where each job's backups actually go and warns when no copy leaves the server: a local folder, or an SFTP or S3 endpoint that turns out to be this machine or one of its containers. Event:
backup.no_offsite. - Per-database health. The Databases page shows, for every database, when it was last dumped successfully, how large the dump was and whether anything is wrong, instead of one overall count.
- Dump-shrink warning. A dump at least 50% smaller than that database's recent dumps is flagged and the run becomes
partial. The thresholds are under Settings → Monitoring. - Guided database restore (Restore a database, on the Restore page). Pick a database and a snapshot; Arkive checks the dump, takes a safety dump of the current database, can stop the apps that use it, loads the dump and starts them again. A restore can be undone from the safety dump. PostgreSQL, MariaDB and MySQL are restored in place. SQLite files are restored, integrity-checked and left for you to swap in, with the exact steps, because Arkive does not write to your app data.
- "Finish protecting this server" checklist on the dashboard after setup: a clean first backup, a passed restore test, an offsite target, a notification channel and a saved recovery kit. Each step is judged from what actually happened, not from a checkbox.
- Unraid Community Applications template, with read-only data mounts by default.
- User guide in
docs/: quick start, storage providers, restore, restore drills, monitoring, notifications, recovery kit, security, upgrading and troubleshooting. - Keyboard and screen-reader support across the interface: a skip link, labelled controls and dialogs, visible focus, readable contrast in both themes, and layouts that work on a phone.
- A footer with the running version and links to the source.
- An automated upgrade test from 0.2.4 to the current version, and a restore round trip against real PostgreSQL, MariaDB, MySQL and SQLite, for people working on Arkive.
Changed
- Database dumps restore completely. PostgreSQL dumps keep owners and grants. MariaDB and MySQL dumps include stored procedures, functions and events, and every application database on the server is dumped, not only
MYSQL_DATABASE. MariaDB 11 images, which shipmariadb-dumpinstead ofmysqldump, are supported. - The
islamdiaa/arkive:latestimage now moves only when a new version is released. Until now every push tomainrepublishedlatest, so the Unraid template and the example Compose file could pull unreleased code. Builds ofmainare still published asmainand as the commit SHA. - GitHub releases are created from this changelog when a version is tagged.
- A local storage target on a read-only mount is rejected when you add it, instead of failing at the first backup.
- The frontend moved to SvelteKit 3 and Tailwind CSS 4. Nothing should look or behave differently.
- Dependency updates: apprise 2.1.0, click 8.5.0, and the Inter and JetBrains Mono fonts.
- restic 0.19.1 and rclone 1.75.2 are rebuilt with
golang.org/x/net0.62.0, which fixes CVE-2026-78661.
Fixed
- Restore-plan commands now run as written: they use the container's own database user and client, no longer rely on bash-only syntax, and handle SQLite write-ahead logs.
- Restore drills no longer fail on a
CREATE TABLEinside a function body or on a MySQL system-schema dump. - Log redaction no longer mangles container names such as
immich-postgres.
Known limitations
- MariaDB and MySQL user accounts and grants are not part of the dumps yet. After restoring onto a fresh server, re-create the application's database user.
- Guided restore does not cover MongoDB or Redis; restore those dumps by hand as described in the user guide.
Full changelog: v0.4.0...v0.5.0
Arkive 0.4.0
Arkive 0.4.0 is about one question: do my backups actually work? It follows a production audit that found v0.2.4 reporting success for months while backing up no databases at all, and it adds checks that don't rely on a backup run reporting its own failure.
docker pull islamdiaa/arkive:0.4.0Upgrade by recreating the container with the same /config volume; database migrations run on start. See Upgrading from 0.2.x below.
Highlights
Knowing it works
- Overdue-backup watchdog. A job whose last good backup is older than its schedule window turns the dashboard red and sends
backup.stalealerts. - Heartbeat. Point Arkive at an Uptime Kuma push monitor or healthchecks.io. It pings only while every job is healthy, so you also hear about it when Arkive itself is down.
- Weekly restore drills. Recent database dumps are restored from the latest snapshot and loaded into a throwaway, network-isolated container of the same database image.
- No silent successes. A run that misses anything (a database, a path, a target, unreadable files, failed discovery) is
partial, with the reason.
Backups
- Every database in a PostgreSQL cluster is dumped, plus roles (
pg_dumpall --globals-only). - Dumps are stored uncompressed by default, so restic deduplicates them: a large database adds only its changes to each snapshot.
- SQLite copies from read-only mounts no longer drop data still in the write-ahead log.
- Exclude a database from backups on the Databases page (for example an app cache that holds an exclusive lock).
- Truncated dumps are detected and never replace the last good one; dump files publish atomically.
Recovery
- Recovery kit: a one-time export of the encryption password, every repository location and the restore steps. The dashboard reminds you until you confirm you've saved it.
- Keyfile guard: Arkive refuses to start if
/config/.keyfileis missing or doesn't match the database, instead of silently creating a new key that would strand every stored secret. - Restores always land in
/config/restores, so the data you protect can be mounted read-only.
Fixes
- Weekday schedules (
* * 1-5,* * 0) ran a day late; the weekly restore drill never ran. - The Docker client now reconnects after a startup timeout. In v0.2.4, one timeout disabled database dumps until the container was restarted.
- Scheduled jobs that collide wait for each other instead of being skipped.
- The restic host name is stable (no more container IDs splitting retention groups); old snapshots are re-labelled during weekly retention.
- The light theme now works across the whole UI.
Security
- Command injection in the snapshot browser (fixed). An authenticated API caller could pass a path that restic read as an option (
--password-command). Because Arkive holds the Docker socket, this amounted to control of the host. User-supplied values are now passed after--and validated. - API open before setup (fixed). Until the setup wizard ran, every API route was reachable without credentials. Now only the scans the wizard needs are open, and setup can be completed only once, even under concurrent requests.
- Dependency updates for published advisories: cryptography 50.0.2, weasyprint 70.0, jinja2 3.1.6, python-multipart 0.0.32, apprise 1.13.1, pydantic-settings 2.16.2, zod 4.6.7.
- restic 0.19.1 and rclone 1.75.2 (rebuilt with a current Go toolchain), plus Debian security updates in the image.
- A security policy with private vulnerability reporting.
If you run v0.2.x on a network others can reach, upgrade.
Upgrading from 0.2.x
- Recreate the container with the same
/configvolume. Migrations run automatically. - Keep
/config/.keyfile. 0.4.0 refuses to start without the keyfile that encrypted your stored secrets. SetARKIVE_ALLOW_NEW_KEYFILE=1only if you intend to start over and re-enter them. - Mount data read-only (
/mnt/user/appdata:/mnt/user/appdata:ro,/boot/config:/boot-config:ro); Arkive no longer needs to write there. - After upgrading, save the recovery kit (Settings → Recovery kit) and add a notification channel.
Full changelog: v0.2.4...v0.4.0