Repository navigation
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