octoleo/restic
2
2
Fork 0
mirror of https://github.com/octoleo/restic.git synced 2024-12-22 10:58:55 +00:00
Code Issues Releases Wiki Activity

Further changelog polishing

Browse Source
This commit is contained in:
Michael Eischer 2022-08-24 21:13:14 +02:00
parent ee6b9dc492
commit 7a5d29ce24
5 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
changelog/unreleased/issue-21
View File

@ -7,8 +7,9 @@ that the repository cannot be read by restic versions prior to 0.14.0.
You can configure whether data is compressed with the option `--compression`. It You can configure whether data is compressed with the option `--compression`. It
can be set to `auto` (the default, which will compress very fast), `max` (which can be set to `auto` (the default, which will compress very fast), `max` (which
will trade backup speed and CPU usage for better compression), or `off` (which will trade backup speed and CPU usage for better compression), or `off` (which
disables compression). Each setting is only applied for the single run of restic. disables compression). Each setting is only applied for the current run of restic
The option can also be set via the environment variable `RESTIC_COMPRESSION`. and does *not* apply to future runs. The option can also be set via the
environment variable `RESTIC_COMPRESSION`.
To upgrade in place run `migrate upgrade_repo_v2` followed by `prune`. See the To upgrade in place run `migrate upgrade_repo_v2` followed by `prune`. See the
documentation for more details. The migration checks the repository integrity documentation for more details. The migration checks the repository integrity

4
changelog/unreleased/issue-3295
View File

@ -2,8 +2,8 @@ Change: Deprecate `check --check-unused` and add further checks
Since restic 0.12.0, it is expected to still have unused blobs after running Since restic 0.12.0, it is expected to still have unused blobs after running
`prune`. This made the `--check-unused` option of the `check` command rather `prune`. This made the `--check-unused` option of the `check` command rather
useless and tended to confuse users. This option has now been deprecated and useless and tended to confuse users. This option has been deprecated and is
is now ignored. now ignored.
The `check` command now also warns if a repository is using either the legacy The `check` command now also warns if a repository is using either the legacy
S3 layout or mixed pack files with both tree and data blobs. The latter is S3 layout or mixed pack files with both tree and data blobs. The latter is

3
changelog/unreleased/pull-3475
View File

@ -3,6 +3,7 @@ Enhancement: Allow limiting IO concurrency for local and SFTP backend
Restic did not support limiting the IO concurrency / number of connections for Restic did not support limiting the IO concurrency / number of connections for
accessing repositories stored using the local or SFTP backends. The number of accessing repositories stored using the local or SFTP backends. The number of
connections is now limited as for other backends, and can be configured via the connections is now limited as for other backends, and can be configured via the
the `-o local.connections=2` and `-o sftp.connections=5` options. the `-o local.connections=2` and `-o sftp.connections=5` options. This ensures
that restic does not overwhelm the backend with concurrent IO operations.
https://github.com/restic/restic/pull/3475 https://github.com/restic/restic/pull/3475

1
changelog/unreleased/pull-3680
View File

@ -5,3 +5,4 @@ features we're dropping support for Go 1.14, which means that restic now
requires at least Go 1.15 to build. requires at least Go 1.15 to build.
https://github.com/restic/restic/issues/3680 https://github.com/restic/restic/issues/3680
https://github.com/restic/restic/issues/3883

3
changelog/unreleased/pull-3772
View File

@ -1,7 +1,7 @@
Bugfix: Correctly rebuild index for legacy repositories Bugfix: Correctly rebuild index for legacy repositories
After running `rebuild-index` on a legacy repository containing mixed pack After running `rebuild-index` on a legacy repository containing mixed pack
files (that is, pack files with store both metadata and file data), `check` files (that is, pack files which store both metadata and file data), `check`
printed warnings like `pack 12345678 contained in several indexes: ...`. printed warnings like `pack 12345678 contained in several indexes: ...`.
This warning was not critical, but has now nonetheless been fixed by properly This warning was not critical, but has now nonetheless been fixed by properly
handling mixed pack files while rebuilding the index. handling mixed pack files while rebuilding the index.
@ -10,4 +10,5 @@ Running `prune` for such legacy repositories will also fix the warning by
reorganizing the pack files which caused it. reorganizing the pack files which caused it.
https://github.com/restic/restic/pull/3772 https://github.com/restic/restic/pull/3772
https://github.com/restic/restic/pull/3884
https://forum.restic.net/t/5044/13 https://forum.restic.net/t/5044/13