forum/Distributing data to a set of drivesgit-annexhttp://git-annex.branchable.com/forum/Distributing_data_to_a_set_of_drives/git-annexikiwiki2014-05-17T17:00:19Zcomment 1http://git-annex.branchable.com/forum/Distributing_data_to_a_set_of_drives/comment_1_f1fa72879f4e1db13bf59dea33c91624/Adam2014-05-08T16:56:34Z2014-05-08T16:56:34Z
I recommend rewriting your comment. Use paragraphs and be more clear and specific.
comment 2http://git-annex.branchable.com/forum/Distributing_data_to_a_set_of_drives/comment_2_e13b4e5c1e6f1f503f93d521b504d5c1/joeyh.name2014-05-17T17:00:19Z2014-05-17T17:00:19Z
<p>git-annex doesn't allow bonding repositories like that, but it does have repository groups which can accomplish the same thing.</p>
<p>For example, if you put B C and D into the archive group, and set the <a href="http://git-annex.branchable.com/forum/preferred_content/">preferred content</a> expression to "standard", then each repository will only want files that have not yet reached some other archive repository.</p>
<p>Or, you can make up your own group name, like "BCD" and set the preferred content of each repository to something like "not (copies=BCD:2)" -- and now it will try to have 2 copies of each file on one of the drives.</p>
<p>Once it's configured, using either the git-annex assistant, or <code>git annex sync --content</code> will copy files around according to the configuration.</p>
<p>This will tend to fill up the first drive, or the first 2 drives, and only use subsequent drives if files don't fit on the first drive. You can use <span class="createlink"><a href="http://git-annex.branchable.com/ikiwiki.cgi?do=create&from=forum%2FDistributing_data_to_a_set_of_drives%2Fcomment_2_e13b4e5c1e6f1f503f93d521b504d5c1&page=cost" rel="nofollow">?</a>cost</span> settings to control which drives files are put on.</p>