mirror of
https://github.com/restic/restic.git
synced 2024-09-08 04:19:31 +02:00
replace all uses of target in relation to backup
This commit is contained in:
parent
0ddff92323
commit
729e009485
@ -603,7 +603,7 @@ restic users. The changes are ordered by importance.
|
||||
* Enhancement #3941: Support `--group-by` for backup parent selection
|
||||
|
||||
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.
|
||||
|
||||
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/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
|
||||
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
|
||||
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.
|
||||
|
@ -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
|
||||
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)
|
||||
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
|
||||
|
@ -1,7 +1,7 @@
|
||||
Enhancement: Support `--group-by` for backup parent selection
|
||||
|
||||
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
|
||||
read all files again.
|
||||
|
||||
|
@ -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
|
||||
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
|
||||
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
|
||||
|
@ -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)
|
||||
// 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.
|
||||
node, err = arch.nodeFromFileInfo(snPath, atree.FileInfoPath, fi, true)
|
||||
if err != nil {
|
||||
|
Loading…
Reference in New Issue
Block a user