Dear Armin,
thanks for reporting back.
There really might be a problem with converting the config file between
BIT 1.2.1 and 1.3.3. I have to investigate this further and try to
reproduce it.
It might be a serious problem to everyone upgrading from Debian 11 to
12 and using "Repeatedly (anacron)"
Thank you all for your replies and sorry I didn't reply earlier - since
I didn't get any email notification I wasn't aware of them.
I rechecked all options and found the reason. In the "General" settings,
the Schedule was set to "Every Day". After changing this back to
"Repeatedly (anacron)", ev
Dear Armin,
maybe you can save the time generating all the diagnostic output I asked
for.
I'm not absolute sure about this point but based on my research it is
not possible to configure Back In Time (BIT) that way that it run "Every
Day" and at boot. "Every Day" do result in a crontab line li
Please show the output of
cat /etc/anacrontab
Please also think hard about if you have configured something on your
Debian 11 machines in the past?
I'm not an expert in cron and anacron but in my understanding anacron do
not start cron-jobs after their scheduled time (in hours in minutes).
Dear Armin,
thanks for reporting this. I'm member of the upstream maintainer team
and not a Debian person. Please be aware that the current maintainer
team is quit new to BIT and we are not yet familiar with all parts of
the code and the behavior of BIT. But I'll try to assist you. I need to
Package: backintime-common
Version: 1.3.3-4
I am using backintime on all my workstations for backups. It is
scheduled with "every day". As they are workstations, there is no time,
they are running reliably every day.
Before my update to bookworm, the backup was started shortly after the
workst
6 matches
Mail list logo
