[Nssbackup-team] [Bug 601579] Re: [Feature request] Separate backup frequency from crontab frequency
Checking for connection type/speed is useful. On a somewhat related issue, I backup from home to a network device. When I'm away from home the device is not available. I put up with the error messages backup started/backup failed, but it would be nicer if I could say not being able to reach the backup device is normal, be totally silent in that situation. Of course, for all cases (drive not available, slow network connection, or anything else), it would be nice to be notified if no backups had been possible for a week so I could fix the problem or change the requirements. -- [Feature request] 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. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 601579] [NEW] Separate backup frequency from crontab frequency
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. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
[Nssbackup-team] [Bug 601584] [NEW] Add a cancel after n hours option to nssbackup configuration
Public bug reported: 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 ** Affects: nssbackup Importance: Undecided Status: New -- Add a cancel after n hours option to nssbackup configuration https://bugs.launchpad.net/bugs/601584 You received this bug notification because you are a member of NSsbackup team, which is subscribed to NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
Re: [Nssbackup-team] [Question #116342]: tar takes a long time, 100% CPU, with no output
Question #116342 on NSsbackup changed: https://answers.launchpad.net/nssbackup/+question/116342 Status: Answered = Open B.J. Herbison is still having a problem: Thank you for the response. I appreciate that you did not write and do not maintain tar, but I hope you have insight into how nssbackup is using tar. I don't have insight into the NAS device, but a simple two window experiment with cat and ls -l showed that writing to a file shows up in the file size before the file is closed so it appears that the backup process is hung before gzip has enough data to start writing to disk. Looking at top, tar is taking 100% of a CPU and gzip 0%. Looking at ps, tar has over nine minutes of CPU time in ten minutes, gzip still shows up at 0:00. There was a burst of network traffic at the backup start (writing the nine files relating to the backup) but the network traffic has been under 4 KiB/s since then. I did not catch the start of the backup with iotop, but I never saw the tar process on the list. (I should have read the man page and used iotop -o or pressed o before the backup started.) Do you have any suggestions for what I could try next? I remember tar having some problems with long file names quite a while ago (over a decade) but I don't remember the symptoms -- and I don't remember doing anything strange that would add unusually long file names between when the backups worked and when they stopped. (By the way, do the old nssback.date.log files left by a failed run get cleaned up automatically at some point or will I need to clean them up manually when this issue gets resolved?) Thank you for your help with this problem. You received this question notification because you are a member of NSsbackup team, which is an answer contact for NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
Re: [Nssbackup-team] [Question #116342]: tar takes a long time, 100% CPU, with no output
Question #116342 on NSsbackup changed: https://answers.launchpad.net/nssbackup/+question/116342 B.J. Herbison gave more information on the question: Additional information: The target device is a mounted network drive, but it is available with over 1TB free. The backup created nine files in the target directory so it is writable. Nothing looks unusual in the log file, the last line talks about invoking tar. -- You received this question notification because you are a member of NSsbackup team, which is an answer contact for NSsbackup. ___ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
