The value is from a section:
"BackendStatistics": {
"RemoteCalls": 29,
"BytesUploaded": 112855294,
which deals with Destination files. I don’t think it has Source file details. There might be a similar issue gathering statistics earlier in the processing, but I’m not certain. If you look at Channel Pipeline, it has a number of processing steps, and what one would like would be one that knows each file path, and also added (not currently in backup) blocks resulting from the file path. I don’t think (not sure) that this exists.
Better developer documentation would be nice, but the last time I looked, I thought main backup path is:
FileEnumerationProcess.cs → SourcePaths → MetadataPreProcess.cs → ProcessedFiles → FilePreFilterProcess.cs → AcceptedChangedFile → FileBlockProcessor.cs → StreamBlock → StreamBlockSplitter.cs → OutputBlocks → DataBlockProcessor.cs → BackendRequest
which shows how BackendStatistics is pretty far removed from file paths. I think DataBlockProcessor.cs
is the first spot that knows which blocks are new, and at this time it’s just blocks. Does it still know path?
looks like “no” to me, but an expert developer (they are rare, which limits ability to add features) may differ.
One easy way to reduce backup size is to backup fewer folders and files, e.g. based on a Source analysis, using any number of easily available tools. This works worse if you have a lot of exclusions they don’t know. Duplicati’s reports can find big files after excludes, but they’re not very good at adding up total of small files.
Until you run The PURGE command, versions still retained will hold whatever files they originally backed up.