add support for anacron and systemd-cron

Backup agent for Linux servers and workstations on-premises or in the public cloud

add support for anacron and systemd-cron

Veeam Logoby chris400 » Sun Feb 26, 2017 10:56 pm 1 person likes this post

I'm using Linux on Desktops too. They are not running 24/7, so cronjobs can be missed. Gladly there is anacron and systemd-cron. Pls add an option to use it in veeam.

https://sourceforge.net/projects/anacron/
https://github.com/systemd-cron/systemd-cron
chris400
Influencer
 
Posts: 10
Liked: 3 times
Joined: Sat Feb 04, 2017 10:31 am
Full Name: Christoph

Re: add support for anacron and systemd-cron

Veeam Logoby PTide » Fri Mar 03, 2017 10:51 am 1 person likes this post

Hi,

The request that you've made makes sense and has been noted. Would you like to start missed backups at startup or after a delay?

Thank you!
PTide
Veeam Software
 
Posts: 4033
Liked: 336 times
Joined: Tue May 19, 2015 1:46 pm

Re: add support for anacron and systemd-cron

Veeam Logoby chris400 » Mon Mar 06, 2017 7:00 am 1 person likes this post

Missed backups should start at boot after a (configurable) delay :-)
chris400
Influencer
 
Posts: 10
Liked: 3 times
Joined: Sat Feb 04, 2017 10:31 am
Full Name: Christoph

Re: add support for anacron and systemd-cron

Veeam Logoby senfsosse » Sun Feb 25, 2018 8:13 am 1 person likes this post

Seems this feature has not made it in V2, has it? I would very much appreciate if this could be implemented as soon as possible.
senfsosse
Lurker
 
Posts: 1
Liked: 1 time
Joined: Sun Feb 25, 2018 8:08 am
Full Name: Thomas Runge

Re: add support for anacron and systemd-cron

Veeam Logoby PTide » Mon Feb 26, 2018 5:44 pm

Hi,

Right, it hasn't made it in v2. As a workaround you can copy-paste the automatically created cron entry to the job scheduler of your choice, it will work just fine. But don't forget to disable built-in scheduler in the job settings.

Also, I'd like to share some concerns that I have regarding the subject. Job schedulers like anacron and systemd-cron/systemd-timers allow users to implement advanced schema (like run missed backup, for example), while cron does not provide such flexibility. Thus, if we decide to leverage alternative scheduler(s) to support advanced scenarios, that will mean that some users won't be able to benefit from new features, which seems to be a little bit unfair :) Maybe we should create a built-in job scheduler instead of trying to support all flavours of linux schedulers?

Thanks
PTide
Veeam Software
 
Posts: 4033
Liked: 336 times
Joined: Tue May 19, 2015 1:46 pm


Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 2 guests