github junkerderprovinz/bombvault v9.7.0

latest releases: v10.6.3, v10.6.2, v10.6.1...
one month ago

Each container, VM and folder set now chooses where it is backed up and which off-site targets get a copy, so a share that already lives on a NAS no longer has to go to B2 as well. Every item lists its backups as one timeline over all the places that hold them, and its card says how many sites have a current copy and whether 3-2-1 is met. Settings, schedules and repositories carry over as they are: until you choose otherwise, every item stays where it was and keeps going to every off-site target. BombVault also comes to Android, with an app that pairs with your group by QR code and shows what runs on all your servers. ParleyPort, your own relay, and the BombVault Widget get a page of their own under Settings, Apps.

✨ Added

Placement per item

  • A placement row on every card. Containers, VMs and folder sets choose between Local, Local + off-site and Off-site only. Local keeps the item out of every off-site copy. Local + off-site copies it to the targets ticked under Copy to, one chip per off-site target of the domain. Off-site only writes it straight to a direct repository beside a target, or to a remote repository of your own. The row is there in the simple view as well.
  • The location is fixed from the first backup on, the copies are not. BombVault never moves backups between repositories, so Stored on locks once an item has a backup. The ticks under Copy to can change at any time and move nothing.
  • What is really there. Under the row the card says where the item goes and what the targets hold: how many sites have a copy, when each target was last seen, and whether 3-2-1 is met. A target that has not been read for a while, or whose last run failed, is shown dimmed with its date and does not count. A site is the server itself, each off-site target and each repository marked Off the premises. BombVault checks copies and sites; it does not check the "two media" part of 3-2-1.
  • Older copies stay until you remove them. A target that no longer gets an item keeps the copies it has and trims them to its own retention at the next off-site run of the domain. Delete in B2 on the card removes them at once. When some of them exist nowhere else, the question lists them by date and asks for the item's name first. Append-only targets cannot be deleted from.
  • Off the premises. A named repository on Settings, Storage, Repositories can be marked as standing elsewhere. Remote repositories start marked, and a rest-server in the same building can be switched off. The mark only counts sites for the cards and changes no copy.

Android app

  • An app for your phone. bombvault-android.apk is attached to the release. It starts on a list of your servers with the activity log of all of them on top, the same lines the Dashboard shows, and opens the phone view of whichever you tap.
  • Pairing by QR code. Settings, Pairing, Show phrase shows the twelve words with a QR code beside them. Scan it with the app's own scanner, or paste or type the words. The app then lists the servers in that group before it saves anything, and one tap adds them all and joins the phone to the group like another instance. It reads what runs on each server through the group without a sign-in, also away from home over the relay.
  • Settings in the app. The gear beside the plus opens settings laid out like KnightLoader's. You pick the language and the name the phone shows on the Instances page. The look follows the first server in the list until you set your own, and animations have a setting of their own. There is a report to copy when you report a problem, the About card, and one button that removes every server and leaves the group.
  • No password on a paired phone. A phone paired with your group opens each of its servers already signed in: before it loads a page, it asks that server over the group for a session. A server added by its address still asks for the password, as in a browser. The session goes only to a member that is a phone. Anyone with the twelve words could already open every backup of the group, so pairing grants nothing new.
  • A touch screen answers every press. Nothing hovers under a finger, so a control dims while it is held, and a README button lights in its brand colour until the finger lifts. A long press on a button counts as a slow tap and opens no link menu.
  • The phone on the Instances page. The app has its own card marked Android app, under the name you gave the phone. It has no scorecard because it backs nothing up, and Remove takes it off the page.
  • Servers outside a group can be added by their address, and servers that announce themselves on the local network are listed for one tap. A self-signed certificate is trusted once by its fingerprint, and the app warns when a server later shows a different one.
  • Downloads and uploads work as in a browser. Exports, recovery kits, flash ZIPs and database dumps land in the phone's Downloads, and a settings import opens the phone's file picker.
  • Install BombVault in the browser. A web app manifest lets Chrome and Edge install the interface as an app in its own window. Nothing is cached, so an update shows at once.

