Package: storebackup
Version: 3.5.2-2
Severity: normal
Tags: d-i
X-Debbugs-Cc: debian-amd64@lists.debian.org, papachaotica@gmail.com, debian-boot@lists.debian.org
User: debian-amd64@lists.debian.org
Usertags: amd64
User: debian-boot@lists.debian.org
Usertags: amd64

Since the update from storebackup 3.2 to 3.5, two backups are triggered in quick
succession: the `anacron.timer` calls `/etc/cron.daily/storebackup`, and the
`storebackup.timer`/`service` does exactly the same thing. A look at the file
list confirms that this is not a leftover from the old version. It appears that
an old method was either overlooked during the switch to systemd or intentionally
left in place to ensure a safe transition process.
After all, two backups are better than none.
This message was translated from German using Google.

Okt 01 08:22:34 asr systemd[1]: Starting storebackup.service - Run storeBackup for all configs in /etc/storebackup.d...
Okt 01 08:27:31 asr anacron[48665]: Job cron.daily' started Okt 01 08:27:31 asr anacron[55395]: Updated timestamp for job

drwxr-xr-x  8 root         root         4,0K  1. Okt 08:27 2026.10.01_08.22.46
drwxr-xr-x  7 root         root         4,0K  1. Okt 08:31 2026.10.01_08.27.40