I just backed up a new instance of a raspberry pi that is a pretty
close clone of an existing one.
The backup size shows as follows:
File Size/Count Reuse Summary
Existing files are those already in the pool; new files are those added to
the pool. Empty files and SMB errors aren't counted in the reuse and new counts.
Totals Existing Files New
Files
Backup# Type #Files Size/MiB MiB/sec #Files Size/MiB
#Files Size/MiB
0 full 117300 4179.6 9.07 20044 542.7 4
0.2
I would have thought that: Totals = Existing + New
(with the exception that there might be some double counting due to multiple
copies of the same file)
However, I don't think this explains the difference between:
Total = 117300 files
Existing + New = 20048 files
Total = 4179.6 MiB
Existing + New = 542.9 MiB
Am I missing something here???
Also, according to 'df' the actual number of MiB on the partitions
being backed up is 3920.0 MiB. Since I am excluding /tmp/ and a small
number of other directories and files, the actual raw size of the
files to be backed up is < 3920 MiB. Running 'du -sxb' shows the
usage is: 3678.0 MiB.
So why does backuppc show a total backup size of 4179.6 MiB that is
bigger than the total space used on the 2 partitions being backed up
as shown by 'df' or 'dh'?
Could this be explained just by sparse files?
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
