v0.11.0

[aawsome]

Hello rusticeans,

we are happy to release rustic 0.11.0! This release introduces some breaking changes. If you use it with an existing config or repository, please take a look at https://rustic.cli.rs/docs/breaking_changes.html.

New features in 0.11.0 are:

• The options to determine which information is stored for nodes have been refactored. Using set-atime, set-ctime, set-devid, set-xattr allows to fine-tune this to your needs.
• The option set-blockdev = "file" allows to backup block devices as normal files allowing to e.g. backup disc-image directly.
• Support for multiple parents has been added.
• Logging has been overworked, see below.
• rustic rewrite is now able to rewrite trees allowing to remove things from existing snapshots.
• Additional to using passwords, rustic is now able to directly use the masterkey. The masterkey can be also exported as QR image allowing for a paper disaster revovery :-) Access mode can be switched any time, see https://rustic.cli.rs/docs/commands/misc/key.html
• warm-up for cold storage has been improved supporting more ways to warm-up and parallel warm-up.
• The latest~N syntax now works for all commands.

For more new features, optimizations and bugfixes, see below.

Thanks a lot to everybody who contributed!

Changelog

Added

• [breaking] extend LocalSourceSaveOptions (#461)
• [breaking] Add support for multiple parents (#427)
• [breaking] Add log-level-logfile, -dryrun and -dependencies options; remove quiet options (#1565)
• [breaking] Allow to rewrite trees (#1644,#462,#1651,#465)
• Allow to use masterkey instead of password/keyfile (#1654,#468)
• Add support for batch warmup (#438)
• (commands) allow to identify snapshots with "latest" or "latest~N" (N >= 0) (#1563)
• Allow ls to list local files (using excludes) (#1645)
• Add default behavior for diff without arguments (#1673)
• Add option --forget-time to forget (#1670)
• Update copy and add --force (#1653,#464)
• improve restore algorithm (#453)
• Optimize prune rewrite (#448)

Fixed

• update clap help (#1663)
• handle all arg combinations for diff command (#1639)
• use filtered snapshots for repair command (#1636)
• fix rewrite file count (#466)
• Return error if too few snapshots for latest~N (#459)
• Use early-delete-index only if instant-delete is selected (#457)
• improve error handling for missing UID/GID name (#454)
• FreeBSD build (#440)

Other

• [breaking] Use jiff instead of chrono (#1625,#452)
• Update MSRV to 1.88.0 (#1664)
• Document OPENDAL* env variables (#1646)
• Add root directory to sftp_hetzner_sbox.toml (#1628)
• update dependencies (#1635,#1637,#1667,#1674)

---

This discussion was created from the release v0.11.0.

[kapitainsky]

It is fantastic that rustic is getting better and feature rich but at the same time I think that it is becoming more and more important to keep up to date with documentation.

At the moment to understand some new options I have to browse through pull requests and issues. And even then I miss 100% clarity. Maybe it is just me:) But I would be grateful if provided documentation is more like "for dummies" style.

What I am missing are some examples of new features. For example something as trivial as how do I use rustic rewrite to remove wrongly backed up file from my repo? Or for set-blockdev, how do I backup some sample partition?

[aawsome]

Hi @kapitainsky Thanks for the feedback!

Docs have been in progress a bit, but now I think I can link the docs of some of the major new features:

• blockdevice backup: https://rustic.cli.rs/docs/commands/backup/blockdev.html
• rewrite command: https://rustic.cli.rs/docs/commands/misc/rewrite.html
• using masterkey: https://rustic.cli.rs/docs/commands/misc/key.html
• batch warmup: https://rustic.cli.rs/docs/commands/init/cold_storage.html

Help on the docu is highly appreciated! If anyone can describe something missing of finds errors in the docu, please don't hesitate to propose a change. The "edit" button on the top right makes this really easy.

[kapitainsky]

Thank you! Now when you provided initial overview (this is the hardest step) it is much easier to start experimenting with new features. And hopefully community can help to improve docs further.