mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-23 14:41:43 +00:00
Merge pull request #1744 from ThomasWaldmann/improve-append-only-docs
add clarification about append-only mode, fixes #1689
This commit is contained in:
commit
1cd48535e4
1 changed files with 6 additions and 1 deletions
|
@ -800,9 +800,14 @@ That's all to it.
|
||||||
Drawbacks
|
Drawbacks
|
||||||
+++++++++
|
+++++++++
|
||||||
|
|
||||||
As data is only appended, and nothing deleted, commands like ``prune`` or ``delete``
|
As data is only appended, and nothing removed, commands like ``prune`` or ``delete``
|
||||||
won't free disk space, they merely tag data as deleted in a new transaction.
|
won't free disk space, they merely tag data as deleted in a new transaction.
|
||||||
|
|
||||||
|
Be aware that as soon as you write to the repo in non-append-only mode (e.g. prune,
|
||||||
|
delete or create archives from an admin machine), it will remove the deleted objects
|
||||||
|
permanently (including the ones that were already marked as deleted, but not removed,
|
||||||
|
in append-only mode).
|
||||||
|
|
||||||
Note that you can go back-and-forth between normal and append-only operation by editing
|
Note that you can go back-and-forth between normal and append-only operation by editing
|
||||||
the configuration file, it's not a "one way trip".
|
the configuration file, it's not a "one way trip".
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue