|
|
@@ -64,6 +64,8 @@ Description
|
|
|
|
|
|
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.
|
|
|
@@ -80,15 +82,6 @@ There is no risk of data loss by this.
|
|
|
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.
|
|
|
@@ -103,5 +96,5 @@ With --target the original archive is not replaced, instead a new archive is cre
|
|
|
|
|
|
When rechunking space usage can be substantial, expect at least the entire
|
|
|
deduplicated size of the archives using the previous chunker params.
|
|
|
-When recompressing approximately 1 % of the repository size or 512 MB
|
|
|
-(whichever is greater) of additional space is used.
|
|
|
+When recompressing expect approx. (throughput / checkpoint-interval) in space usage,
|
|
|
+assuming all chunks are recompressed.
|
Thomas Waldmann