[Borgbackup] move borg repo including cache to new machine?

[devzero at web.de]

apparently, i found it was a serious bug in our backup script. 

sorry for the noise!





> Not sure why you mention the cache? It is client-side, so if you only
> moved the repo, the client side cache does not need moving at all.

for now, we do not have any borg installation remote, we do everything borg related on the backup server only/itself.

we first pull everthing from the remote servers via rsync to a local staging dir and then let borg run across that staging
area afterwards.

sure, we need extra space, but what we want is rotating, space saving, deduplicated "incremental backup forever".

so having a rsync copy + borg repo for each of our backed up servers is ok and worth the extra diskspace...

regards
roland


> Gesendet: Freitag, 28. Dezember 2018 um 17:28 Uhr
> Von: "Thomas Waldmann" <tw at waldmann-edv.de>
> An: borgbackup at python.org
> Betreff: Re: [Borgbackup] move borg repo including cache to new machine?
>
> > i need to move a larger borg-repo to a new machine.
> > 
> > apparently, after moving everything (cache dir, repo-dir and staging-dir which is rsynced) ,  borg is re-chunking everything and creating a new cache for existing source location.
> > 
> > does somebody know why and how to avoid this?
> 
> If you moved the repo "as is" and everything else stayed "as is", it
> should not do that.
> 
> Not sure why you mention the cache? It is client-side, so if you only
> moved the repo, the client side cache does not need moving at all.
> 
> Also, what do you mean with staging-dir?
> 
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>