Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Decision tree for backup types

There are different backup types and each has its advantages and disadvantages. Different backup types can be combined. For example, every months a full backup can be created with tar and in between a weekly rsync delta backup. However, this requires manual configuration of Systemd timers and requires good Systemd knowledge. The raspiBackupInstaller configures only one backup type. backup types.

All backup types can be completely restored with raspiBackup. be restored completely.

An dd backup creates a consistent binary image of the system. The entire device with the system is always read and backed up. This means that data that has not changed is also backed up. It also means that the restore device must be at least as large as the original system for the restore. No partition is resized. This causes problems especially problems, especially with SD cards, as the SD cards - although 32GB in size, for example - always have slight differences and therefore a restore of a 32GB system to another 32GB SD card cannot be successful because the SD card is slightly smaller.

An dd backup can be restored under Windows with the appropriate tools.

But it is not recommended to use the backup type dd. Explanations are given in Why should you not use dd as a backup type? in detail.

A ddz backup, like a dd backup, backs up the entire system. This method puts a heavy load on the CPU as the amount of data is reduced. (It is a dd backup with zipping switched on with -z). A restore with Windows tools is not possible.

A tar backup backs up all the data stored on the system device, although the backup is not not as large as an dd backup, as only the data that actually exists is backed up. actually exists. Therefore, a tar backup can also be restored on devices that is smaller than the original device. Of course, only if all data fits on the new device.

A tgz backup backs up the entire system, like a tar backup. This method puts a heavy load on the CPU as the amount of data is reduced. (It is a tar backup with zipping switched on with -z)

An rsync backup only saves the data that has changed since the last backup, except for the first time. last backup. The hard links of the ext3/ext4 file system file system ensures that the backup is still consistent. However, the data is not compressed. However, this in turn has the advantage that you can easily retrieve individual files from the backup by copying them. backup. This method is very fast if an initial initial backup has already been created.

TypeFull backupBackup timeBackup sizeData compressionCPU loadedCard loadedSelective restore possibleFile system
ddyeslonglargenomediumhighnoall, fat32 only up to 4GB
ddzyeslongsmalleryesyeshighnoall, fat32 only up to 4GB
taryesmediummediumnomediumyesall, fat32 only up to 4GB
tgzyesmediummediumyesyesmediumyesall, fat32 only up to 4GB
rsyncyesshort with hardlinkssmall with hardlinksnonohardlyyesext3/ext4

decisiontree

Note