Thanks @MichaelEischer for the reply.
No, in both cases it’s the total number of blobs in the snapshot.
I’ve read the Scripting section of the documentation. But can’t understand the numbers. Here is the “summary” part of a snapshot (restic snapshots --json abcd1234
):
"summary": {
"backup_start": "2024-10-18T...",
"backup_end": "2024-10-18T...",
"files_new": 5,
"files_changed": 43,
"files_unmodified": 233347,
"dirs_new": 1,
"dirs_changed": 48,
"dirs_unmodified": 24382,
"data_blobs": 89,
"tree_blobs": 48,
"data_added": 100216326,
"data_added_packed": 17808787,
"total_files_processed": 233395,
"total_bytes_processed": 54711800386
},
So there are 89 data blobs.
With the command restic stats abcd1234 --json --mode raw-data
I get this output:
{
"total_size": 37253339317,
"total_uncompressed_size": 45095159709,
"compression_ratio": 1.2104997977569625,
"compression_progress": 100,
"compression_space_saving": 17.389494665510508,
"total_blob_count": 218008,
"snapshots_count": 1
}
So in this very same snapshot there are now 218008 blobs. Why are those numbers so different? How can they have the same meaning?
tree_blobs
should be roughly equivalent to dirs_new + dirs_changed + dirs_unmodified
.
But it is not: tree_blobs
is 48 and dirs_new + dirs_changed + dirs_unmodified
= 24431.
Essentially for historical reasons. Do you have specific fields in mind?
If the backup summary would contain backup_start
and backup_end
instead of total_duration
, they would be essentially the same (except for the snapshot ID).
I’m looking forward to clarifying those numbers.