borg appendonly config
This commit is contained in:
parent
0990d74574
commit
b16e6fb4e6
3 changed files with 35 additions and 40 deletions
|
@ -6,6 +6,13 @@ files in this special remote. You store files by using borg as usual, to
|
|||
back up the git-annex repository. Then `git-annex sync` will learn about
|
||||
the annexed files that are stored in the borg repository.
|
||||
|
||||
## setup example
|
||||
|
||||
# borg init --encryption=keyfile /path/to/borgrepo
|
||||
# git annex initremote borg type=borg borgrepo=/path/to/borgrepo
|
||||
# borg create /path/to/borgrepo `pwd`::{now}
|
||||
# git annex sync borg
|
||||
|
||||
## configuration
|
||||
|
||||
These parameters can be passed to `git annex initremote` to configure the
|
||||
|
@ -22,9 +29,15 @@ remote:
|
|||
repository that belong to unrelated git-annex repositories. It can also
|
||||
make syncing faster.
|
||||
|
||||
## setup example
|
||||
* `appendonly` - You could use borg to delete content from the
|
||||
repository at any time, so this defaults to "no", which
|
||||
makes the remote be untrusted. If you set to "yes", you must
|
||||
take care to avoid using commands like `borg delete` and
|
||||
`borg prune` with the borg repository.
|
||||
|
||||
# borg init --encryption=keyfile /path/to/borgrepo
|
||||
# git annex initremote borg type=borg borgrepo=/path/to/borgrepo
|
||||
# borg create /path/to/borgrepo `pwd`::{now}
|
||||
# git annex sync borg
|
||||
## avoid archive name reuse
|
||||
|
||||
Borg repositories contain archives, and git-annex assumes that, once
|
||||
created, the content of an archive does not change. So if you delete an
|
||||
archive and then create a new archive with the same name, it will confuse
|
||||
git-annex about what is contained in the borg repository.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue