github junkerderprovinz/bombvault v2.9.0

latest releases: v10.6.3, v10.6.2, v10.6.1...
4 months ago

Per-source retention, plus a round of fixes. All of it came from @manilx's reports and requests. Thanks. 🙏

Added

  • Per-source retention (separate local & off-site policies). Retention used to be one policy for both repos. You can now set a separate keep-last / daily / weekly / monthly policy for the off-site repo, so you can keep off-site copies longer as an archive than the local ones. The off-site policy defaults to all-zero, which means no off-site pruning - existing off-site repos are never silently trimmed on upgrade, you opt in deliberately. Off-site pruning runs best-effort after each restic copy, so an off-site hiccup never fails a backup that already succeeded. (Settings → Retention, now split into Local and Off-site.) (requested by @manilx, #18)
  • Remove a stale VM entry. A VM that was deleted from the host but still shows under "Not installed" now has a Remove entry button (VMs tab) that clears the leftover entry. (A VM that still has backups is cleared with "Delete all backups" in its Backups panel instead.) (requested by @manilx)

Fixed

  • Retention / Prune now work after a container update. restic backups had no fixed host, so each snapshot took the container's hostname, which inside Docker is a random short container ID that changes every time the container is recreated (an update, a template edit, and so on). restic groups retention by host, so after any update the older snapshots landed in a separate group and were never pruned. The result: keep-policies (and the manual Prune button) appeared to do nothing, especially right after updating. Backups now pin a stable host and Prune groups by path, so a target's entire history is pruned together. Snapshots already piled up under old hostnames are cleaned up on the next prune. (reported by @manilx)
  • Off-site prune now uses the off-site policy. A manual Prune against the off-site repo previously applied the local retention policy. Each source now prunes with its own policy.
  • Maintenance "healthy" indicator no longer carries across repos. In Settings → Integrity & maintenance, switching the Local/Off-site source now clears the per-action result indicators, so a green result from one repo doesn't stay shown for the other where nothing has run. (reported by @manilx)

Note: the recurring daily dumpxml: failed to get domain error for a deleted VM was already fixed earlier in the 2.8.x line (the scheduler now skips a VM that's no longer defined on the host) - updating to this image and removing the stale entry clears it for good.

Thanks

  • @manilx for the detailed reports and feature requests behind this release. 🙏

Image: ghcr.io/junkerderprovinz/bombvault:2.9.0 (also :2, :2.9, :latest) and docker.io/junkerderprovinz/bombvault:2.9.0, multi-arch (amd64 + arm64).

Don't miss a new bombvault release

NewReleases is sending notifications on new releases.