mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-23 14:41:43 +00:00
recreate: update --help
This commit is contained in:
parent
c1ccad82c3
commit
c6f0969352
1 changed files with 2 additions and 9 deletions
|
@ -2355,6 +2355,8 @@ def build_parser(self, prog=None):
|
|||
recreate_epilog = textwrap.dedent("""
|
||||
Recreate the contents of existing archives.
|
||||
|
||||
This is an *experimental* feature. Do *not* use this on your only backup.
|
||||
|
||||
--exclude, --exclude-from and PATH have the exact same semantics
|
||||
as in "borg create". If PATHs are specified the resulting archive
|
||||
will only contain files from these PATHs.
|
||||
|
@ -2371,15 +2373,6 @@ def build_parser(self, prog=None):
|
|||
used to have upgraded Borg 0.xx or Attic archives deduplicate with
|
||||
Borg 1.x archives.
|
||||
|
||||
borg recreate is signal safe. Send either SIGINT (Ctrl-C on most terminals) or
|
||||
SIGTERM to request termination.
|
||||
|
||||
Use the *exact same* command line to resume the operation later - changing excludes
|
||||
or paths will lead to inconsistencies (changed excludes will only apply to newly
|
||||
processed files/dirs). Changing compression leads to incorrect size information
|
||||
(which does not cause any data loss, but can be misleading).
|
||||
Changing chunker params between invocations might lead to data loss.
|
||||
|
||||
USE WITH CAUTION.
|
||||
Depending on the PATHs and patterns given, recreate can be used to permanently
|
||||
delete files from archives.
|
||||
|
|
Loading…
Reference in a new issue