Companions

  • Settings, Apps. A new page beside Integrations with a card for each companion. ParleyPort's card offers its Unraid template, copies the Docker command that starts it, and leads to its repository and to the relay settings under Pairing. The BombVault Widget's card offers its template and its repository, and installs or removes the plugin over the host SSH connection. That part sat on the dashboard widget card under Integrations before; the embeddable activity log stays there.

Placement defaults

  • One row per domain under Settings, Storage, Placement defaults, with the same three segments. Its copies apply at once to every item without a choice of its own, and to the project folders of Compose stacks. Its location applies to a new item at that item's first backup.
  • Every save says what it changes. Before it saves, a default names each target that gains or loses items and how many snapshots that means. Apply to items without backups puts every item that has no backup yet back on the default, and the question names the items that lose a choice of their own.
  • A new off-site target asks before it copies. Adding a target, filling a domain's off-site field or accepting a mesh offer first says how many items the target will receive and, where known, how much history that is, and offers to leave out the items other targets already leave out.

Direct repositories

  • Off-site only, straight to the target. Choosing a target's direct repository opens a dialog with a suggested location next to the target and a connection test that creates nothing. Create and use creates the repository and points the item or the default at it.
  • It follows its target. A direct repository takes the target's key, storage class, limits, append-only setting, retention including the yearly rule, and compression, and changes with them. The Repositories card shows it read-only. When the target's new key cannot open it, the direct repository keeps the key it has and the save says so. Lowering the target's retention or switching off append-only asks first when items keep their only copy there.
  • Its snapshots are marked. They carry the tag bv:direct, and every other retention pass keeps them, so a direct repository that lost its link to its target never ages by the local rules. A target cannot be removed while an item or a default uses its direct repository.

One timeline per item

  • Every place in one list. Containers, VMs, folder sets, the flash and the app configuration list their backups as one timeline over the repository they are written to and every off-site target. A backup copied off-site appears once, marked with each place that holds it, and each row restores, downloads or browses from the place you pick. An off-site place is read only when you press Check on its line, so the page opens without waiting for a bucket. The line's info bubble says so, and the backups found there stay in the list until you leave the page.
  • Deleting says what is left. Deleting a backup at one place first checks the others and says whether it was the last copy. Delete everywhere removes the backup from every place at once.
  • A stack restore asks about its project folder. When the off-site place a stack is restored from has no copy of the stack's project folder, BombVault asks whether to take it from this server instead.

After a rebuild

  • Off-site copies wait for you. After a rebuild through Discover without the old settings, the choices of which items to leave out are gone. Off-site replication of every rebuilt domain therefore pauses, the Dashboard shows it in amber and a notification goes out. Confirm default on the Placement defaults card shows what the next run would copy, lists the names in the backups that have no entry so you can leave them out, and ends the pause.

🎨 Changed

  • A domain's off-site field saves a new location only when you confirm it, with Enter, by leaving the field or with its Save button, and asks first how much the new location will receive. Clearing the field switches its target off and keeps it, with its credentials, for the next location you enter.
  • Backblaze B2 is set up through its S3 endpoint. The hints no longer suggest b2: locations, because the cloud credentials hold S3 keys. Enter the key ID and application key as the S3 credentials and use an address such as s3:https://s3.eu-central-003.backblazeb2.com/bucket/path.
  • The source switch above the backup lists is gone. The timeline shows every place in each row instead, and the flash's download and plugin list sit in the row of the place they read from.
  • A repository a default points at cannot be moved or deleted, the same as one an item uses. A location inside or around another repository, target or domain path is refused.
  • Every glyph follows one standard, shared with KnightLoader. Each meaning has one drawing, the same in both apps, and no two meanings share one. Prune gets a shredder of its own instead of the bin that Delete wears. Schedules, Notifications and Apps in the Settings rail come from the same set as the rest of the rail, and so do the back and forward arrows in the Android app. Security keeps a shield: a plain one, beside the checked shield of Integrity.
  • The relay's README button shows ParleyPort's logo, in white on a dark ground like every other mark, and every README button keeps its mark nearer the left edge, clear of the words.
  • The README's buttons stand in groups, the server first, then the phone and the companions, with more room between groups than between rows. The comparison with other backup tools has a section of its own after the screenshots.
  • The README asks for Android testers and has buttons for Google Play, F-Droid and the APK, at the top and again in its section on the app, and its screenshots end with a picture of the app. The app is in a closed test on Google Play until it can go public, and the F-Droid listing follows.
  • The README is shorter and points to the documentation. The documentation has a new page for the Android app, and in all 26 languages it now covers Settings, Apps, placement on the configuration page and everything the README used to explain at length.
  • The Save button has a new floppy. It is Material Design Icons' content-save (Apache 2.0), the drawing GlimStone 3.1.6 uses in every app. The old one came from Vecteezy under a licence that is not open.

⚡ Improved

  • Your own relay is ParleyPort. The relay card under Pairing names the ParleyPort container from the Community Apps as one of the two ways to run your own relay, in every language and in the documentation. It is the same relay as before, now published on its own so BombVault and KnightLoader share one.
  • The project relay has a new address, parleyport.halleluja.design, and its card says it runs ParleyPort. Nothing to change on your side: the project relay was never stored, so every instance dials the new name after the update, and the old one keeps answering for a few releases. A DNS filter that allows only the old name needs the new one too.
  • Fewer calls to paid storage. An off-site run lists each target once and hands restic the exact snapshots to copy. A run with nothing new only lists, and forget and prune run at a target only after its rules changed. Stale locks on a remote repository are cleared only when a lock actually stands in the way, for off-site copies, backups and deletes as well as for changed-block VM backups, pulls, restore probes and start tests.
  • Compose project folders age. The snapshots of a stack's project folder now follow the local retention and the retention of each target, like every other item.
  • The MCP tool get_storage_stats lists the off-site targets of a domain beside its own repositories, each marked as off-site.
  • The settings export carries placement. Defaults and copy rules travel in the file, and so do a named repository's link to its target and its Off the premises mark. A file from an older version leaves this instance's placement as it is.
  • GET /api/progress?snapshot=1 sends what is running and ends the stream, for scripts that want one answer instead of a live feed.
  • The settings search finds the new controls. The Placement defaults card with its segments and fields, and the Off the premises switch of the Repositories card, open their page on Storage when you search for them.

🐛 Fixed

  • The Instances page no longer goes blank when a member of the group has not been polled yet, which happened right after pairing.
  • A repository the key does not open is reported, not treated as empty. BombVault used to take such a repository for a missing one and could try to create a new one in its place.
  • A restore from a switched-off target reads that target. A source naming a target that is off or unknown is refused instead of falling back to another target.
  • Clearing a domain's off-site field no longer deletes the target, and saving settings never overwrites a target other than the domain's first one.

🌐 Translations

  • Every new card, row, question and message: 272 new strings in all 42 languages, and the app's own messages in the same languages.
  • Placement per item, the placement defaults, direct repositories and the pause after a rebuild in all 26 documentation languages, on the off-site and recovery, features and configuration pages.
  • Some labels read better: Korean tells Storage and Repositories apart, Swedish says lösennyckel for a passkey, Hungarian says biztonsági mentés where it means a backup, and Quiet toasts no longer sounds like the Notifications page. The documentation lists all four animation levels and names the pairing buttons the way the app does.

Upgrading

  • Nothing has to be changed. The database is upgraded on the first start, settings export files from older versions still import, and no setting or environment variable was removed or renamed. restic stays at 0.17.3 and the repositories are left as they are.
  • Everything keeps going where it went. Every existing item counts as placed where it is, and a domain that already replicates gets a confirmed default that copies every item to every target, so the first run after the update copies what it copied before.
  • The first off-site run after the update trims old project folders. Compose project folder snapshots kept so far without a limit are aged to the local retention and to the retention of each target.
  • Each target is listed once more on its first run, to record what it holds for the cards. Until then a card says the target has not been listed yet. A failed run from before the update counts only when no run to that target has succeeded since.
  • Pair the app with servers on this version. A server on an older version can be in the same group, but it shows the app as a plain instance, and the app reads that server's activity only with a sign-in.

Don't miss a new bombvault release

NewReleases is sending notifications on new releases.