Skip to content

v0.6.0

Choose a tag to compare

@shellharbor shellharbor released this 26 Sep 09:19
· 19 commits to main since this release

Backfort v0.6.0

Backfort v0.6.0 is a major step forward for reliable Linux, Docker Compose, database, and offsite backup recovery.

Highlights

  • Docker Compose backups for explicit project files, named volumes, bind mounts, and database dumps.
  • Logical dump adapters for PostgreSQL, MySQL, MariaDB, MS SQL, and Oracle.
  • Quick backup commands:
    • quick for immediate file and directory backups;
    • quick-compose for portable Compose migration and recovery backups.
  • Local and rclone-backed destinations, including S3-compatible providers such as AWS S3, Cloudflare R2, DigitalOcean Spaces, Vultr Object Storage, Yandex Object Storage, and other rclone remotes.
  • Multi-destination copy policy with success.min_copies.
  • Optional age encryption, multiple recipients, Minisign signatures, and hardened symmetric GPG encryption.
  • Retention with GFS-style rules, max_age_days, protected pinned backups, and safe date-range deletion.
  • restore --pick for interactive terminal selection of completed backup versions.
  • diff for comparing backup manifests in text or JSON form.
  • watchdog dead-man’s-switch checks for missing or stale backups.
  • Unified notifications for Telegram, ntfy, webhooks, and SMTP, with antiflooding, daily digests, redaction, and actionable restore hints.
  • Comprehensive examples, recovery documentation, migration runbooks, and GitHub Wiki pages.

Reliability improvements

  • Fixed file-source preflight so valid local backup jobs complete correctly.
  • Made executable permissions for the CLI and test adapters a CI-enforced requirement.
  • Updated generated Telegram and JSON-list output for Mike Farah yq v4 compatibility.
  • Improved encryption test fidelity by modelling streaming age decryption.
  • Normalized test backup metadata to valid JSON.
  • Expanded CI coverage for Compose, rclone, encryption, watchdog, notifications, pins, deletion, diff, quick backups, and interactive restore.

Upgrade notes

No migration is required for existing YAML configurations.

Before upgrading production systems, run:

backfort.sh -c /etc/backfort/config.yaml doctor
backfort.sh -c /etc/backfort/config.yaml --dry-run run

Then perform a full verification and staged restore drill for at least one important backup:

backfort.sh -c /etc/backfort/config.yaml verify latest --job important-files --full
backfort.sh -c /etc/backfort/con