summaryrefslogtreecommitdiff
path: root/doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_1_c2f7542ac9a4c423c5ae06c16d42a24f._comment
blob: b8c9d33c2ab03c27a67d6a3179fabbeefb200002 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2015-12-11T14:42:32Z"
 content="""
That's what's "special" about special remotes vs regular git remotes: They
only store the content of annexed files and not the git repository. Back up
the git repository separately (and your gpg key if it's being used, and the
credentials if you didn't use embedcreds=yes)

To use your backup, you can make a clone of the backed up git repository and
use `git annex enableremote` to enable it to use the special remote.

See [[design/encryption]] for details of how the encryption is implemented.
I've seen people follow that and manually use the data from the git repo to
decrypt files, but I don't have a pointer to an example at the moment.
"""]]