key_export.rst.inc 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  1. .. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
  2. .. _borg_key_export:
  3. borg key export
  4. ---------------
  5. ::
  6. usage: borg key export [-h] [--critical] [--error] [--warning] [--info]
  7. [--debug] [--lock-wait N] [--show-rc]
  8. [--no-files-cache] [--umask M] [--remote-path PATH]
  9. [--paper] [--qr-html]
  10. [REPOSITORY] [PATH]
  11. Export the repository key for backup
  12. positional arguments:
  13. REPOSITORY
  14. PATH where to store the backup
  15. optional arguments:
  16. -h, --help show this help message and exit
  17. --critical work on log level CRITICAL
  18. --error work on log level ERROR
  19. --warning work on log level WARNING (default)
  20. --info, -v, --verbose
  21. work on log level INFO
  22. --debug work on log level DEBUG
  23. --lock-wait N wait for the lock, but max. N seconds (default: 1).
  24. --show-rc show/log the return code (rc)
  25. --no-files-cache do not load/update the file metadata cache used to
  26. detect unchanged files
  27. --umask M set umask to M (local and remote, default: 0077)
  28. --remote-path PATH use PATH as borg executable on the remote (default:
  29. "borg")
  30. --paper Create an export suitable for printing and later type-
  31. in
  32. --qr-html Create an html file suitable for printing and later
  33. type-in or qr scan
  34. Description
  35. ~~~~~~~~~~~
  36. If repository encryption is used, the repository is inaccessible
  37. without the key. This command allows to backup this essential key.
  38. Note that the backup produced does not include the passphrase itself
  39. (i.e. the exported key stays encrypted). In order to regain access to a
  40. repository, one needs both the exported key and the original passphrase.
  41. There are two backup formats. The normal backup format is suitable for
  42. digital storage as a file. The ``--paper`` backup format is optimized
  43. for printing and typing in while importing, with per line checks to
  44. reduce problems with manual input.
  45. For repositories using keyfile encryption the key is saved locally
  46. on the system that is capable of doing backups. To guard against loss
  47. of this key, the key needs to be backed up independently of the main
  48. data backup.
  49. For repositories using the repokey encryption the key is saved in the
  50. repository in the config file. A backup is thus not strictly needed,
  51. but guards against the repository becoming inaccessible if the file
  52. is damaged for some reason.