BackupTrust Pro 2.3 (23) — Beta

BETA, FOR TESTING ONLY. BackupTrust Pro is not a commercial product and comes with no support and no warranty. Keep your own independent backup of all data. You are responsible for your data.

Fixes false "offline" detection for nested LucidLink mounts. Saved folders do not need to be recreated.

New: Refresh Paths in the plan editor's Diagnostics section checks availability without starting a backup, with results in App Diagnostics.

When a run is refused as unavailable, the log now records the saved path and the matched mount.

https://github.com/macvfx/BackupTrust-Pro/blob/main/RELEASE-NOTES-2.3-BUILD-23.md
https://github.com/macvfx/BackupTrust-Pro/blob/main/README.md

BackupTrust Pro 2.4 (24) — Beta

BETA, FOR TESTING ONLY. BackupTrust Pro is not a commercial product and comes with no support and no warranty. Keep your own independent backup of all data. You are responsible for your data.

Fixes three ways hidden files were handled wrongly. This matters only for plans with Include hidden files turned on.

Restoring an encrypted backup skipped every hidden file, silently. A plan that includes hidden files backs up .env as .env.aea, which is still hidden. The restore script on the destination always restored them. Affects 2.2 and 2.3.

Mirror mode now removes hidden files deleted from the source, and hidden files on an overflow destination are now reclaimable once the same file is on a main destination.

BackupTrust's own folders, disk metadata, .DS_Store and ._ files are never treated as your files: never restored, never deleted.

https://github.com/macvfx/BackupTrust-Pro/blob/main/RELEASE-NOTES-2.4.md
https://github.com/macvfx/BackupTrust-Pro/blob/main/README.md

BackupTrust Pro 2.2 (22) — Testing

Encrypted backups can now be restored from inside the app, Pro only.

Settings > Encryption > Restore Files, or the Restore button beside an encrypted
destination in a plan. Choose the backup, its recovery key file and where the files
should go; the folder structure is rebuilt and restored files keep their original
dates.

Files already present in the restore folder are skipped rather than replaced unless
you ask, previous versions are left out unless you ask, and a wrong recovery key is
refused before anything is written. One file failing to decrypt does not stop the
rest.

Test a Restore still checks that a backup opens without writing anything. Restoring
without BackupTrust, using the script on the destination, works as before.

BackupTrust Pro 2.1 (21) — Testing

Encryption test build, Pro only.

Destinations can now be encrypted. Create a key in Settings > Encryption, save its
recovery key file, then choose that key under a destination in the plan editor.
Files written there become .aea archives that only that recovery file can open.

BackupTrust keeps only the public half of the key, so a scheduled run needs no
password and this Mac cannot read its own backups. The recovery key file is the
only way to decrypt them - keep it somewhere separate from the backup.

Each encrypted destination carries restore instructions and a restore script that
needs only the aea tool built into macOS. Test a Restore decrypts a sample to
prove a backup opens.

BackupTrust Pro 2.0 (20) — Testing

BackupTrust Pro 2.0 (20)

This testing prerelease adds proactive SMB preparation through SMB Connect 0.7.4 or later and corrects the Pro documentation link.

Highlights

• Optional pre-run requests for missing SMB volumes before manual or scheduled backups.
• One request per missing Mount Name, with same-volume coalescing and different-volume serialization.
• Menu-bar Mount with SMB Connect, Try Again, status, and cancellation controls.
• Factual timeout guidance and correlated Mount Name, UUID, elapsed-time, and outcome logging.
• Protection against stale /Volumes directories, unsafe Mount Names, and duplicate-style -1 or -2 paths.
• BackupTrust Standard behavior remains unchanged.

Requirements

• macOS 14 or later on Apple Silicon or Intel.
• SMB Connect 0.7.4 or later for proactive SMB preparation.
• A unique Mount Name, saved credentials, and Allow apps to request this volume enabled for each requested share.

Validation boundary

The universal Developer ID build was notarized by Apple and passed signature, staple, Gatekeeper, version/build, architecture, and SHA-256 validation. Automated tests covered the SMB request and availability logic. This prerelease has not performed destructive unmount or live NAS mutation testing.

SHA-256 for BackupTrust Pro.dmg:

2b9e72f09ff34f00cf58be5dffd33d6bd1d87712a38def9ab108b6e54c878ba0