Add a "cancel after n hours" option to nssbackup configuration

Bug #601584 reported by B.J. Herbison
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nssbackup
Opinion
Wishlist
Unassigned

Bug Description

Some incremental backups have been seen to take a long time (see reports from me and Jean-Peer in https://answers.launchpad.net/nssbackup/+question/116342 ). If a backup isn't working, it would be nice to cancel it and try again.

Proposal: Add a "cancel after n hours" option to nssbackup configuration. Allow the user to optionally specify that the next backup attempt after a failed backup should always be a full backup.

Proposed UI (based on this report and my previous request to separate run frequency from backup frequency):

   Check to see if a backup should be run: [n] minutes/hours/days
   Run an incremental backup every : [n] hours/days
   Perform a full backup every: [n] hours

   [x] Cancel an incremental backup if it takes more than: [n] hours
   The last successful full backup took 0 days 4 hours 15 minutes. (Informational message to guide setting for above parameter)
      [x] Always run a full backup after an incremental backup is canceled.

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

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thanks for reporting.

The current development version already provides an option to cancel a running backup :) The second suggestion sounds reasonable. I'm setting this to 'Opinion' in order to collect some more speakings about it.

Changed in nssbackup:
status: New → Opinion
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.