Adjustments for Borg 1.2.0
while playing around with the 1.2 beta and using borgmatic in a venv for automated backups I was wondering if it - while adding adaptations for 1.2 and the new compaction behavior- would be feasible to add a passthrough mode to run verbatim borg commands on the reposiroties configured with borgmatic, making it possible to at least manually run some new borg features on each configured repo with borgmatic setting up the environment correctly each time (passphrases, data paths, ssh args etc). Like
/opt/borgmatic_venv/bin/borgmatic -c /etc/someconfig borg-run break-lock
/opt/borgmatic_venv/bin/borgmatic -c /etc/someconfig borg-run compact --cleanup-commits
(borg-run is the first thing I came up with)
The latter imrpving on the current situation with the compaction in borg 1.2, even if integration into the normal backup workflow would still be required I think.
@bjo: Thanks for bringing this to my attention! Fortunately in my delay to respond, Borg 1.2.0 hasn't been released quite yet...
There's no specific status—nobody is working on it that I'm aware of. But in the meantime, have you tried
borgmatic borg compact?
Anyone have thoughts on whether
borgmatic compact should be run automatically (when no actions are specified)? I assume it should, since otherwise a repository with a Borg 1.2+ client will grow without bound. But I wanted to see if there were any arguments against, e.g. that running
compact frequently will be slow.
I went ahead and integrated
compact as a default action. The thinking is that
prune won't "work" (actually free up space) without it, and so it would be in line with user expectations to
compact whenever automatically running
prune. However, if you run
prune explicitly (rather than as a default action), you'll still need to
compact on your own.
Implemented in master. Will be shipped as part of the next release. If there are any details I've missed, please post them here!
Deleting a branch is permanent. It CANNOT be undone. Continue?