New
- Stream database dumps into the archive (#540). A new plan option, "Stream database dumps into the archive", sits under the MySQL and PostgreSQL plugin cards and shows when one of them is selected. With it on, each dump goes straight into borg instead of being written to the client's disk first, so you don't need free space for the dumps. It's off by default: a streamed dump runs as fast as borg can take it, so on a slow link the dump stays open longer than a dump to disk would. Windows clients and pg_dump's directory format keep dumping to disk. Thanks to @pano9000 for the suggestion.
- Plain .sql dumps by default. New MySQL, PostgreSQL and MongoDB plugin configurations no longer gzip their dumps. Plain dumps deduplicate far better from one backup to the next; on my test client one run added about 800 MB to the repository against about 2.4 GB for the gzipped runs before it. Existing configurations keep their setting. When compression is on, the agent now uses
gzip --rsyncablewhere it's available. - Duplicate a backup template (#543). Templates have a Duplicate action that makes a copy named "Name (copy)" and opens it for editing. Thanks to @pano9000.
Fixes
- Backups that completed with warnings show as warnings (#542). A backup where a plugin failed (a database dump, for example) showed as a success on the client page, repository page and dashboard. They now say "completed with warnings". In Prometheus metrics,
bbs_plan_last_run_statusis now 2 for a backup with warnings (1 still means failed), and the README has an example alert for it. Thanks to @pano9000 for the report. - Upgrade page no longer hangs after a deferred upgrade. When an upgrade waited for running backups and then ran from the scheduler, the upgrade page could stay on "upgrading" after it had finished. It now reads the upgrade log from the BBS storage folder and checks the installed version when the log is missing.
Agents update to 2.99.1 in this release.