Feature Request: Allow setting BORG_FILES_CACHE_TTL from config #618
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#618
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I'm backing up a large file server over a rather slow line. The server contains two sections: active data and archived data. About once a year, stuff is moved from the active area to the archive area. Given the archive area is huge and only growing, it is only backed up once a month. As
BORG_FILES_CACHE_TTL
defaults to 20, the metadata from the archive area is gone when it's being backup` up again.Currently, I'm injecting
BORG_FILES_CACHE_TTL
via systemd. For consistency reasons, I would like to be able to do so from the borgmatic config instead.Other notes / implementation ideas
I think a key
files_cache_ttl
next to the existingfiles_cache
would make sense.Environment
borgmatic version: 1.5.20
borgmatic installation method: Debian package
Borg version: 1.2.2
Python version: 3.9.2
operating system and version: Debian bullseye
I will try and implement this here: https://projects.torsion.org/sur5r/borgmatic/src/branch/filescachettl
Comments and feedback very welcome.
Lookin' good! Thanks for taking the time to file this and start on the implementation. Here are a few points of feedback:
borg_keys_directory
and similar settings.borg_files_cache_ttl
to emphasize that this corresponds to the environment variable of the same name.make_environment()
function along with the setting of other Borg environment variables? In fact you probably don't even need to change that function at all.. You can likely just edit theOPTION_TO_ENVIRONMENT_VARIABLE
mapping inborgmatic/borg/environment.py
.When you're ready, please feel free to submit this as a pull request. Thanks!
@Soumik_Dutta swooped in and implemented this! The feature will be part of the next release.
I completely forgot about this. Thanks everyone!
Apparently we did too. 😄
Released in borgmatic 1.7.10!