mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-26 01:37:20 +00:00
Code Issues Releases Wiki Activity
borg/docs/usage/upgrade.rst.inc

73 lines
3 KiB
PHP
Raw Normal View History

commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
.. _borg_upgrade:
borg upgrade
------------
::
ran build_usage
2015-12-08 09:21:20 +00:00
usage: borg upgrade [-h] [-v] [--debug] [--lock-wait N] [--show-rc]
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
[--no-files-cache] [--umask M] [--remote-path PATH] [-p]
[-n] [-i]
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
[REPOSITORY]
upgrade a repository from a previous version
positional arguments:
ran build_usage
2015-12-08 09:21:20 +00:00
REPOSITORY path to the repository to be upgraded
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
optional arguments:
ran build_usage
2015-12-08 09:21:20 +00:00
-h, --help show this help message and exit
-v, --verbose, --info
enable informative (verbose) output, work on log level
INFO
--debug enable debug output, work on log level DEBUG
--lock-wait N wait for the lock, but max. N seconds (default: 1).
--show-rc show/log the return code (rc)
--no-files-cache do not load/update the file metadata cache used to
detect unchanged files
--umask M set umask to M (local and remote, default: 0077)
--remote-path PATH set remote path to executable (default: "borg")
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
-p, --progress show progress display while upgrading the repository
ran build_usage
2015-12-08 09:21:20 +00:00
-n, --dry-run do not change repository
-i, --inplace rewrite repository in place, with no chance of going
back to older versions of the repository.
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
Description
~~~~~~~~~~~
docs: borg upgrade also handles borg 0.xx -> 1.0
2016-02-07 18:23:06 +00:00
Upgrade an existing Borg repository.
This currently supports converting an Attic repository to Borg and also
helps with converting Borg 0.xx to 1.0.
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
borg upgrade: add to docs that only LOCAL repos are supported
2016-02-07 20:08:20 +00:00
Currently, only LOCAL repositories can be upgraded (issue #465).
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
It will change the magic strings in the repository's segments
to match the new Borg magic strings. The keyfiles found in
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
$ATTIC_KEYS_DIR or ~/.attic/keys/ will also be converted and
run build_usage
2016-02-07 13:50:39 +00:00
copied to $BORG_KEYS_DIR or ~/.config/borg/keys.
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
The cache files are converted, from $ATTIC_CACHE_DIR or
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
~/.cache/attic to $BORG_CACHE_DIR or ~/.cache/borg, but the
cache layout between Borg and Attic changed, so it is possible
the first backup after the conversion takes longer than expected
due to the cache resync.
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
Upgrade should be able to resume if interrupted, although it
will still iterate over all segments. If you want to start
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
from scratch, use `borg delete` over the copied repository to
make sure the cache files are also removed:
borg delete borg
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
Unless ``--inplace`` is specified, the upgrade process first
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
creates a backup copy of the repository, in
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
REPOSITORY.upgrade-DATETIME, using hardlinks. This takes
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
longer than in place upgrades, but is much safer and gives
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
progress information (as opposed to ``cp -al``). Once you are
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
satisfied with the conversion, you can safely destroy the
backup copy.
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
WARNING: Running the upgrade in place will make the current
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
copy unusable with older version, with no way of going back
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
to previous versions. This can PERMANENTLY DAMAGE YOUR
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 15:42:16 +00:00
REPOSITORY! Attic CAN NOT READ BORG REPOSITORIES, as the
ran setup.py build_usage
2016-01-23 19:54:20 +00:00
magic strings have changed. You have been warned.
Reference in a new issue Copy permalink