Skip to content

Releases: borgmatic-collective/borgmatic

borgmatic 1.8.5

20 Nov 05:16
Compare
Choose a tag to compare
  • #701: Add a "skip_actions" option to skip running particular actions, handy for append-only or
    checkless configurations. See the documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/set-up-backups/#skipping-actions
  • #701: Deprecate the "disabled" value for the "checks" option in favor of the new "skip_actions"
    option.
  • #745: Constants now apply to included configuration, not just the file doing the includes. As a
    side effect of this change, constants no longer apply to option names and only substitute into
    configuration values.
  • #779: Add a "--match-archives" flag to the "check" action for selecting the archives to check,
    overriding the existing "archive_name_format" and "match_archives" options in configuration.
  • #779: Only parse "--override" values as complex data types when they're for options of those
    types.
  • #782: Fix environment variable interpolation within configured repository paths.
  • #782: Add configuration constant overriding via the existing "--override" flag.
  • #783: Upgrade ruamel.yaml dependency to support version 0.18.x.
  • #784: Drop support for Python 3.7, which has been end-of-lifed.

borgmatic 1.8.4

27 Oct 05:21
Compare
Choose a tag to compare
  • #715: Add a monitoring hook for sending backup status to a variety of monitoring services via the
    Apprise library. See the documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#apprise-hook
  • #748: When an archive filter causes no matching archives for the "rlist" or "info"
    actions, warn the user and suggest how to remove the filter.
  • #768: Fix a traceback when an invalid command-line flag or action is used.
  • #771: Fix normalization of deprecated sections ("location:", "storage:", "hooks:", etc.) to
    support empty sections without erroring.
  • #774: Disallow the "--dry-run" flag with the "borg" action, as borgmatic can't guarantee the Borg
    command won't have side effects.

borgmatic 1.8.3

30 Sep 20:37
Compare
Choose a tag to compare
  • #665: BREAKING: Simplify logging logic as follows: Syslog verbosity is now disabled by
    default, but setting the "--syslog-verbosity" flag enables it regardless of whether you're at an
    interactive console. Additionally, "--log-file-verbosity" and "--monitoring-verbosity" now
    default to 1 (info about steps borgmatic is taking) instead of 0. And both syslog logging and
    file logging can be enabled simultaneously.
  • #743: Add a monitoring hook for sending backup status and logs to Grafana Loki. See the
    documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#loki-hook
  • #753: When "archive_name_format" is not set, filter archives using the default archive name
    format.
  • #754: Fix error handling to log command output as one record per line instead of truncating
    too-long output and swallowing the end of some Borg error messages.
  • #757: Update documentation so "sudo borgmatic" works for pipx borgmatic installations.
  • #761: Fix for borgmatic not stopping Borg immediately when the user presses ctrl-C.
  • Update documentation to recommend installing/upgrading borgmatic with pipx instead of pip. See the
    documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/set-up-backups/#installation
    https://torsion.org/borgmatic/docs/how-to/upgrade/#upgrading-borgmatic

borgmatic 1.8.2

14 Aug 19:56
Compare
Choose a tag to compare
  • #345: Add "key export" action to export a copy of the repository key for safekeeping in case
    the original goes missing or gets damaged.
  • #727: Add a MariaDB database hook that uses native MariaDB commands instead of the deprecated
    MySQL ones. Be aware though that any existing backups made with the "mysql_databases:" hook are
    only restorable with a "mysql_databases:" configuration.
  • #738: Fix for potential data loss (data not getting restored) in which the database "restore"
    action didn't actually restore anything and indicated success anyway.
  • Remove the deprecated use of the MongoDB hook's "--db" flag for database restoration.
  • Add source code reference documentation for getting oriented with the borgmatic code as a
    developer: https://torsion.org/borgmatic/docs/reference/source-code/

borgmatic 1.8.1

04 Aug 04:56
Compare
Choose a tag to compare

borgmatic 1.8.0

