Debian Codegraph @

debian/NEWS

raw
1 btrbk (0.32.0-1) unstable; urgency=medium
2
3 The default for timestamp_format has changed from "short" to
4 "long". If you have not explicitely configured timestamp_format,
5 set "timestamp_format short" in btrbk.conf to revert old behavior.
6
7 Restrictions on subvolume names have been dropped (allowing
8 whitespace and special characters), changing the way command
9 arguments are escaped when called via ssh. If you are using
10 "ssh_filter_btrbk.sh" on remote hosts, make sure to update it with
11 the latest version.
12
13 -- Axel Burri <[email protected]> Sun, 23 Oct 2022 15:00:05 +0200
14
15 btrbk (0.27.0-1) unstable; urgency=low
16
17 Due to a bugfix in the scheduler [1] [2], previously preserved
18 monthly/yearly backups could get deleted when upgrading to
19 btrbk-0.27.0.
20
21 Before upgrading to btrbk-0.27.0, make sure to stop all cron jobs
22 or systemd timers calling btrbk.
23
24 After upgrading, run "btrbk prune --dry-run --print-schedule" and
25 check if any snapshots/backups would get deleted. If you want to
26 forcibly preserve a snapshot/backup forever, rename it:
27
28 mv mysubvol.YYYYMMDD mysubvol.YYYYMMDD.keep_forever
29
30 Note that btrbk ignores subvolumes with unknown naming scheme, e.g.
31 (".keep_forever" suffix in the example above).
32
33 [1] https://github.com/digint/btrbk/issues/217
34 [2] https://github.com/digint/btrbk/commit/719fb5f
35
36 -- Axel Burri <[email protected]> Tue, 16 Oct 2018 12:33:36 +0200
37
38 btrbk (0.23.0-1) unstable; urgency=medium
39
40 As the retention policy semantics changed with btrbk-0.23.0, the
41 configuration files created for earlier versions are not
42 compatible, and will force btrbk into "failsafe mode". Please read
43 "doc/upgrade_to_v0.23.0.md"
44 <http://digint.ch/btrbk/doc/archive/btrbk-0.23.0/upgrade_to_v0.23.0.html>
45 before upgrading to btrbk-0.23.0.
46 We apologize for the inconvenience.
47
48 -- Axel Burri <[email protected]> Sun, 24 Apr 2016 13:28:23 +0200