borgmatic

• #245: Monitor backups with PagerDuty hook integration. See the documentation for more
  information: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pagerduty-hook
• #255: Add per-action hooks: "before_prune", "after_prune", "before_check", and "after_check".
• #274: Add ~/.config/borgmatic.d as another configuration directory default.
• #277: Customize Healthchecks log level via borgmatic "--monitoring-verbosity" flag.
• #280: Change "exclude_if_present" option to support multiple filenames that indicate a directory
  should be excluded from backups, rather than just a single filename.
• #284: Backup to a removable drive or intermittent server via "soft failure" feature. See the
  documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server/
• #287: View consistency check progress via "--progress" flag for "check" action.
• For "create" and "prune" actions, no longer list files or show detailed stats at any verbosities
  by default. You can opt back in with "--files" or "--stats" flags.
• For "list" and "info" actions, show repository names even at verbosity 0.

🎆

• #276, #285: Disable colored output when "--json" flag is used, so as to produce valid JSON ouput.
• After a backup of a database dump in directory format, properly remove the dump directory.
• In "borgmatic --help", don't expand $HOME in listing of default "--config" paths.

• #268: Override particular configuration options from the command-line via "--override" flag. See
  the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#configuration-overrides
• #270: Only trigger "on_error" hooks and monitoring failures for "prune", "create", and "check"
  actions, and not for other actions.
• When pruning with verbosity level 1, list pruned and kept archives. Previously, this information
  was only shown at verbosity level 2.

• Fix repository probing during "borgmatic init" to respect verbosity flag and remote_path option.
• #249: Update Healthchecks/Cronitor/Cronhub monitoring integrations to fire for "check" and
  "prune" actions, not just "create".

• #259: Optionally change the internal database dump path via "borgmatic_source_directory" option
  in location configuration section.
• #271: Support piping "borgmatic list" output to grep by logging certain log levels to console
  stdout and others to stderr.
• Retain colored output when piping or redirecting in an interactive terminal.
• Add end-to-end tests for database dump and restore. These are run on developer machines with
  Docker Compose for approximate parity with continuous integration tests.

• Fix "--repository" flag to accept relative paths.
• Fix "borgmatic umount" so it only runs Borg once instead of once per repository / configuration
  file.
• #253: Mount whole repositories via "borgmatic mount" without any "--archive" flag.
• #269: Filter listed paths via "borgmatic list --path" flag.

• #235: Pass extra options directly to particular Borg commands, handy for Borg options that
  borgmatic does not yet support natively. Use "extra_borg_options" in the storage configuration
  section.
• #266: Attempt to repair any inconsistencies found during a consistency check via
  "borgmatic check --repair" flag.

• #256: Fix for "before_backup" hook not triggering an error when the command contains "borg" and
  has an exit code of 1.
• #257: Fix for garbled Borg file listing when using "borgmatic create --progress" with
  verbosity level 1 or 2.
• #260: Fix for missing Healthchecks monitoring payload or HTTP 500 due to incorrect unicode
  encoding.

• Fix for database dump removal incorrectly skipping some database dumps.
• #123: Support for mounting an archive as a FUSE filesystem via "borgmatic mount" action, and
  unmounting via "borgmatic umount". See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/extract-a-backup/#mount-a-filesystem

• Show summary log errors regardless of verbosity level, and log the "summary:" header with a log
  level based on the contained summary logs.

• Show full error logs at "--verbosity 0" so you can see command output without upping the
  verbosity level.

• #247: With "borgmatic check", consider Borg warnings as errors.
• Dial back the display of inline error logs a bit, so failed command output doesn't appear
  multiple times in the logs (well, except for the summary).

• #241: When using the Healthchecks monitoring hook, include borgmatic logs in the payloads for
  completion and failure pings.
• With --verbosity level 1 or 2, show error logs both inline when they occur and in the summary
  logs at the bottom. With lower verbosity levels, suppress the summary and show error logs when
  they occur.

• #246: Fix for "borgmatic restore" showing success and incorrectly extracting archive files, even
  when no databases are configured to restore. As this can overwrite files from the archive and
  lead to data loss, please upgrade to get the fix before using "borgmatic restore".
• Reopen the file given by "--log-file" flag if an external program rotates the log file while
  borgmatic is running.

• #228: Database dump hooks for MySQL/MariaDB, so you can easily dump your databases before backups
  run.
• #243: Fix repository does not exist error with "borgmatic extract" when repository is remote.

• Monitor backups with Cronhub hook integration. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#cronhub-hook
• Fix Healthchecks/Cronitor hooks to skip actions when the borgmatic "--dry-run" flag is used.

• #238: In documentation, clarify when Healthchecks/Cronitor hooks fire in relation to other hooks.
• #239: Upgrade your borgmatic configuration to get new options and comments via
  "generate-borgmatic-config --source". See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/upgrade/#upgrading-your-configuration

• Verbosity level "-1" for even quieter output: Errors only (#236).

• Log to file instead of syslog via command-line "--log-file" flag (#233).

• #234: Support for Borg --keep-exclude-tags and --exclude-nodump options.