I know there are a million questions and issues logged about >1 client backing up to the same remote repository. But I’ve been unable to find anything about one client backing up to >1 remote repo at the same time (each in their own b2 buckets).
Here’s the story:
I had a backup going that was getting unreasonably large, due to having no exclude rules. So things like VM images and backups, ISO images etc. were in it. (It’s actually a backup of a mirror; the script that creates maintains that mirror is supposed to exclude all that stuff, but obviously not well.)
So I decided to start over with a new bucket. (I’ll delete the old bucket later.)
On top of that, I accidentally killed the first backup job uncleanly. So I figured that I’d check/repair that repo. (Even though it will eventually be redundant and deleted, with fires closing in it seems prudent to not throw anything away just yet and in fact make sure it’s good.)
Here’s where I may have screwed up: While I was still running
restic rebuild-index on the first bucket/repository, I also ran
restic init and
restic backup to the second bucket/repository.
Many hours later, it suddenly occurred to me that restic might only have one cache directory, without awareness of different targets, and both repos might be getting horribly mangled.
So I killed both jobs.
Now I’m running
restic rebuild-index on the second bucket/repo. (I’ll worry about the first one later after I figure out what if anything can/should be done.)
When I look in ~/.cache/restic, I do see two subfolders with hex names. I was hopeful that was one for each of the two remote repos. But they both have timestamps later than when I killed the first
restic rebuild-index. So, it seems as if the current (second)
restic rebuild-index is updating both cache folders? In which case, that would imply there’s only one global cache folder for restic?
So my questions:
- Is running two instances at the same time, to two different buckets/repos, indeed not supported?
- Did I screw the pooch on one or both repos?
- Will a
restic rebuild-index, run by itself, fix the second repo? (No errors so far.)
- Once that completes, if I run a
restic rebuild-indexon the first bucket/repo, will that work as well? (Which would imply that either there are either two separate caches, or it gets completely rebuilt with each run of
- And most importantly, what is the meaning of everything?