Closed framps closed 1 month ago
Hint: "binLMU packages" should read "binNMU ..."
Thx. Typo fixed.
I got a proposal to handle this issue in a more elegant way:
Use a different naming scheme of the backup directories which includes the os version.
Use
raspberrypi@debian12-rsync-backup-20240416-094106
instead of
raspberrypi-rsync-backup-20240416-094106
Then every time a new OS version is saved a new backup directory is used and thus a new full backup is created.
It's a low hanging fruit to add another option. A change of the backup directory name requires much more effort.
I think I will add a new option first and change the backup directory name in a later release.
This issue is obsolete and will be handled by #791
Unfortunately binNMU packages may not be updated in a backup with rsync because they get the same timestamp and size during package build and therefore rsync doesn't detect a file change and doesn't update the file in the backup.
In particular when an OS update was made the first backup of this updated system should be a full update to catch the issue with the binNMU packages.
As of now there is no way to get raspiBackup to create a new full rsync backup even a previous backup exists which will catch this issue.
A workaround to this is to define option
in the config file. Then rsync will create a checksum for every file and detect file changes even the date and size was not changed. But this unfortunately has a serious performance impact.