File: comment_3_f4e3f28db005301adeef7ccd2c9998fb._comment

package info (click to toggle)
git-annex 10.20230126-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 69,344 kB
  • sloc: haskell: 74,654; javascript: 9,103; sh: 1,304; makefile: 203; perl: 136; ansic: 44
file content (18 lines) | stat: -rw-r--r-- 733 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo"
 nickname="Marek"
 subject="I should have thought of this"
 date="2013-04-30T19:55:19Z"
 content="""
Thanks joey, I thought of the object storage just yesterday and that the drive where it resides needs to be the big one. 

I think that I will do it as you described with one addition:

I set up the git-annex repository on my big drive. Lets call that BIG.
Then I set up another on the smaller drive (or raid) and set both to sync. Lets call that RAID.

BUT: Can I use num copies to tell BIG to only sync files in certain directories to RAID. Or will syncing sync everything regardless?

Thanks for your help

"""]]