-
Notifications
You must be signed in to change notification settings - Fork 259
Closed
Description
Using backintime version 1.3.2 from the command line only. No GUI installed.
root@server1:~/backintime# backintime --version
backintime 1.3.2
I have three profiles. I intended to run profile 1 and 2 daily at 1am and 2am respectfully. Profile 3 should be run every Sunday at 3am.
Config snippet:
profile1.name=filesystem
profile1.schedule.mode=20
profile1.schedule.time=1
profile2.name=databases
profile2.schedule.mode=20
profile2.schedule.time=2
profile3.name=containers
profile3.schedule.mode=30
profile3.schedule.time=03
profile3.schedule.weekday=7
When I run check_config
, it goes through the process of creating the crontab entries, but seems to specify the times as 1, 2 and 3 minutes past midnight:
root@server1:~/backintime# crontab -l
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
#Back In Time system entry, this will be edited by the gui:
1 0 * * * /usr/bin/nice -n19 /usr/bin/ionice -c2 -n7 /usr/bin/backintime --config /root/backintime/backintime.config backup-job >/dev/null 2>&1
#Back In Time system entry, this will be edited by the gui:
2 0 * * * /usr/bin/nice -n19 /usr/bin/ionice -c2 -n7 /usr/bin/backintime --profile-id 2 --config /root/backintime/backintime.config backup-job >/dev/null 2>&1
#Back In Time system entry, this will be edited by the gui:
3 0 * * 7 /usr/bin/nice -n19 /usr/bin/ionice -c2 -n7 /usr/bin/backintime --profile-id 3 --config /root/backintime/backintime.config backup-job >/dev/null 2>&1
Seems like a bug to me.
Cheers,
Whytey
Metadata
Metadata
Assignees
Labels
No labels