I've been using Vorta for backups on my GNU/Linux system with no problems creating, mounting, and restoring from archives.
I went with default options and see that my current back up profile uses "repokey-blake2" for encryption, fine. But how do I find out where they encryption keys are so I can back them up? I'd hate to lose those keys or not being able to access them if/when I want to restore on another device.
The are located in your repository config. A repository at /home/user/repository would have the config at /home/user/repository/config. This will be easier once a fix for https://github.com/borgbase/vorta/issues/304 is done. I am actually working on it https://github.com/borgbase/vorta/pull/599 but don't have time to finish it yet.
@samuel-w: thank you for getting back to me so quickly! 馃槂
I found the config file in my repository, just a few questions:
key so presumably that's the one Vorta uses to encrypt/decrypt my repository. If so, and since the config file resides with my repository, that means anyone who has access to the repository directory would have the means to encrypt/decrypt it, too?config for read/write access?Thanks! And looking forward to #304 and #599. Let me know if I can help test or something.
No, its a borg file. Vorta is just a frontend for borg, and it runs borg commands to do everything.
You need two things to decrypt a repository. The password and the key. If you lose one, then it is impossible to decrypt the data. That is why backing up the keyfile and knowing your password is important.
To copy a repository to a new location should just be copying it over, and setting BORG_RELOCATED_REPO_ACCESS_IS_OK if you are running borg from command line (Vorta automatically sets BORG_RELOCATED_REPO_ACCESS_IS_OK). Running borg restore or pressing restore in the Vorta UI will use the key automatically.
Got it, thanks! Makes sense.
Closing since it鈥檚 answered.