[Borgbackup] conversion from attic to borg
Antoine Beaupré
anarcat at debian.org
Fri Dec 4 10:45:20 EST 2015
On 2015-12-04 09:46:46, Dan Christensen wrote:
> Antoine Beaupré <anarcat at debian.org> writes:
>
>> On 2015-12-04 09:08:55, Dan Christensen wrote:
>>
>>> If several client machines access the same repo, do I run it for
>>> each of them, or just one of them?
>>
>> I didn't think of that: i would assume it's enough to run it once.
>
> I read that the upgrade process upgrades the cache as well, so I guess
> the other clients that access the same repo won't get their caches
> upgraded, and will have to do a full rebuild instead?
Ah, true, i forgot about those. Then I guess you *could* run the upgrade
process multiple times, once per client. The server side is
"idempotent", that is: it can be run multiple times without ill
effects, and it will skip work already done.
>>> And presumably it's faster if I run it directly on the machine storing
>>> the repo?
>>
>> I would assume so as well. In fact, I don't know if it's possible at all
>> to run it remotely.
>
> In many use cases, the repo will never have been accessed directly from
> the machine storing the repo, so there will be no existing cache on that
> machine. Presumably that's not a problem, and one could use the
> --no-files-cache option?
I don't think `--no-files-cache` is a valid option for the upgrade
command, but it could be added!
If you mean on the `create` command, then yes, you could use that
option, but borg will re-create the missing cache anyways...
a.
--
Au nom de l'état, la force s'appelle droit.
Au main de l'individu, elle s'appelle crime.
- Max Stirner
More information about the Borgbackup
mailing list