Ability to call borg with --stats
independent of --list --filter AME
#100
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#100
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Before the logging-fix in 1.2.6, using
-v 1
(logging.INFO) would only print the borg create stats, which was all the information I personally wanted to get from the nightly backup mails.Are there any plans to control the borg
--stats
and--list
flags separately in borgmatic?I was indeed a little worried about the logging fixes changing the user experience for certain use cases. Looks like that's happened here!
What exactly were you pulling out of the
borg create
stats previously? For instance, some of that information is currently available viaborgmatic --info
, but it's more summary stats rather than per-archive stats. Put another way, what would you want to control withborg
--stats
and--list
flags separately?I'm running prune, create and check of the last 2 archives in the same borgmatic run.
This is the output I'm interested in:
When checking the nightly email reports, I mostly just glance at the "Deduplicated size" column of "This archive" to see whether the number is reasonable.
I will try the
--info
flag.Got it. Unfortunately
--info
by itself won't give you the de-duplicated size of the current / most recent backup, because that output is more oriented towards the "all archives" stats. So, a couple of ideas to get what you're looking for:-v 1
, but just grep the output for the for the data you're interested in. Example:borgmatic -v 1 ... 2>&1 | grep -C 2 size
. Not the most elegant solution, but may work.--create
, you could pass the--json
argument once witten/borgmatic#97 is done. That would allow you to get at all the size information directly via JSON values.-v 1
is more verbose than it used to be, maybe there's a case to be made for also making-v 0
more verbose, and including (only) Borg summary output there.I currently pipe the output with
-v 1
throughgrep -v -e "^[AME] .*"
to filter out the file changes, which pretty much produces the same output as before. It is then mailed to me through postfix.Personally, I vote for Option 3, but that might be too noisy for someone running silent backups.
Tangentially related discussion: #53.
I would also like something like option 3, the possibility to just print "--stats" for create and check.
I was also surprised by the change since I had previously been content with just the stats-output from each run. I am just launching it manually on my personal computers to backup to some external hard drives. The stats-output allowed me a quick overview of whether everything seemed alright or if there was a surprising increase in size.
how about passing the
--stats
like--progress
to borg?for pruning and creating backups
Continuing the discussion on this PR from none other than Stunkymonkey! witten/borgmatic#115 (comment)
Merged Stunkymonkey's PR. Support for this will be part of the next release!
Just released in borgmatic 1.2.13!