On Nov 1, 2007 7:03 PM, Micah Anderson <[EMAIL PROTECTED]> wrote: > * Adam Porter <[EMAIL PROTECTED]> [071102 00:56]: > > Package: backupninja > > Version: 0.9.4-6 > > Severity: wishlist > > > > --- Please enter the report below this line. --- > > I don't always have my system powered up when backupninja is set to run my > > local rdiff-backup backup. It would be nice if backupninja could use > > Anacron, or some Anacron-like logic, so I could specify a frequency > > of "daily" or "every 24 hours," and then have backupninja run it if that > > much > > time has passed since the last backup was run, regardless of what time it is > > at the moment. > > > Hi, > > Please correct me if I misunderstand you, but I believe that this > functionality already exists in backupninja. > > The backupninja cron runs every hour and although the default value for > 'when' in /etc/backupninja.conf is "everyday at 01:00" you could change > that to be something that works for you, such as: when = hourly, or > specify multiple 'when' options so that the backup will fire at a time > that you are likely to have your laptop on (if multiple 'when'options > are present, then they all apply). See backup.d(5) SCHEDULING section. > > Or, you could use anacron with a job that on wakeup of your laptop > simply does a backupninja --now.
I don't necessarily want to run backupninja every hour, or even more than once a day. I simply want it to run if it's been 24 hours or more since the last time it was run. Running rdiff-backup can be CPU- and IO-intensive. I have manually niced and ioniced it down, but we shouldn't expect users to have to do that. I don't need or want it to run that often, anyway. And I don't think running --now on wakeup of a laptop would necessarily be a good idea. If someone sleeps and wakes their laptop several times a day... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
