Large Image when backing up new RevPi Core 3+ Using RPIBoot and Win32 DiskImager

[sirockin]

I’ve just received a new RevPi Connect+ (32GB) and have been trying to back up the installed image from my Windows 10 machine as described here:
https://revolution.kunbus.com/tutorials ... ng-images/

I was able to successfully run the RPIBoot and then the Win32 disk imager but the final result (which took over an hour to complete) was an image file of 29.1GB. I repeated the process wondering if I had made a mistake and got an identical result.

I have checked the disk usage on the machine itself via SSH and get the following:

```
pi@RevPi21499:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 2.4G 25G 9% /
devtmpfs 459M 0 459M 0% /dev
tmpfs 464M 0 464M 0% /dev/shm
tmpfs 464M 6.2M 458M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 44M 22M 22M 50% /boot
tmpfs 93M 0 93M 0% /run/user/1000
```

The web interface says I have 24.98 free.

[dirk]

Hi sirockin, the image of the system is just a raw copy of the contents of the eMMC. So you cannot enhance this process at all but you may use some compression software afterwards to shrink the image file.

[sirockin]

Thanks Dirk. So just to be clear, if I restore the Rev Pi from this image, the disk space utitlisation will be as before - 2.4GB?

[dirk]

Hi well yes. But the process of saving or restoring the image takses the whole space on the eMMC which is in your case 32Gb.