From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to synchronise between 2 locations
Date: Thu, 28 Mar 2024 07:32:21 +0100 [thread overview]
Message-ID: <2192508.irdbgypaU6@persephone> (raw)
In-Reply-To: <ZgR5Zp_zgSJjz3mh@schatulle>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
On Wednesday, 27 March 2024 20:54:14 CET Frank Steinmetzger wrote:
> Am Wed, Mar 27, 2024 at 03:42:07PM -0400 schrieb Matt Connell:
> > On Wed, 2024-03-27 at 19:58 +0100, J. Roeleveld wrote:
> > > Hi all,
> > >
> > > I am looking for a way to synchronise a filesystem between 2 servers.
> > > Changes can occur on both sides which means I need to have it
> > > synchronise in both directions.
> > >
> > > Does anyone have any thoughts on this?
> > >
> > > Also, both servers are connected using a slow VPN link, which is why
> > > I can't simply access files on the remote server.
> >
> > I've been using syncthing for years and am extremely pleased with it.
> > It works so well that I sometimes forget that its there, truly in the
> > It Just Works category of software.
>
> Syncthing is also a good idea. The major difference: syncthing is a
> permanently running daemon, so changes are synced very fast (the interval is
> configurable, IIRC). OTOH, Unison is run individually by you. That’s why I
> prefer the latter: in case I broke some file on my machine, I can get it
> back from another machine without having to break out the backup disk
> (which may not even have what I need because my backup interval is too
> big).
I had a quick look and it seems to depend on systems running outside of my
network. Can it be used without any link to a "centralised" server?
--
Joost
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-28 6:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 18:58 [gentoo-user] How to synchronise between 2 locations J. Roeleveld
2024-03-27 19:08 ` Mark Knecht
2024-03-28 6:28 ` J. Roeleveld
2024-03-28 13:51 ` [gentoo-user] " Grant Edwards
2024-03-28 15:27 ` J. Roeleveld
2024-03-27 19:18 ` [gentoo-user] " ralfconn
2024-03-27 19:37 ` Frank Steinmetzger
2024-03-28 0:08 ` Alarig Le Lay
2024-03-29 11:24 ` Frank Steinmetzger
2024-03-28 6:30 ` J. Roeleveld
2024-03-28 16:33 ` ralfconn
2024-03-29 11:27 ` Frank Steinmetzger
2024-03-27 19:42 ` Matt Connell
2024-03-27 19:54 ` Frank Steinmetzger
2024-03-27 19:59 ` Matt Connell
2024-03-27 21:34 ` Frank Steinmetzger
2024-03-27 20:12 ` tastytea
2024-03-28 6:32 ` J. Roeleveld [this message]
2024-03-28 10:00 ` tastytea
2024-03-29 2:26 ` Grant Taylor
2024-03-29 11:32 ` Frank Steinmetzger
2024-03-29 13:32 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2192508.irdbgypaU6@persephone \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox