upstream/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2026-02-03 04:20:45 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

align docs

Browse source
This commit is contained in:
Michael Eischer 2025-11-23 17:47:46 +01:00
parent cf409b7c66
commit 7d08c9282a
2 changed files with 5 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
changelog/unreleased/issue-5453
View file

@ -1,12 +1,10 @@
Enhancement: `restic copy` can now spool packfiles across muliple snapshots
Enhancement: `copy` copies snapshots in batches
When using `restic copy` used to save all newly created packfiles when finishing one snapshot,
even when the actual packfile size was quite small. This applied particularly to
incremental backups, when there was only small changes between individual backups.
The `copy` command used to copy snapshots individually, even if this resulted in creating pack files
smaller than the target pack size. In particular, this resulted in many small files
when copying small incremental snapshots.
When using the new option `--batch`, `restic copy` now creates one large request list
which contains all blobs from all snapshots to be copied and then executes the
copy operation.
Now, `copy` copies multiple snapshots at once to avoid creating small files.
https://github.com/restic/restic/issues/5175
https://github.com/restic/restic/pull/5464

8
doc/045_working_with_repos.rst
View file

@ -216,14 +216,6 @@ example from a local to a remote repository, you can use the ``copy`` command:
snapshot 4e5d5487 of [/home/user/work] at 2020-05-01 22:44:07.012113 +0200 CEST by user@kasimir
skipping snapshot 4e5d5487, was already copied to snapshot 50eb62b7
In case you want to copy a repository which contains many backups with little changes
between ``restic backup`` runs, you can use the option ``--batch`` to make full use of
the ``--pack-size`` option. Newly created packfiles are saved when the ``copy``
operation for one snapshot finishes. The option ``--batch`` disregards these snapshot boundaries
and creates optimally filled packfiles. You can always always achieve the same effect
by running ``restic prune`` after a ``restic copy`` operation, but this involves the extra
``prune`` step.
The example command copies all snapshots from the source repository
``/srv/restic-repo`` to the destination repository ``/srv/restic-repo-copy``.
Snapshots which have previously been copied between repositories will