nssbackup-team team mailing list archive

["B.J. Herbison" <bj@xxxxxxxxxxxx>]

Public bug reported:

Nssbackup currently has two controls on scheduling, a crontab entry that
controls when to run the process, and a frequency of full backups.

Proposal: Separate the control for when the process is started by cron
from the frequency of when a backup is actually run. For example, have
cron run the program every hour, but only perform an incremental backup
if six hours (or two days) have elapsed since the last successful
incremental backup.

Justification: I am running on a computer that is powered down much of
the day, and not on a regular schedule. I don't need an incremental
backup to be created every hour, but if I don't schedule nssbackup every
hour then backups will only be run occasionally. I want backups to be
run regularly without manual intervention.

Using:

Ubuntu 10.04
uname -a : Linux Oofy 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

>From Ubuntu Software Center: Version: 0.2.1ppa1~lucid1 (nssbackup)
>From Configurator help: (Not So) Simple Backup Suite 0.2.1

Installed from a PPA

** Affects: nssbackup
     Importance: Undecided
         Status: New

-- 
Separate backup frequency from crontab frequency
https://bugs.launchpad.net/bugs/601579
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.