Added a comment: Can git-annex be used to quasi-realtime replication?
authorshodanshok@8c8405b6944c211be7dec8ae8fccde70adc19027 <shodanshok@web>
Mon, 16 Jan 2017 17:41:07 +0000 (17:41 +0000)
committeradmin <admin@branchable.com>
Mon, 16 Jan 2017 17:41:07 +0000 (17:41 +0000)
doc/not/comment_16_d2ae9613ad81508dbda6ed425d441ccb._comment [new file with mode: 0644]

diff --git a/doc/not/comment_16_d2ae9613ad81508dbda6ed425d441ccb._comment b/doc/not/comment_16_d2ae9613ad81508dbda6ed425d441ccb._comment
new file mode 100644 (file)
index 0000000..1955a94
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="shodanshok@8c8405b6944c211be7dec8ae8fccde70adc19027"
+ nickname="shodanshok"
+ avatar="http://cdn.libravatar.org/avatar/8b4dd6a9f2396b788ca18f3690609ad3"
+ subject="Can git-annex be used to quasi-realtime replication?"
+ date="2017-01-16T17:41:07Z"
+ content="""
+Suppose I have two Samba fileservers in two different locations. Can I use git-annex in thin mode + git-annex assistant to automatically synchronize these two fileserver? Specifically, I am trying to understand if:
+
+1) git-annex preserve owner/group ID and POSIX ACLs;
+2) it can efficiently manage very large number of file/directory (500K+ files)
+3) it can be used alongside inotify to efficiently transfer only changed files
+
+One last thing: I which sense git-annex is not like Unison? It seems it can be configured to have very similar functionality. I am missing something?
+
+Thank you all.
+"""]]