mirror of
https://github.com/borgbackup/borg.git
synced 2025-01-03 05:35:58 +00:00
Clarification of keyfile backup
Proposed clarification in response to my confusion in https://github.com/borgbackup/borg/issues/6204.
This commit is contained in:
parent
a65f298477
commit
578fbe087e
1 changed files with 6 additions and 4 deletions
10
docs/faq.rst
10
docs/faq.rst
|
@ -514,10 +514,12 @@ The Borg config directory has content that you should take care of:
|
|||
recovered.
|
||||
|
||||
``keys`` subdirectory
|
||||
All your borg keyfile keys are stored in this directory. Please note that
|
||||
borg repokey keys are stored inside the repository. You MUST make sure to have an
|
||||
independent backup of these keyfiles, otherwise you cannot access your backups anymore if you lose
|
||||
them. You also MUST keep these files secret; everyone who gains access to your repository and has
|
||||
All your borg keyfile keys are stored in this directory. Please note that borg repokey keys are stored inside the repository.
|
||||
|
||||
If you use keyfile encryption, you MUST make sure to have an independent backup of these keyfiles, otherwise you cannot access your backups anymore if you lose
|
||||
them. If you use repokey encryption it is also highly recommended that you backup the keyfiles in case the originals (stored within the repository) get damaged. The best way to create a backup is using the ``borg key export`` command.
|
||||
|
||||
You also MUST keep these files secret; everyone who gains access to your repository and has
|
||||
the corresponding keyfile (and the key passphrase) can extract it.
|
||||
|
||||
Make sure that only you have access to the Borg config directory.
|
||||
|
|
Loading…
Reference in a new issue