github junkerderprovinz/bombvault v7.9.0

latest releases: v10.6.0, v10.5.5, v10.5.3...
3 months ago

BombVault 7.9.0 makes off-site setup less scary and more accurate: a freshly reachable destination no longer shows a fatal error, the setup wizard only shows the controls that apply to your actual backend, and retention values are explained in place instead of left to guesswork. It also fixes a stale lock that could block file listing, hidden off-site credentials in Simple mode, a generic connection-test failure message, and a mismatched documentation button on the README.

⚡ Improved

  • The flash export drops the previous OS version's boot files. After an Unraid upgrade, /boot/previous/ keeps the prior version's kernel around as a rollback safety net, on a real boot drive this can be a third or more of the whole export by itself. It's not part of what a flash export restores (OS, license, array config, shares, network, and plugins are all elsewhere), and Unraid rebuilds it fresh on the next real upgrade regardless, so it's now excluded, shrinking a typical export noticeably and leaving more headroom on smaller USB sticks.

🐛 Fixed

  • A fresh remote off-site destination no longer shows a fatal error. A reachable destination that simply hasn't been replicated to yet showed restic's raw "repository does not exist" as a red fatal error in the setup wizard and Settings. It now reports the same "reachable, not initialised" warning state the UI already had translated in all 26 languages, but never triggered. (#130)

  • The off-site setup wizard no longer shows REST-only controls for rclone or s3 destinations. REST username/password fields, the append-only tamper-test button, the "maintenance window" retention option, and the far-side prune cron example were all shown regardless of the selected backend. All four are now gated on the actual configured backend, and the cron example uses your real repo URL for non-REST backends instead of a fabricated local path. (#131)

  • Retention values (Keep last/daily/weekly/monthly) are explained in place. Neither the local nor the off-site retention card said what each field does, that the four rules combine with OR rather than adding up, that they apply per backed-up item, or that an immutable off-site destination is never pruned from here. Both cards now carry inline (i) info bubbles explaining all of it. (#132)

  • "Select files" no longer fails with a generic "Failed to load files". A stale exclusive lock left behind by an earlier interrupted operation blocked the file-listing call the same way it could block a backup, but the file-listing path never got the self-heal the backups list already had. It now self-heals the same way, and clears the stale lock automatically instead of failing. (#129)

  • File-listing errors now show the real reason, matching how the rest of the app already handles errors, instead of a generic message even when the server already sent back the specific cause.

  • Off-site rclone and cloud credentials are visible again in Simple mode. The credential cards on Settings' Off-site tab were wrongly hidden behind Advanced mode, while the repo-path field right next to them has always been visible by default.

  • Off-site "Test connection" now shows the real reason it failed instead of a generic "not reachable" no matter the actual cause (a bad rclone remote type, wrong credentials, an unreachable host).

  • The documentation button on the README now matches the "Buy me a coffee" button's size and colour.

  • Flash zip downloads now extract cleanly in the official Unraid USB Creator. restic's own zip writer stores every entry uncompressed, which the USB Creator's unzip implementation cannot reliably extract past a certain point (verified against a real device down to the byte level). The download is now recompressed on the way out, and a handful of non-Unraid artifacts that have no business in a boot-drive restore (a stray .git checkout, Windows' System Volume Information, fsck recovery dumps, 0-byte .bmp remnants) are dropped along the way. (#136)

  • The dashboard's "replicating" activity line no longer disappears during a long off-site upload. restic copy has no incremental progress output, so a replication slower than 15 seconds looked like it had silently vanished from the dashboard, even though it was still running correctly in the background. It now sends a periodic heartbeat so the line stays visible for the whole upload. (#134)

  • Restarting BombVault mid-backup could corrupt a restic repository. Cancelling an in-flight restic process (for example, an update triggered while a backup batch was still uploading) sent SIGKILL, which restic cannot catch or clean up after; a later automatic prune could then remove data a snapshot's tree still referenced, leaving the repository unable to read that snapshot. Cancellation now sends SIGTERM instead, which restic handles as a clean abort with no partial snapshot left behind.

  • A flash zip download looked like it had stopped after switching tabs. The download's progress lived in the page's own state, which React discards when you navigate away and back, even though the download itself kept running (or had already finished) in the background. Flash downloads now go through the browser's own download manager instead, so they show up correctly no matter what you do in the app while they run.

Upgrading

Just pull the new image.

Don't miss a new bombvault release

NewReleases is sending notifications on new releases.