mirror/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2024-12-22 07:43:03 +00:00
Code Issues Releases Wiki Activity

replace all uses of target in relation to backup

Browse source
This commit is contained in:
Michael Eischer 2024-07-24 19:40:53 +02:00
parent 0ddff92323
commit 729e009485
5 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
CHANGELOG.md
View file

@ -603,7 +603,7 @@ restic users. The changes are ordered by importance.
* Enhancement #3941: Support `--group-by` for backup parent selection * Enhancement #3941: Support `--group-by` for backup parent selection
Previously, the `backup` command by default selected the parent snapshot based on the Previously, the `backup` command by default selected the parent snapshot based on the
hostname and the backup targets. When the backup path list changed, the `backup` command was hostname and the backup paths. When the backup path list changed, the `backup` command was
unable to determine a suitable parent snapshot and had to read all files again. unable to determine a suitable parent snapshot and had to read all files again.
The new `--group-by` option for the `backup` command allows filtering snapshots for the The new `--group-by` option for the `backup` command allows filtering snapshots for the
@ -2575,10 +2575,10 @@ restic users. The changes are ordered by importance.
https://github.com/restic/restic/issues/3166 https://github.com/restic/restic/issues/3166
https://github.com/restic/restic/pull/3207 https://github.com/restic/restic/pull/3207
* Bugfix #3232: Correct statistics for overlapping targets * Bugfix #3232: Correct statistics for overlapping backup sources
A user reported that restic's statistics and progress information during backup was not A user reported that restic's statistics and progress information during backup was not
correctly calculated when the backup targets (files/dirs to save) overlap. For example, correctly calculated when the backup sources (files/dirs to save) overlap. For example,
consider a directory `foo` which contains (among others) a file `foo/bar`. When `restic consider a directory `foo` which contains (among others) a file `foo/bar`. When `restic
backup foo foo/bar` was run, restic counted the size of the file `foo/bar` twice, so the backup foo foo/bar` was run, restic counted the size of the file `foo/bar` twice, so the
completeness percentage as well as the number of files was wrong. This is now corrected. completeness percentage as well as the number of files was wrong. This is now corrected.

4
changelog/0.12.0_2021-02-14/issue-3232
View file

@ -1,7 +1,7 @@
Bugfix: Correct statistics for overlapping targets Bugfix: Correct statistics for overlapping backup sources
A user reported that restic's statistics and progress information during backup A user reported that restic's statistics and progress information during backup
was not correctly calculated when the backup targets (files/dirs to save) was not correctly calculated when the backup sources (files/dirs to save)
overlap. For example, consider a directory `foo` which contains (among others) overlap. For example, consider a directory `foo` which contains (among others)
a file `foo/bar`. When `restic backup foo foo/bar` was run, restic counted the a file `foo/bar`. When `restic backup foo foo/bar` was run, restic counted the
size of the file `foo/bar` twice, so the completeness percentage as well as the size of the file `foo/bar` twice, so the completeness percentage as well as the

2
changelog/0.16.0_2023-07-31/issue-3941
View file

@ -1,7 +1,7 @@
Enhancement: Support `--group-by` for backup parent selection Enhancement: Support `--group-by` for backup parent selection
Previously, the `backup` command by default selected the parent snapshot based Previously, the `backup` command by default selected the parent snapshot based
on the hostname and the backup targets. When the backup path list changed, the on the hostname and the backup paths. When the backup path list changed, the
`backup` command was unable to determine a suitable parent snapshot and had to `backup` command was unable to determine a suitable parent snapshot and had to
read all files again. read all files again.

2
doc/040_backup.rst
View file

@ -239,7 +239,7 @@ By default, restic always creates a new snapshot even if nothing has changed
compared to the parent snapshot. To omit the creation of a new snapshot in this compared to the parent snapshot. To omit the creation of a new snapshot in this
case, specify the ``--skip-if-unchanged`` option. case, specify the ``--skip-if-unchanged`` option.
Note that when using absolute paths to specify the backup target, then also Note that when using absolute paths to specify the backup source, then also
changes to the parent folders result in a changed snapshot. For example, a backup changes to the parent folders result in a changed snapshot. For example, a backup
of ``/home/user/work`` will create a new snapshot if the metadata of either of ``/home/user/work`` will create a new snapshot if the metadata of either
``/``, ``/home`` or ``/home/user`` change. To avoid this problem run restic from ``/``, ``/home`` or ``/home/user`` change. To avoid this problem run restic from

2
internal/archiver/archiver.go
View file

@ -634,7 +634,7 @@ func (arch *Archiver) saveTree(ctx context.Context, snPath string, atree *Tree,
} }
debug.Log("%v, dir node data loaded from %v", snPath, atree.FileInfoPath) debug.Log("%v, dir node data loaded from %v", snPath, atree.FileInfoPath)
// in some cases reading xattrs for directories above the backup target is not allowed // in some cases reading xattrs for directories above the backup source is not allowed
// thus ignore errors for such folders. // thus ignore errors for such folders.
node, err = arch.nodeFromFileInfo(snPath, atree.FileInfoPath, fi, true) node, err = arch.nodeFromFileInfo(snPath, atree.FileInfoPath, fi, true)
if err != nil { if err != nil {