forum/Two computer setup: "transfer" or "full backup" repository groups?git-annexhttp://git-annex.branchable.com/forum/Two_computer_setup__58_____34__transfer__34___or___34__full_backup__34___repository_groups__63__/git-annexikiwiki2016-03-12T16:58:09Zupdatehttp://git-annex.branchable.com/forum/Two_computer_setup__58_____34__transfer__34___or___34__full_backup__34___repository_groups__63__/comment_1_b8702892280447193e6e80be22a580a0/Blake2016-03-12T16:58:09Z2013-10-30T07:19:56Z
<p>It seems both Client-A and Client-B ARE actually syncing with this current setup. I think Client-B was just delayed due to the initial startup scan. So I guess at this point I am more or less asking if having both Client-A and Client-B have the remote repository being a "full backup" type is appropriate or if there is a better configuration that achieves what I am hoping to have.</p>
<p>Regards,
Blake</p>
comment 2http://git-annex.branchable.com/forum/Two_computer_setup__58_____34__transfer__34___or___34__full_backup__34___repository_groups__63__/comment_2_50cafde7e30b928480d1f142ddd763d2/joeyh.name2016-03-12T16:58:09Z2013-11-01T16:47:18Z
<p>git-annex keeps track of the repository group on a per repository basis. That is, if the repository on Server-A is a full backup, both Client-A and Client-B will consider it to be one, and use it appropriately. You can't have just Client-A think it's a full backup; this setting will be automatically synced to Client-B.</p>
<p>Your setup sounds ok, although you might need to set up a XMPP account in order for Client-A and Client-B to immediately message one-another when they have new changes to sync. Otherwise, they might only poll Server-A occasionally for changes.</p>