Not in a simple way, no. You could probably dig into the .sqlite file and get file sizes and the like from that but you’d basically be writing your own SQL to do it.
Could you create a feature request to include file size info into the file log?
Reducing backup size pretty much comes down to some combination of:
• reduce source size
• increase compression
• reduce versions / retention
I’d suggest you start with looking at what’s actually being backed up and make sure you’re not grabbing junk you don’t need.
Right, this is exactly was I’m trying to do. There are around 50’000 files in the profile therefore I’m trying to find the biggest and check whether I really need them.
You could set the “Advanced options” --zip-compression-level higher (such as to 9 for maximum compression). Not that this is found in the “Zip compression” section of the “Add advanced option” select list.
As far as I remember, I did it in general settings as a common rule for all backups.
You might also want to look at the --retention-policy feature (although it was added to a canary version after your beta, so you’d have to update to that version or wait for the feature to come to your upgrade path).
Could you drop me a link to read more about this feature?
The --verbose command does not affect the email output. You would need some logic to store the log file, and then attach the log file to the email for this to work.