mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

question about annotating availability in the snapshot

Browse source
This commit is contained in:
yarikoptic 2023-05-19 14:36:46 +00:00 • committed by admin
parent d73467ebf7
commit ea7a904c0d
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/make_a_snapshot_backup_into_a___34__remote__34__.mdwn Normal file
View file

@ -0,0 +1,13 @@
I use BTRFS, so have CoW and snapshots of the entire system which I transfer regularly to a backup box.
Before dropping some content in the "working" instance of the repository, I thought to note availability of the keys in some backup snapshot(s) on a backup server.
The difficulty is that those all would have the same git-annex UUID (since they are snapshots of the same "working one"), and internally git-annex would have availability marked based on that UUID so I guess that would not work as is.
So I am thinking (didn't try) to do the following dance:
- make a "read-write" copy of the entire backup snapshot
- `git annex init` the backup copy inthat snapshot to cause regeneration of UUID
- run `git annex fsck` so git-annex annotates availability of those keys with that new UUID
- make read-only snapshot of the read-write snapshot
- add that read-only snapshot host:/path as a remote to the "working" instance.
Would that be "optimal" way or may be there is some feature of git-annex which would allow me to avoid the dance?