Closed Matzz closed 5 years ago
do you need to also give /root/.config/borg
?
@ThomasWaldmann I'm backuping s3 bucket mapped via s3fs. So I wan't to limit the number of read/write operations on that filesystem to reduce the cost. As far as I understand keeping /root/.cache/borg
is essential to do that.
I didn't say you shall not keep the cache - I said you might want to keep the config also (to avoid the error msg you run into and not need the workaround via the env var).
@ThomasWaldmann Sorry I misread your message. Mounting config directory helped. Thanks!
Have you checked borgbackup docs, FAQ, and open Github issues?
yes
Is this a BUG / ISSUE report or a QUESTION?
Issue / Question
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
1.1.8
Operating system (distribution) and version.
fedora:29
Hardware / network configuration, and filesystems used.
docker image
How much data is handled by borg?
N/A
Full borg command line that lead to the problem (leave away excludes and passwords)
Run twice following commands
Output:
Describe the problem you're observing.
I'm using
pschiffe/docker-borg
docker image. I know that borg don't maintain any official docker image. But my issue seems to be related to borg rather than the way how this image works. I already asked here https://github.com/pschiffe/docker-borg/issues/6 but I was redirected to borg repo.When I'm trying to backup directory using unencrypted repository I'm getting "Attempting to access a previously unknown unencrypted repository" error. I know that I could avoid that using BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK. However, I still feel that something is wrong. Due to this error I'm not fully sure that borg will use cache which is essential for me. I would like to know what borg check before emitting
Attempting to access a previously unknown unencrypted repository
. I thought it is check if hostname is the same as before but adding-h foo
didn't help me.