I have a few questions about the DietPi backup.
Is the complete system backed up?
The background to my query is:
I would like to back up a current DietPi system on which Wingibts is installed, among other things, and restore it on a new data carrier.
Specifically, it’s about a Pi 4 with an SSD connected via USB3.0.
But since this constellation causes minor problems with Wingbits(ADS-B) (I think it’s about USB jitter - please correct me if it’s wrong), I would like to copy the system from the SSD to a RasPiKey(eMMC module for the PI), clone it anyway.
If possible, this should happen without too much effort.
For this reason I was thinking of DietPi backup.
However, it should be noted that the RasPiKey has 32GB and the SSD is larger. However, without having just checked, I would say that less than 32GB is used on the SSD.
Hopefully I have been able to express my concern clearly.
I would appreciate a few tips and assistance.
Thanks for the link.
That’s one way of course, but quite a lot of effort.
Ultimately, I just want to copy the running system from an approx. 100GB SSD to a 32 GB eMMC, which should then be inserted into the Pi’s SD card slot.
So I understand correctly that DietPi-Backup is a full backup and thus saves the complete contents of the SSD. This is then of course too large for the eMMC?
My simple-minded thought was to install a normal standard installation of DietPi on the eMMC and then use the backup of the SSD as a restore.
I guess this is a big mistake on my part?
I have to mention that my installation is a headless system, so there is no desktop installed, which makes it difficult to work with GParted.
Backup is saving used data only using rsync. It is not creating a 1:1 image. Therefore the backup way should work.
Gparted can be used as Linux live environment on nearly every system. Easiest is to start on a regular desktop system and connect the SSD.
At the end you would need to decide between backup option or cloning of your system. Both ways have there advantages