Skip to content

Releases: borgmatic-collective/borgmatic

borgmatic 1.6.2

31 May 16:42
Compare
Choose a tag to compare
  • #523: Reduce the default consistency check frequency and support configuring the frequency
    independently for each check. Also add "borgmatic check --force" flag to ignore configured
    frequencies. See the documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#check-frequency
  • #536: Fix generate-borgmatic-config to support more complex schema changes like the new
    Healthchecks configuration options when the "--source" flag is used.
  • #538: Add support for "borgmatic borg debug" command.
  • #539: Add "generate-borgmatic-config --overwrite" flag to replace an existing destination file.
  • Add Bash completion script so you can tab-complete the borgmatic command-line. See the
    documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/set-up-backups/#shell-completion

borgmatic 1.6.1

24 May 23:23
Compare
Choose a tag to compare
  • #294: Add Healthchecks monitoring hook "ping_body_limit" option to configure how many bytes of
    logs to send to the Healthchecks server.
  • #402: Remove the error when "archive_name_format" is specified but a retention prefix isn't.
  • #420: Warn when an unsupported variable is used in a hook command.
  • #439: Change connection failures for monitoring hooks (Healthchecks, Cronitor, PagerDuty, and
    Cronhub) to be warnings instead of errors. This way, the monitoring system failing does not block
    backups.
  • #460: Add Healthchecks monitoring hook "send_logs" option to enable/disable sending borgmatic
    logs to the Healthchecks server.
  • #525: Add Healthchecks monitoring hook "states" option to only enable pinging for particular
    monitoring states (start, finish, fail).
  • #528: Improve the error message when a configuration override contains an invalid value.
  • #531: BREAKING: When deep merging common configuration, merge colliding list values by appending
    them. Previously, one list replaced the other.
  • #532: When a configuration include is a relative path, load it from either the current working
    directory or from the directory containing the file doing the including. Previously, only the
    working directory was used.
  • Add a randomized delay to the sample systemd timer to spread out the load on a server.
  • Change the configuration format for borgmatic monitoring hooks (Healthchecks, Cronitor,
    PagerDuty, and Cronhub) to specify the ping URL / integration key as a named option. The intent
    is to support additional options (some in this release). This change is backwards-compatible.
  • Add emojis to documentation table of contents to make it easier to find particular how-to and
    reference guides at a glance.

borgmatic 1.6.0

26 Apr 17:08
Compare
Choose a tag to compare
  • #381: BREAKING: Greatly simplify configuration file reuse by deep merging when including common
    configuration. See the documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#include-merging
  • #473: BREAKING: Instead of executing "before" command hooks before all borgmatic actions run (and
    "after" hooks after), execute these hooks right before/after the corresponding action. E.g.,
    "before_check" now runs immediately before the "check" action. This better supports running
    timing-sensitive tasks like pausing containers. Side effect: before/after command hooks now run
    once for each configured repository instead of once per configuration file. Additionally, the
    "repositories" interpolated variable has been changed to "repository", containing the path to the
    current repository for the hook. See the documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/add-preparation-and-cleanup-steps-to-backups/
  • #513: Add mention of sudo's "secure_path" option to borgmatic installation documentation.
  • #515: Fix "borgmatic borg key ..." to pass parameters to Borg in the correct order.
  • #516: Fix handling of TERM signal to exit borgmatic, not just forward the signal to Borg.
  • #517: Fix borgmatic exit code (so it's zero) when initial Borg calls fail but later retries
    succeed.
  • Change Healthchecks logs truncation size from 10k bytes to 100k bytes, corresponding to that
    same change on Healthchecks.io.

borgmatic 1.5.24

14 Mar 20:45
Compare
Choose a tag to compare
  • #431: Add "working_directory" option to support source directories with relative paths.
  • #444: When loading a configuration file that is unreadable due to file permissions, warn instead
    of erroring. This supports running borgmatic as a non-root user with configuration in ~/.config
    even if there is an unreadable global configuration file in /etc.
  • #469: Add "repositories" context to "before_" and "after_" command action hooks. See the
    documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/add-preparation-and-cleanup-steps-to-backups/
  • #486: Fix handling of "patterns_from" and "exclude_from" options to error instead of warning when
    referencing unreadable files and "create" action is run.
  • #507: Fix Borg usage error in the "compact" action when running "borgmatic --dry-run". Now, skip
    "compact" entirely during a dry run.

borgmatic 1.5.23

10 Feb 18:30
Compare
Choose a tag to compare
  • #394: Compact repository segments and free space with new "borgmatic compact" action. Borg 1.2+
    only. Also run "compact" by default when no actions are specified, as "prune" in Borg 1.2 no
    longer frees up space unless "compact" is run.
  • #394: When using the "atime", "bsd_flags", "numeric_owner", or "remote_rate_limit" options,
    tailor the flags passed to Borg depending on the Borg version.
  • #480, #482: Fix traceback when a YAML validation error occurs.

borgmatic 1.5.22

05 Jan 04:21
Compare
Choose a tag to compare
  • #288: Add database dump hook for MongoDB.
  • #470: Move mysqldump options to the beginning of the command due to MySQL bug 30994.
  • #471: When command-line configuration override produces a parse error, error cleanly instead of
    tracebacking.
  • #476: Fix unicode error when restoring particular MySQL databases.
  • Drop support for Python 3.6, which has been end-of-lifed.
  • Add support for Python 3.10.

borgmatic 1.5.21

22 Nov 21:20
Compare
Choose a tag to compare
  • #28: Optionally retry failing backups via "retries" and "retry_wait" configuration options.
  • #306: Add "list_options" MySQL configuration option for passing additional arguments to MySQL
    list command.
  • #459: Add support for old version (2.x) of jsonschema library.

borgmatic 1.5.20

12 Oct 00:04
Compare
Choose a tag to compare
  • Re-release with correct version without dev0 tag.

borgmatic 1.5.19

11 Oct 18:12
Compare
Choose a tag to compare
  • #387: Fix error when configured source directories are not present on the filesystem at the time
    of backup. Now, Borg will complain, but the backup will still continue.
  • #455: Mention changing borgmatic path in cron documentation.
  • Update sample systemd service file with more granular read-only filesystem settings.
  • Move Gitea and GitHub hosting from a personal namespace to an organization for better
    collaboration with related projects.
  • 1k ★s on GitHub!

borgmatic 1.5.18

06 Aug 16:04
Compare
Choose a tag to compare
  • #389: Fix "message too long" error when logging to rsyslog.
  • #440: Fix traceback that can occur when dumping a database.