[Borgbackup] bypassing "Cache newer than repo" error

[Marian Beermann]

Hi sitaram

This sounds like you created one repository and copied it to multiple
drives/locations?

In that case this is to be expected - Borg distinguishes different
repositories by their ID, which is independent of the location and would
be the same for these copied repositories.

You can change the repository ID in the "config" file of the repository
(it's hex, keep it the same length), which separates the repositories.

Note: for encrypted repositories it's a very unsafe thing to have
multiple independently updated copies of a repository; if they diverge
(minutely different contents) and an attacker gains access to more than
one copy, the privacy of the repository contents may be compromised.

Cheers, Marian

FAQs:
http://borgbackup.readthedocs.io/en/stable/faq.html#can-i-copy-or-synchronize-my-repo-to-another-location

On 08.10.2016 13:06, Sitaram Chamarty wrote:
> Hi
>
> Some of the directories are backed up to two (in one case three)
> different external (USB) hard disks.  When I finish with the first USB
> drive, unmount it, and mount the next one and try the backup, borg tells
> me the cache is newer.
>
> I could not find anything about how to bypass this in the docs.  I have
> now created a complicated system of separately maintaining the cache
> directories for each external disk (labelled in some way that correlates
> with the physical disk in question) and manually shuffle them around.
>
> Any pointers would be appreciated.
>
> regards
> sitaram
>
> PS: Yes removing ~/.cache/borg works and is generally harmless.  But
> that makes ALL the files show up as "A ...", whereas I like to eyeball
> the list to see if something got updated which I did not expec to be
> updated based on what I have been working on since the last backup.
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>