mirror of
https://github.com/borgbackup/borg.git
synced 2025-01-01 04:37:34 +00:00
clarify same-filesystem requirement for borg upgrade, fixes #2083
(cherry picked from commit fe746fa594
)
This commit is contained in:
parent
e0d967aeb7
commit
e7ae63f1f6
1 changed files with 7 additions and 7 deletions
|
@ -3499,13 +3499,13 @@ def define_archive_filters_group(subparser, *, sort_by=True, first_last=True):
|
|||
|
||||
borg delete borg
|
||||
|
||||
Unless ``--inplace`` is specified, the upgrade process first
|
||||
creates a backup copy of the repository, in
|
||||
REPOSITORY.before-upgrade-DATETIME, using hardlinks. This takes
|
||||
longer than in place upgrades, but is much safer and gives
|
||||
progress information (as opposed to ``cp -al``). Once you are
|
||||
satisfied with the conversion, you can safely destroy the
|
||||
backup copy.
|
||||
Unless ``--inplace`` is specified, the upgrade process first creates a backup
|
||||
copy of the repository, in REPOSITORY.before-upgrade-DATETIME, using hardlinks.
|
||||
This requires that the repository and its parent directory reside on same
|
||||
filesystem so the hardlink copy can work.
|
||||
This takes longer than in place upgrades, but is much safer and gives
|
||||
progress information (as opposed to ``cp -al``). Once you are satisfied
|
||||
with the conversion, you can safely destroy the backup copy.
|
||||
|
||||
WARNING: Running the upgrade in place will make the current
|
||||
copy unusable with older version, with no way of going back
|
||||
|
|
Loading…
Reference in a new issue