Question about incremental job statistics - btrfs

[gothaggis]

I don't quite understand the reporting:
Total size: 0.0B
Data read: 0.0B
Transferred 757.5 MB (compression 1.3x, dedupe 1.5x)
Backup size 996.1 MB

different subvolume:
total size: 416.6 MB
data read 416.6 MB
Transferred 585.5MB (compression 2.3x, dedupe 1.2x)
Backup size 358.6MB

why is the transferred size larger than total size in these two cases? I understand there may be some overhead, but having no changes at all in the first case resulted in more data being transferred than the 2nd case - curious how to explain this?

[PTide]

Hi,

There is a known issue (described in Release Notes) with an overhead in 'Transferred' stats if BTRFS has no subvolumes. However, it seems that's not the case. Please describe your BTRFS structure, job settings, and circumstances when you observe the effect. Is it the same job's subsequent sessions or two separate jobs with different backups scopes?

Thanks!

[gothaggis]

I have multiple jobs, each backing up a single subvolume (all different) - spaced out over the day so they don't overlap
backup mode: volume level backup
backup destination: veeam backup and replication server 9.5 U4 over 10gbE connection
14 restore points
file system indexing, oracle processing, and active full all disabled
scheduled to run every day.

very first run of veeam agent job1 for a single btrfs subvolume (lets call it subvol1), which is 5.3TB on disk:
Total size 5.3TB
Data read 5.3TB
Transferred 848.2GB
Backup size 1003.3GB
dedupe 24.1x
Compression 5.6x
Duration 10:52:07

2nd run of job1, the next day, of subvol1 (and indeed, no data had been added to this subvolume)
Total size: 0.0B
Data read: 0.0B
Transferred 757.5 MB (compression 1.3x, dedupe 1.5x)
Backup size 996.1 MB

very first run of veeam agent job2 for a different single btrfs subvolume (subvol2), which is 1.9TB on disk:
Total size 1.9TB
Data read 1.9TB
Transferred 171.8GB
Backup size 211.1GB
dedupe 69.9x
Compression 9.1x

2nd run of job2, the next day, of subvol2
different subvolume:
total size: 416.6 MB
data read 416.6 MB
Transferred 585.5MB (compression 2.3x, dedupe 1.2x)
Backup size 358.6MB

[PTide]

2nd run of job1, the next day, of subvol1 (and indeed, no data had been added to this subvolume)
Total size: 0.0B
Data read: 0.0B
Transferred 757.5 MB (compression 1.3x, dedupe 1.5x)
Backup size 996.1 MB

That does not seem right. I'd suggest you to contact support team directly so they can investigate and contact development team directly if needed. Once you open a case please post the case ID.

Thanks!