- Update to borgbackup 1.1.1
- Compatibility notes:
* When upgrading from borg 1.0.x to 1.1.x, please note:
* read all the compatibility notes for 1.1.0*, starting from 1.1.0b1.
* borg might ask some security-related questions once after upgrading.
You can answer them either manually or via environment variable.
One known case is if you use unencrypted repositories, then it will ask
about a unknown unencrypted repository one time.
* your first backup with 1.1.x might be significantly slower (it might
completely read, chunk, hash a lot files) - this is due to the
--files-cache mode change (and happens every time you change mode). You
can avoid the one-time slowdown by using the pre-1.1.0rc4-compatible mode
(but that is less safe for detecting changed files than the default).
See the --files-cache docs for details.
* The deprecated --no-files-cache is not a global/common option any more, but
only available for borg create (it is not needed for anything else).
Use --files-cache=disabled instead of --no-files-cache.
* The nodump flag ("do not backup this file") is not honoured any more by
default because this functionality (esp. if it happened by error or
unexpected) was rather confusing and unexplainable at first to users.
If you want that "do not backup NODUMP-flagged files" behaviour, use:
borg create --exclude-nodump ...
- Fixes:
* borg recreate: correctly compute part file sizes. fixes cosmetic, but
annoying issue as borg check complains about size inconsistencies of part
files in affected archives. you can solve that by running borg recreate
on these archives.
* bsdflags support: do not open BLK/CHR/LNK files, avoid crashes and slowness
* recreate: don't crash on attic archives w/o time_end
* don't crash on repository filesystems w/o hardlink support (forwarded request 535946 from alarrosa)