From 651fe3f396823d19af285e04139fbfc2a0cb3b9c Mon Sep 17 00:00:00 2001 From: alt Date: Fri, 4 Jun 2021 10:13:06 +0000 Subject: [PATCH] Added a comment --- ...ment_2_1dcf100a28991c664681d78ed4c12e39._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/distributed_borg/comment_2_1dcf100a28991c664681d78ed4c12e39._comment diff --git a/doc/forum/distributed_borg/comment_2_1dcf100a28991c664681d78ed4c12e39._comment b/doc/forum/distributed_borg/comment_2_1dcf100a28991c664681d78ed4c12e39._comment new file mode 100644 index 0000000000..205e2f2b83 --- /dev/null +++ b/doc/forum/distributed_borg/comment_2_1dcf100a28991c664681d78ed4c12e39._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="alt" + subject="comment 2" + date="2021-06-04T10:13:06Z" + content=""" +Leave it to the Grand Wizard himself :) + +With a few tweaks based on your explanation, this appears to be working smoothly. I think our issue was caused by attempting to connect repos that were individually initialized (i.e., with `git init`, `git annex init`, and `git annex initremote` on each workstation); by performing this initialization routine only on a single workstation, then following through with `git clone` and `git annex enableremote` on each additional workstation, the syncing works as expected. + +Thank you for your work and guidance! This is very exciting. + +The next thing to figure out is Borg repo mirroring to alleviate the overhead caused by Step 1(b) in the procedure above. Currently, the number of `borg create` operations each workstation must perform is multiplied by the number of Borg special remotes, which obviously doesn’t scale well. Ideally, a workstation could create an archive on a single server—say, the nearest available—offloading to the server the burden of creating archives on the remaining Borg repos. It sounds good in my head, but I struggle to find prior art for something like Borg-based swarms for eventual consistency. +"""]] -- 2.30.2