19 Jul 05:51
Compare
Choose a tag to compare
  • #575: BREAKING: For the "borgmatic borg" action, instead of implicitly injecting
    repository/archive into the resulting Borg command-line, pass repository to Borg via an
    environment variable and make archive available for explicit use in your commands. See the
    documentation for more information:
    https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/
  • #719: Fix an error when running "borg key export" through borgmatic.
  • #720: Fix an error when dumping a database and the "exclude_nodump" option is set.
  • #724: Add "check_i_know_what_i_am_doing" option to bypass Borg confirmation prompt when running
    "check --repair".
  • When merging two configuration files, error gracefully if the two files do not adhere to the same
    format.
  • #721: Remove configuration sections ("location:", "storage:", "hooks:" etc.), while still keeping
    deprecated support for them. Now, all options are at the same level, and you don't need to worry
    about commenting/uncommenting section headers when you change an option (if you remove your
    sections first).
  • #721: BREAKING: The retention prefix and the consistency prefix can no longer have different
    values (unless one is not set).
  • #721: BREAKING: The storage umask and the hooks umask can no longer have different values (unless
    one is not set).
  • BREAKING: Flags like "--config" that previously took multiple values now need to be given once
    per value, e.g. "--config first.yaml --config second.yaml" instead of "--config first.yaml
    second.yaml". This prevents argument parsing errors on ambiguous commands.
  • BREAKING: Remove the deprecated (and silently ignored) "--successful" flag on the "list" action,
    as newer versions of Borg list successful (non-checkpoint) archives by default.
  • All deprecated configuration option values now generate warning logs.
  • Remove the deprecated (and non-functional) "--excludes" flag in favor of excludes within
    configuration.
  • Fix an error when logging too-long command output during error handling. Now, long command output
    is truncated before logging.

borgmatic 1.7.15

25 Jun 05:23
Compare
Choose a tag to compare
  • #326: Add configuration options and command-line flags for backing up a database from one
    location while restoring it somewhere else.
  • #399: Add a documentation troubleshooting note for MySQL/MariaDB authentication errors.
  • #529: Remove upgrade-borgmatic-config command for upgrading borgmatic 1.1.0 INI-style
    configuration.
  • #529: Deprecate generate-borgmatic-config in favor of new "config generate" action.
  • #529: Deprecate validate-borgmatic-config in favor of new "config validate" action.
  • #697, #712, #716: Extract borgmatic configuration from backup via new "config bootstrap"
    action—even when borgmatic has no configuration yet!
  • #669: Add sample systemd user service for running borgmatic as a non-root user.
  • #711, #713: Fix an error when "data" check time files are accessed without getting upgraded
    first.

borgmatic 1.7.14

04 Jun 05:24
Compare
Choose a tag to compare
  • #484: Add a new verbosity level (-2) to disable output entirely (for console, syslog, log file,
    or monitoring), so not even errors are shown.
  • #688: Tweak archive check probing logic to use the newest timestamp found when multiple exist.
  • #659: Add Borg 2 date-based matching flags to various actions for archive selection.
  • #703: Fix an error when loading the configuration schema on Fedora Linux.
  • #704: Fix "check" action error when repository and archive checks are configured but the archive
    check gets skipped due to the configured frequency.
  • #706: Fix "--archive latest" on "list" and "info" actions that only worked on the first of
    multiple configured repositories.

borgmatic 1.7.12

13 Apr 22:13
Compare
Choose a tag to compare

borgmatic 1.7.11

03 Apr 23:11
Compare
Choose a tag to compare
  • #479, #588: BREAKING: Automatically use the "archive_name_format" option to filter which archives
    get used for borgmatic actions that operate on multiple archives. Override this behavior with the
    new "match_archives" option in the storage section. This change is "breaking" in that it silently
    changes which archives get considered for "rlist", "prune", "check", etc. See the documentation
    for more information:
    https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#archive-naming
  • #479, #588: The "prefix" options have been deprecated in favor of the new "archive_name_format"
    auto-matching behavior and the "match_archives" option.
  • #658: Add "--log-file-format" flag for customizing the log message format. See the documentation
    for more information:
    https://torsion.org/borgmatic/docs/how-to/inspect-your-backups/#logging-to-file
  • #662: Fix regression in which the "check_repositories" option failed to match repositories.
  • #663: Fix regression in which the "transfer" action produced a traceback.
  • Add spellchecking of source code during test runs.