[Borgbackup] Can rsynced repos be used independently after the initial rsync?

[Oon-Ee Ng]

Oh, how does that affect encryption or authentication? Is it just the fact
that both repos use the exact same encryption key? Based on my (probably
flawed) understanding that doesn't really invalidate security?

On Sun, 28 Oct 2018, 12:50 am Marian Beermann, <public at enkore.de> wrote:

> This can work, if you change the repository ID in the repository's
> config file in the two "forked" repos.
>
> Realize that all encryption / authentication offered by Borg is
> completely useless when used like this.
>
> Cheers, Marian
>
> Am 27.10.18 um 17:06 schrieb Oon-Ee Ng:
> > The FAQ question on this says that syncing of the repo can be done using
> > any tool (including rsync) as long as no backup is run to the repo while
> > it's being synced.
> >
> > However it also notes that as a long-term solution this leaves much to
> > be desired, since anything corrupting the first repo would be synced
> > over and result in a corrupted second repo. The recommendation given is
> > to keep backups separate (run borg create twice, once to each).
> >
> > Given I have a relatively large repo relative to my network connections
> > throughput, and I want to have one borg repo on a local network backup
> > machine and one on a remote backup machine, I was thinking about:-
> >
> > 1. Running rsync (would likely take slightly under a day) of the repo
> > from local backup machine to remote.
> >
> > 2. Independently using both repos after rsync is successful. That means
> > my backup script would call borg create repo1:/path followed by borg
> > create repo2:/path
> >
> > Would this work, and does it have any downsides?
> >
> > _______________________________________________
> > Borgbackup mailing list
> > Borgbackup at python.org
> > https://mail.python.org/mailman/listinfo/borgbackup
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20181028/e48afdd7/attachment.html>