[Borgbackup] Multi-machine backup when there's some data overlap

[Oon-Ee Ng]

I read that, and figured it meant "no you can't do that directly" since
having to rebuild indices seems like it would make backups take
significantly longer.

Would there be a clever way of sharing the indice/cache which would help
with that?

On Tue, 16 Oct 2018, 9:18 pm Zack Coffey, <clickwir at gmail.com> wrote:

> https://borgbackup.readthedocs.io/en/stable/faq.html
>
> That question is the very first answer in the FAQ.
>
> The answer is basically "yes, but..."
>
> Each machine is responsible for taking care of the whole repo as if it
> were it's own. So it needs to sync the whole thing, take care of everything
> and leave it all in a good state. Otherwise the next backup client is going
> to have trouble. Oh, and only 1 can run at a time.
>
> If all of those are not a concern and dedupe is a higher priority, then
> yes they can all backup to 1 repo. Otherwise, individual repos is wiser.
>
> On Tue, Oct 16, 2018 at 1:14 AM Oon-Ee Ng <ngoonee.talk at gmail.com> wrote:
>
>> Apologies in advance if I get terminology wrong, I've used rsnapshot for
>> a decade or more and am only now looking to upgrade my backup process.
>>
>> Having said that, what's the best way to approach multi-machine backup?
>> Obviously the most straightforward way is to initialize at least one borg
>> backup per machine. However if I read that correctly this will create
>> isolated repositories, which cannot take advantage of any data overlap.
>>
>> Just to avoid this being an XY problem, my core use case is having
>> multiple computers (Linux and Windows via cygwin) backing up to a single
>> backup host using borgbackup. Some of these machines have duplicated data
>> (especially in terms of photos/videos, since these are personal/family
>> machines), so there should be significant space savings from being keeping
>> them in one repository, if that is at all possible.
>>
>> Thanks in advace!
>> _______________________________________________
>> 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/20181016/ee1d7de7/attachment-0001.html>