Every card can pause its item's schedule with one click, and the box that receives off-site copies can start an append-only rest-server for the rest of your group and hand each instance a login of its own. The interface follows GlimStone 3.1.6, and the Apps page offers the Android app with its APK and a QR code. A container from another server's repository can be restored onto a plain Docker host, even when its network does not exist there.
✨ Added
Pause from the card
- Pause schedule on every card. Containers, VMs and folder sets have Pause schedule beside Back up now, and Resume schedule to bring the item back. A paused item is left out of scheduled runs and of Backup Everything; Back up now still works.
- One switch, two places. The button sets the same value as Include in schedule, so the two always agree, and the counts of scheduled items follow either one.
- A grey badge. A paused item wears Schedule paused, with an info bubble that says what it skips.
Receiving server
- One click on the receiving box. Set up receiving server on the Receiver tab asks for a folder and a port, then starts
restic/rest-serverthrough the Docker socket in append-only mode with private repositories. It refuses when a container calledrest-serverexists or the port is taken. - Editable in the Docker tab. BombVault writes the container's Unraid template to the flash drive, or offers it as a download when the flash drive is out of reach.
- Checked right away. The tamper test runs against the new server and the card shows whether it refuses deletes. Check again repeats it.
- Offered to your group. The other instances find the server in the destination wizard under From your group, with the address filled in. Each gets a login of its own the first time it picks the server and writes only into its own folder, so partners never meet. Revoke login on the card takes one away and leaves what it copied in place.
- A login for someone outside the group is created with the server and shown once.
Android app on the Apps page
- The app comes first. Settings, Apps starts with the Android app: Google Play and F-Droid marked as coming, and the APK for the release the server runs, with its version in the card's corner.
- A QR code for the phone. On a computer the APK button carries a QR code segment, so the file goes to the phone without typing a link.
Restoring onto another kind of host
- A network picker for a container from another server. When its network does not exist here, such as an Unraid
br0network on a plain Docker host, the container's row under Restore from another BombVault repo offers this server's networks, withbridgechosen. The container keeps its other networks and gets its IP and MAC address from the chosen one. - Checked before anything is written. The pre-flight check shows a red Network line until a network is chosen, and the restore refuses instead of writing the appdata and then failing to create the container.
Destinations
- Silo is in the list of your own S3 servers. It is the community fork of MinIO maintained by Pigsty, and BombVault talks to it as MinIO, with object lock.
- Take over a hand-typed target. A destination lists the off-site targets typed in by hand whose repository lies in one of its folders, under Already under this destination. Take over hangs one on the destination: it keeps its repository, snapshots, retention and placement, and takes the destination's name, credentials, storage class and append-only switch.
- Checked first. BombVault takes a target over only after the destination's sign-in has opened its repository, and it refuses to put an append-only target under a destination that is not append-only.
- The primary too. Taking over the target a domain's off-site field names empties that field and moves the target into the list of off-site targets below it. Saving the old address into the field again is refused, so the target cannot slip back.
- Flash, self-backup and ZFS too. These domains have no placement row, so their off-site section has an Add from button for each destination, which creates the domain's repository in a folder under it. The placement defaults card links there.
🎨 Changed
- GlimStone 3.1.6. The settings column is a single tab stop and the arrow keys walk it, Escape steps the settings search back one thing at a time, and the app's Danger zone has a colour of its own.
- The direct repository's connection test turns its button green or red with the verdict, like every other test.
- The Retention page says which target its off-site rules cover. They apply to each domain's primary off-site target, the address in its off-site field. Every other off-site target, including one made from a destination, keeps its own rules, and with only zeros there BombVault never prunes it.
- The Android app's store description names the default relay,
parleyport.halleluja.design, and says that your own ParleyPort works too. Its "What's new" lists this version.
🐛 Fixed
- Restoring from another server onto a plain Docker host. The guard against writing into an unmounted folder only trusted mounts below the Host Data folder. On a plain Docker host that folder is the storage itself, so every container and VM restore from another server was refused there.
- Binds after a restore between hosts with different data roots. A container restored from an Unraid server onto a host with another root, such as
/srv/appdata, kept its/mnt/...binds and started without its data. The binds follow the appdata to where it was restored. - A restic address in the S3 endpoint field. Pasting the address restic uses, such as
s3:http://nas:9000/bucket/folder, made the connection test fail with an error about an invalid region. BombVault keeps only the server from it, and the bucket and folder are picked in the next step.
🌐 Translations
- The pause button, the receiving server, the Android card, the network picker, the takeover, the Add from button and every new message in all 42 languages.
- The pause button, the receiving server, the network picker, Silo, the takeover and the Add from button in all 26 documentation languages, on the off-site and recovery, features and Android pages.
Upgrading
- Nothing has to be changed. The database is upgraded on the first start. An item that was out of the schedule before shows as paused, because it is the same switch.