Is there a way to see the size (in bytes) of each snapshot? Duplicacy’s backups started using twice as much space on my B2 storage last month, according to the bill from Backblaze. I’d like to identify exactly when this happened, so I can figure out which files are responsible.
Size of each snapshots may not tell you much because of deduplication. I.e. if snapshot a can reference 1TB worth of files and snapshot B takes another (or same?) 1TB — your duplicacy datastore can be from 1TB to 2TB. This does not tell you much about snapshots.
I think better approach to find the culprit would be to compare lists of files in each snapshot, or snapshots themselves with
duplicacy diff, to see if you have started picking up a new bunch of data
Good point. The statistic I’m interested in is the disk space taken up by the new chunks in a snapshot. This stat is displayed during the backup operation, but I guess there is no simple way to get it otherwise?
duplicacy list --files produce what you need, or at least, something you can derive what you need from?
Check command returns everything you need:
snap | rev | | files | bytes | chunks | bytes | uniq | bytes | new | bytes | NAS1-Snapshots | 31 | @ 2022-08-09 02:23 | 273811 | 1493G | 295127 | 1361G | 7914 | 42,105M | 22295 | 109,749M | NAS1-Snapshots | 32 | @ 2022-08-13 02:00 | 274917 | 1711G | 332349 | 1543G | 6473 | 33,469M | 50625 | 254,786M | NAS1-Snapshots | 33 | @ 2022-08-15 17:46 | 274930 | 1717G | 333557 | 1548G | 6667 | 34,174M | 10892 | 53,250M | NAS1-Snapshots | 34 | @ 2022-08-18 23:24 | 275016 | 1734G | 337153 | 1564G | 48 | 31,252K | 20934 | 105,130M | NAS1-Snapshots | 35 | @ 2022-08-20 22:19 | 275072 | 1749G | 340216 | 1578G | 49 | 30,628K | 3113 | 14,243M | NAS1-Snapshots | 36 | @ 2022-08-22 17:14 | 275059 | 1761G | 342774 | 1590G | 51 | 30,782K | 2613 | 11,944M | NAS1-Snapshots | 37 | @ 2022-08-25 12:25 | 275145 | 1781G | 346881 | 1608G | 62 | 30,912K | 11188 | 53,172M |